Repository navigation
Move the tap to 0.8.0 and make it a release step - #20
Merged
Merged
Conversation
The tap itself is already at 0.8.0 (BootIntel/homebrew-tap@eca8bf0), with the four checksums read out of the cli-v0.8.0 SHA256SUMS artifact and paired with each url line programmatically rather than transcribed. A wrong digest makes `brew install` fail with a checksum mismatch, which reads to a user like a compromised download. Two fixes here. The in-repo reference copy sat at 0.5.0 while 0.6.0, 0.6.1 and 0.7.0 shipped, so it was advertising checksums for archives nobody would install, under a header claiming it tracked the latest release. It is now byte-identical to the published formula from the class declaration onward, so a diff between the two is a real finding rather than noise. The cause was process, not carelessness: docs/releasing.md mentioned the tap only under one-time setup, never in the numbered list of things to do when cutting a release. It is now step 7, which is what stops this recurring. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Follow-up to the 0.8.0 release. The live tap is already updated at BootIntel/homebrew-tap@eca8bf0; this fixes the repo side.
Two things
The in-repo reference copy was stale. It sat at
0.5.0while 0.6.0, 0.6.1 and 0.7.0 shipped, under a header claiming it tracked the latest release. It advertised checksums for archives nobody would install. It is now byte-identical to the published formula from theclass Bootinteldeclaration onward, so a diff between the two is a real finding rather than noise.The cause was the checklist, not carelessness.
docs/releasing.mdmentioned the tap only under one-time setup, never in the numbered list for cutting a release. It is now step 7, which is the part that stops this recurring.On the checksums
They were read out of the release's
SHA256SUMSand paired with eachurlline programmatically, not transcribed. A wrong digest makesbrew installfail with a checksum mismatch, which to a user is indistinguishable from a compromised download.The x86_64-linux archive was independently downloaded, checked against
SHA256SUMS, extracted and run (bootintel 0.8.0,verdictand--interrupt-autobootboth present) before any of this went out.No code changes.
🤖 Generated with Claude Code