release.yml: pin Inno Setup to 6.2.2 (innoextract 1.9 in trixie)

innoextract 1.11/1.10/1.9 in Debian trixie chokes on 6.4.3 too — actual line where innoextract added 6.4 support requires upstream HEAD. 6.2.2 is the last version reliably parsed by innoextract 1.9+ which is what trixie ships.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

.gitea/workflows/release.yml

@@ -87,13 +87,15 @@ jobs:
           Xvfb :99 -screen 0 1024x768x16 &
           sleep 1
           wineboot --init >/dev/null 2>&1 || true
-          # Pin Inno Setup version. Must match what innoextract on the
+          # Pin Inno Setup version. The innoextract package in Debian
-          # runner image can unpack — innoextract 1.11 (latest in Debian
+          # trixie (1.9.x) parses headers up through Inno Setup 6.2.x.
-          # trixie as of 2026-05) supports Inno Setup up to 6.4.x. Newer
+          # 6.3+ already fails with "Unexpected setup data version" /
-          # versions (6.5+, 6.7+) fail with "Setup loader checksum mismatch".
+          # "Stream error while parsing setup headers", 6.5+ with
-          # When innoextract 1.12+ lands we can bump to 6.7.x.
+          # "Setup loader checksum mismatch". Stay on 6.2.2 until either
-          INNO_VERSION="6.4.3"
+          # innoextract gets bumped in Debian or we replace it with a
-          INNO_TAG="is-6_4_3"
+          # docker-image-based ISCC step.
+          INNO_VERSION="6.2.2"
+          INNO_TAG="is-6_2_2"
           curl -fsSL -o /tmp/innosetup.exe \
             "https://github.com/jrsoftware/issrc/releases/download/${INNO_TAG}/innosetup-${INNO_VERSION}.exe"
           # innoextract unpacks the installer payload to ./app — that's the