From d05d5239953bb773a29504f4f23adc15ccfdea4e Mon Sep 17 00:00:00 2001
From: grabowski <berwn@buildfor.life>
Date: Wed, 22 Jul 2026 16:56:26 +0700
Subject: [PATCH] Release 1.2.2

---
 docs/release-notes/v1.2.2.md | 40 ++++++++++++++++++++++++++++++++++++
 metadata.json                |  2 +-
 pyproject.toml               |  2 +-
 uv.lock                      |  2 +-
 4 files changed, 43 insertions(+), 3 deletions(-)
 create mode 100644 docs/release-notes/v1.2.2.md

diff --git a/docs/release-notes/v1.2.2.md b/docs/release-notes/v1.2.2.md
new file mode 100644
index 0000000..71d7114
--- /dev/null
+++ b/docs/release-notes/v1.2.2.md
@@ -0,0 +1,40 @@
+Results are unchanged from 1.2.1 for the same board and settings. This
+release is about what the plugin tells you while it works, and about no
+longer overstating what a frequency result means.
+
+Progress while solving:
+
+- The dialog used to close on OK and leave nothing on screen until the
+  figures appeared - minutes, on a real board, with no sign the plugin
+  was doing anything. A small window now stays up for that whole
+  stretch: the stage running, elapsed seconds, and Cancel.
+- It covers the figure work as well as the solve. Laying out labels and
+  writing the four PNGs at full resolution is seconds on a modest board
+  and 10-15 on a large one, and that used to be silent too.
+- Cancel stops the solve and returns you to the board with no error
+  figure - the run simply reports that it was cancelled.
+
+Frequency results are described honestly:
+
+- Nothing advertises "AC resistance" any more. At f > 0 the plugin
+  applies the exact 1D foil and barrel skin-effect correction and
+  nothing else: proximity redistribution and inductance are not
+  modelled, so the number is a lower bound on the resistive rise, not
+  an AC impedance simulation. The README headline, the PCM and plugin
+  descriptions, the dialog note, the CLI help and the summary line all
+  say so now.
+- The computation itself has not changed - only its description. A
+  frequency result from 1.2.1 is the same number, previously labelled
+  in a way that invited it to be read as an impedance.
+
+Also in this release:
+
+- The offline runner takes --progress, so the same busy window can be
+  used outside KiCad.
+- The frequency field keeps its specific reason for rejecting an input
+  ("1,500" is a thousands separator, "-5" is negative) instead of a
+  generic "cannot parse".
+
+The in-KiCad |J| overlay push remains experimental and opt-in, off by
+default. It writes reference images to User.9-User.12 and replaces what
+is on those layers.
diff --git a/metadata.json b/metadata.json
index cdc64b4..992ac51 100644
--- a/metadata.json
+++ b/metadata.json
@@ -17,7 +17,7 @@
     },
     "versions": [
         {
-            "version": "1.2.1",
+            "version": "1.2.2",
             "status": "stable",
             "kicad_version": "10.0",
             "runtime": "ipc"
diff --git a/pyproject.toml b/pyproject.toml
index 75524fd..a800bd6 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -3,7 +3,7 @@
 # the dependency list there in sync with [project.dependencies].
 [project]
 name = "fill-resistance"
-version = "1.2.1"
+version = "1.2.2"
 description = "DC resistance of copper zone fills and traces between two contacts (KiCad 10 plugin)"
 license = "GPL-3.0-or-later"
 requires-python = ">=3.11"
diff --git a/uv.lock b/uv.lock
index 312d8c6..bcc82b6 100644
--- a/uv.lock
+++ b/uv.lock
@@ -216,7 +216,7 @@ wheels = [
 
 [[package]]
 name = "fill-resistance"
-version = "1.2.1"
+version = "1.2.2"
 source = { virtual = "." }
 dependencies = [
     { name = "kicad-python" },