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

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>

.github/workflows/ci.yml

@@ -12,10 +12,10 @@ on:
     inputs:
       product-version:
         type: string
-        default: '1.2.1'
+        default: '1.2.2'
       release-version:
         type: string
-        default: '1.2.1'
+        default: '1.2.2'
 
 permissions:
   contents: read
@@ -59,8 +59,8 @@ jobs:
           ./build/Test-PackagingInputs.ps1
       - name: Build unsigned prerelease MSI
         env:
-          PRODUCT_VERSION: ${{ inputs.product-version || '1.2.1' }}
-          RELEASE_VERSION: ${{ inputs.release-version || '1.2.1' }}
+          PRODUCT_VERSION: ${{ inputs.product-version || '1.2.2' }}
+          RELEASE_VERSION: ${{ inputs.release-version || '1.2.2' }}
         run: |
           ./build/Build-Installer.ps1 -ProductVersion $env:PRODUCT_VERSION -ReleaseVersion $env:RELEASE_VERSION
           if ($LASTEXITCODE -ne 0) { exit $LASTEXITCODE }

CHANGELOG.md

@@ -1,6 +1,6 @@
 # Changelog
 
-## Unreleased
+## 1.2.2
 
 Sign-out now 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 always asks for credentials (the provider
@@ -11,7 +11,7 @@ and the provider's own discovery (HTTPS end-session endpoint on the issuer's ori
 hint), and the companion opens it in the browser and waits for the state-matched return. A server without the
 capability gets the ordinary logout, and the log says the provider session was not ended. The command-line
 `sign-out` cannot open the companion's callback inbox, so it still ends only the QQQ session and says so.
-No change to pairing, history or the printing protocol.
+No change to pairing, history or the printing protocol, and no other application change since 1.2.1.
 
 ## 1.2.1
 

Directory.Build.props

@@ -60,7 +60,7 @@
         commit as "+<sha>" on AssemblyInformationalVersion, which the About dialog and the
         CLI's version output show as a short hash. -->
    <PropertyGroup>
-      <VersionPrefix>1.2.1</VersionPrefix>
+      <VersionPrefix>1.2.2</VersionPrefix>
       <VersionSuffix></VersionSuffix>
    </PropertyGroup>
 

build/Build-CiRelease.ps1

@@ -14,9 +14,9 @@ bundle with SHA256SUMS. It takes no certificate, timestamp server or payload inp
 [CmdletBinding()]
 param(
    [ValidatePattern('^\d+\.\d+\.\d+$')]
-   [string] $ProductVersion = '1.2.1',
+   [string] $ProductVersion = '1.2.2',
    [ValidatePattern('^\d+\.\d+\.\d+(-[0-9A-Za-z.-]+)?$')]
-   [string] $ReleaseVersion = '1.2.1'
+   [string] $ReleaseVersion = '1.2.2'
 )
 
 $ErrorActionPreference = 'Stop'

build/Package-Release.ps1

@@ -4,8 +4,8 @@
 
 [CmdletBinding()]
 param(
-   [string] $ProductVersion = '1.2.1',
-   [string] $ReleaseVersion = '1.2.1',
+   [string] $ProductVersion = '1.2.2',
+   [string] $ReleaseVersion = '1.2.2',
    # Assemble artifacts/release from an already built MSI (the signed stable flow builds and signs it in
    # separate workflow steps). With ExpectedPublisherSubject the MSI must carry that publisher's signature.
    [switch] $AssembleOnly,

docs/SESSION-STATE.md

@@ -1,3 +1,9 @@
+# Session state — 2026-11-09
+
+## Current — 1.2.2 prepared (sign-out fix); not tagged, signed or released
+
+Version 1.2.2 carries only the sign-out fix merged in PR 18 (`a695996`): sign-out ends the identity provider's session and every browser sign-in sends `max_age=0`. No other application change since `v1.2.1`. The release change follows the 1.2.1 commit: `VersionPrefix`, the CI and packaging version defaults and the CHANGELOG heading. On the release branch, on the development PC: locked NativeCI restore, Release x64 build with `-warnaserror` (0 warnings, 0 errors), 377 Windows/CLI tests passed with no failures or skips, source notices verified for 319 tracked files, PowerShell analysis clean (17 scripts). Core.Tests was not built locally (Defender quarantine unchanged), so `Verify.ps1` was not run here; hosted CI is the evidence for it. 1.2.1 stays the current stable until a signed 1.2.2 is published. Next: merge, tag `v1.2.2` on the merge commit, signed generic and GG Forge installers, release with checksums computed after signing, install on the print station. The server must advertise `nativeSessionLogout` and the provider must end its session on the invalidation flow for the fix to take effect.
+
 # Session state — 2026-11-06
 
 ## Current — 1.2.1 released; printing cohort protocol 1.1.0 / QBit 1.1.0 / client 1.2.1 complete