5 Commits

Include renames

Author	SHA1	Message	Date
janikandClaude Fable 5	19327c23b1	Release 1.4.1: a Bonded checkbox in the terminal tables ... The config's per-terminal bonded key becomes editable in the dialog (previously file-only, shown as a text suffix): checked, the terminal's contacts short into one internally joined lug - the total value stays prescribed, the per-contact split is a solve outcome. Same-name rectangle groups seed it checked as before; unchecking one falls back to the per-cell area share, and checking a single-contact terminal gives it an equipotential-lug contact instead of uniform injection. Save config... writes the flag back (removed when unchecked - false is the schema default). With this, every non-structural terminal option (active, values, v_oc, contact layer, bonded, comment) is table-editable. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-08-27 17:20:35 +07:00
janikandClaude Fable 5	26b1cfaa45	Release 1.4.0: PDN mode, the config-file workflow, and the dialog editor ... Multiple Thevenin supplies and prescribed-current loads on one net, solved in absolute volts with the Tellegen power balance verified per run; a source-sink pair table (effective copper resistance per supply x load pair plus an exactly-summing proportional-sharing loss attribution), in summary.txt and as its own figure. Bonded terminals short a package's contacts into one lug so the per-pin split becomes a solve outcome. Geometry dumps carry the terminal set (schema v8). The dialog gained a Classic/PDN mode selector and a full PDN editor: per-role supply/load tables built from the marker rectangles (or a config's terminal set, which never pins mode or net), with Component hints, per-terminal Layer scopes, Active checkboxes, comments, a per-net row filter, resizable tables and a scrolling, screen-sized dialog. Numbers accept SI suffixes (50m, 4.7k) everywhere. fill_res_config.json fully specifies a run (classic or PDN) with validation, comments, named side-by-side configs (the one called default auto-loads), Load/Save buttons with an editable file name, and saves that never drop anything drawn on the board. 347 tests, green on Python 3.13 and on the 3.9 macOS wheel stack. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-08-27 17:01:24 +07:00
janikandClaude Fable 5	24fed64f83	Release 1.3.0 ... macOS is now field-tested and working; the README platform notes say so instead of untested. Linux remains audited-only. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-07-23 13:37:17 +07:00
grabowski	d05d523995	Release 1.2.2	2026-07-22 16:56:26 +07:00
grabowski	d7c3089031	Release notes come from a file in the repo, not the tag ... Deriving the body from the tag annotation does not survive CI: the release action does not fall back to it (v1.2.0 published empty), and checkout leaves the tag lightweight, so %(contents) yields the commit message instead - which is what v1.2.1 first published. Keep the notes at docs/release-notes/v<version>.md, pass that as body_path, and fail the run when it is missing.	2026-07-22 16:27:31 +07:00