Stop claiming a verification that does not happen - #35
Merged
Conversation
DeliriumPulse
force-pushed
the
docs/release-truthful
branch
from
August 8, 2026 09:59
b4a49a5 to
f9014dc
Compare
docs/RELEASE.md said the verifier rejects any digest differing from the checked-in release-reference.json. Nothing reads that file. It was corrupted deliberately and pnpm release:verify still exited 0, and it had sat a full release stale without anything noticing. The README made a softer version of the same claim. verify-release.mjs recomputes digests from the artifacts on disk and compares them to a manifest derived from those same artifacts, so it proves reproducibility from this source, not conformance to an independent record. Both now say that, and point at the attestation for the check that is actually independent. Also repoints the attestation command and the trusted-publisher settings at the CodeTruss organisation. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
DeliriumPulse
enabled auto-merge (squash)
August 8, 2026 10:09
DeliriumPulse
force-pushed
the
docs/release-truthful
branch
from
August 8, 2026 10:09
f9014dc to
a6a2665
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
docs/RELEASE.mdstated the verifier rejects any archive, SBOM or executable digest differing from the checked-inrelease-reference.json. Nothing reads that file — corrupting it deliberately leftpnpm release:verifyat exit 0, and it had gone a full release stale unnoticed.The README made a softer version of the same claim. What
verify-release.mjsactually does is recompute digests from the artifacts on disk and compare them to a manifest derived from those same artifacts: proof of reproducibility from this source, not conformance to an independent pin. Both documents now say that plainly and point at the attestation for the genuinely independent check.Also repoints the attestation command and trusted-publisher settings at the CodeTruss org.
A documented guarantee with no code behind it is worse than no guarantee, so this errs toward describing reality. Making the verifier actually enforce the reference is the better long-term fix and needs the file in both repos; worth doing separately.
🤖 Generated with Claude Code