build(release): 1.2.2 with the sign-out fix #19

Open
james.maes wants to merge 1 commits from release/1.2.2 into main
pull from: release/1.2.2
Owner

Version 1.2.2. The only application change since v1.2.1 is the sign-out fix merged in PR 18 (a695996): signing out ends the identity provider's browser session as well as the QQQ session, and every browser sign-in sends max_age=0 beside prompt=login, so the next sign-in asks for credentials.

Change

Same files as the 1.2.1 release commit (6404922), no code change:

  • Directory.Build.props: VersionPrefix 1.2.1 to 1.2.2.
  • .github/workflows/ci.yml, build/Build-CiRelease.ps1, build/Package-Release.ps1: version defaults to 1.2.2.
  • CHANGELOG.md: the Unreleased section becomes 1.2.2.
  • docs/SESSION-STATE.md: 1.2.2 prepared, not tagged, signed or released.

README, RELEASING and INSTALLATION still name 1.2.1 as the current stable; that stays true until a signed 1.2.2 is published (1.2.1 updated them in a follow-up docs PR after the release).

Verification run on this branch (d6c3013, development PC)

  • dotnet restore Qqq.PrintAgent.NativeCI.slnx -p:Platform=x64 --locked-mode: exit 0.
  • dotnet build Qqq.PrintAgent.NativeCI.slnx -c Release -p:Platform=x64 --no-restore -warnaserror: 0 warnings, 0 errors.
  • dotnet test tests/Qqq.PrintAgent.Cli.Tests -c Release -p:Platform=x64 --no-restore: 377 passed, 0 failed, 0 skipped.
  • python .github/scripts/check-source-headers.py: 319 tracked files verified.
  • ./build/Analyze-Scripts.ps1: 17 scripts, 75 rules, no findings.
  • ./build/Package-Release.ps1 -ProductVersion 1.2.2 -ReleaseVersion 1.2.2: exit 0 (SDK inventory, branded-installer dry run, packaging input checks, generic and gg-forge installers, 0 warnings and 0 errors in both MSI builds).

Not run on this PC: ./build/Verify.ps1 and Qqq.PrintAgent.Core.Tests. CLAUDE.md forbids building Core.Tests here (Defender quarantine); the hosted run under Checks is the evidence for both.

Unsigned local installers (not release assets)

Built from d6c3013; all three executables in both payloads report 1.2.2+d6c30132475bc69e4701d0f944c5358a713c9bf9, file version 1.2.2.65535. Get-AuthenticodeSignature reports NotSigned for both.

File Bytes SHA-256
QqqPrintAgent-v1.2.2-x64.msi 128698752 bc121723691402c7f31ebf5e76ceb22e8d7945bffddb16d2a37c48e3c98218ff
GgForgePrintAgent-v1.2.2-x64.msi 128678638 bd3739014fc01e7c98c72b04c1b1080b63573aa58a238c54a1d14fc36528356c

These prove the 1.2.2 source packages for both editions. They are not attached anywhere; the release installers are rebuilt from the merge commit and signed.

Checks

  • GitHub shadow, hosted Windows: ci run 42736423971 on d6c30132475bc69e4701d0f944c5358a713c9bf9 (branch release/1.2.2, event push): success. It ran Verify.ps1 (Core.Tests 197 passed, Windows/CLI tests 377 passed, 0 failed, 0 skipped), the SDK inventory, the branded-installer and packaging checks and both unsigned MSI builds at 1.2.2. The branch reached the shadow without any push to GitHub from this work.
  • Gitea: main has no .gitea/workflows (PR 17 adds them and is still open), so no Gitea Actions run exists for this branch and the commit carries no Gitea status.

Not done

No tag, no signing, no release, no merge. Signing and publication are the owner's steps.

🤖 Generated with Claude Code

