Skip to content

Stamp the verified rc.4 Windows digest for publication - #20

Merged
oliverdougherC merged 1 commit into
mainfrom
codex/rc4-publish-20260922
Sep 22, 2026
Merged

oliverdougherC merged 1 commit into
mainfrom
codex/rc4-publish-20260922

Conversation

@oliverdougherC

Copy link
Copy Markdown
Owner

Single-line publication stamp: fills the verified 1.3.0-rc.4 Windows GUI SHA-256 (2ec0a4bcb7d94af340e61a1837bfc9380b51b2dd60bbd1f48eb023dfa24c0379, 180,189,569 bytes, built from 5d379c7, hash-verified on the build host) into frontend/app/run/releaseAssets.ts. The console digest ships in the release SHA256SUMS only, matching rc.3. Historical rc.3 digests untouched; no client, protocol, or scientific changes, so the accepted binaries remain source-bound to 5d379c7.

Verified locally: vitest 78/78, eslint+typecheck clean, next build succeeds.

The frozen GUI executable was rebuilt from 5d379c7 on the owned Windows host,
hash-verified there (2ec0a4bc...c0379, 180,189,569 bytes), accepted through the
native recovery/consent sweep, and merged as PR #19. The page rendered
"SHA-256 published with the release" for the primary Windows download until
this one line exists; with it, the page names the exact bytes users must match
before running. The console companion digest ships in the release SHA256SUMS,
not on the page, matching rc.3. No other field changes: rc.3 digests stay as
published history, and the Mac/Linux entries already carry their verified
byte-identical digests.
@oliverdougherC
oliverdougherC merged commit f98eec7 into main Sep 22, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant