Skip to content

release: the verdict sees machine/, not only the files it hashes - #98

Merged
aledbf merged 1 commit into
mainfrom
release/verdict-sees-the-definition
Oct 2, 2026
Merged

aledbf merged 1 commit into
mainfrom
release/verdict-sees-the-definition

Conversation

@aledbf

@aledbf aledbf commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

v20261002.01's notes say "Checkpoints taken against v20261001.02 still resume". They do not: #97 changed how the fingerprint is hashed, and fingerprint-diff only compared the files Fingerprint hashes. A change to machine/ - a device added, the shape, the hashing - moves every fingerprint and was invisible to the verdict.

  • hack/release writes fingerprint_sha256 into machine.env: spin-machine fingerprint of the shipped tree with a named CPU (Skylake-Server-v4), so no runner's own CPU enters it. spin pins go.mod to the release's commit (hack/spin-machine refuses otherwise), so this is the machine/ spin computes with.
  • fingerprint-diff counts it among FP_KEYS. Against a release that does not record it (every one so far), the verdict is the partial one: "Not compared, and therefore not vouched for: fingerprint_sha256".

Checked: the extraction yields the 64-hex fingerprint of _output; fingerprint-diff against v20261002.01 gives the partial verdict.

🤖 Generated with Claude Code


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

fingerprint-diff compared qemu, kernel, bios and pvh, so a change to what machine/ hashes or
how - #97 folded the fingerprint into one hash - moved every fingerprint while the verdict
said checkpoints still resume. hack/release records Fingerprint itself, of the shipped tree
with a named CPU, as fingerprint_sha256, and the verdict compares it with the rest.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
@aledbf
aledbf merged commit ca7b54f into main Oct 2, 2026
2 checks passed
@aledbf
aledbf deleted the release/verdict-sees-the-definition branch October 2, 2026 01:59
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