Version 1.2.2. The only application change since `v1.2.1` is the sign-out fix merged in PR 18 (`a695996`): signing out ends the identity provider's browser session as well as the QQQ session, and every browser sign-in sends `max_age=0` beside `prompt=login`, so the next sign-in asks for credentials. ## Change Same files as the 1.2.1 release commit (`6404922`), no code change: - `Directory.Build.props`: `VersionPrefix` 1.2.1 to 1.2.2. - `.github/workflows/ci.yml`, `build/Build-CiRelease.ps1`, `build/Package-Release.ps1`: version defaults to 1.2.2. - `CHANGELOG.md`: the `Unreleased` section becomes `1.2.2`. - `docs/SESSION-STATE.md`: 1.2.2 prepared, not tagged, signed or released. README, RELEASING and INSTALLATION still name 1.2.1 as the current stable; that stays true until a signed 1.2.2 is published (1.2.1 updated them in a follow-up docs PR after the release). ## Verification run on this branch (`d6c3013`, development PC) - `dotnet restore Qqq.PrintAgent.NativeCI.slnx -p:Platform=x64 --locked-mode`: exit 0. - `dotnet build Qqq.PrintAgent.NativeCI.slnx -c Release -p:Platform=x64 --no-restore -warnaserror`: 0 warnings, 0 errors. - `dotnet test tests/Qqq.PrintAgent.Cli.Tests -c Release -p:Platform=x64 --no-restore`: 377 passed, 0 failed, 0 skipped. - `python .github/scripts/check-source-headers.py`: 319 tracked files verified. - `./build/Analyze-Scripts.ps1`: 17 scripts, 75 rules, no findings. - `./build/Package-Release.ps1 -ProductVersion 1.2.2 -ReleaseVersion 1.2.2`: exit 0 (SDK inventory, branded-installer dry run, packaging input checks, generic and `gg-forge` installers, 0 warnings and 0 errors in both MSI builds). Not run on this PC: `./build/Verify.ps1` and `Qqq.PrintAgent.Core.Tests`. CLAUDE.md forbids building Core.Tests here (Defender quarantine); the hosted run under Checks is the evidence for both. ## Unsigned local installers (not release assets) Built from `d6c3013`; all three executables in both payloads report `1.2.2+d6c30132475bc69e4701d0f944c5358a713c9bf9`, file version `1.2.2.65535`. `Get-AuthenticodeSignature` reports `NotSigned` for both. | File | Bytes | SHA-256 | | --- | --- | --- | | `QqqPrintAgent-v1.2.2-x64.msi` | 128698752 | `bc121723691402c7f31ebf5e76ceb22e8d7945bffddb16d2a37c48e3c98218ff` | | `GgForgePrintAgent-v1.2.2-x64.msi` | 128678638 | `bd3739014fc01e7c98c72b04c1b1080b63573aa58a238c54a1d14fc36528356c` | These prove the 1.2.2 source packages for both editions. They are not attached anywhere; the release installers are rebuilt from the merge commit and signed. ## Checks - GitHub shadow, hosted Windows: `ci` run [42736423971](https://github.com/QRun-IO/qqq-print-agent/actions/runs/42736423971) on `d6c30132475bc69e4701d0f944c5358a713c9bf9` (branch `release/1.2.2`, event `push`): **success**. It ran `Verify.ps1` (Core.Tests 197 passed, Windows/CLI tests 377 passed, 0 failed, 0 skipped), the SDK inventory, the branded-installer and packaging checks and both unsigned MSI builds at 1.2.2. The branch reached the shadow without any push to GitHub from this work. - Gitea: `main` has no `.gitea/workflows` (PR 17 adds them and is still open), so no Gitea Actions run exists for this branch and the commit carries no Gitea status. ## Not done No tag, no signing, no release, no merge. Signing and publication are the owner's steps. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
james.maes added 1 commit 2026-11-10 01:30:58 +00:00
Version 1.2.2 carries the sign-out fix merged in PR 18 (a695996): sign-out
ends the identity provider's session as well as the QQQ session, and every
browser sign-in sends max_age=0, so the next sign-in asks for credentials.
No other application change since v1.2.1.

Same files as the 1.2.1 release change: VersionPrefix, the CI and packaging
version defaults, the CHANGELOG heading and the session state. Not tagged,
signed or released.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Signed-off-by: James Maes <james@kof22.com>
You are not authorized to merge this pull request.
This pull request can be merged automatically.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin release/1.2.2:release/1.2.2
git checkout release/1.2.2
Sign in to join this conversation.