chore(homebrew): point the formula at v0.10.3 - #1579
Open
DeusData wants to merge 1 commit into
Open
Conversation
The formula still pinned 0.8.1 — five releases and two months behind — so `brew install` handed out a June binary while GitHub, npm and PyPI all served the current one. Nothing in the release pipeline touches this file, which is how it drifted that far without anyone noticing. Version and all four SHA-256 digests come from the published v0.10.3 checksums.txt. Worth doing separately: have the release workflow rewrite this formula from checksums.txt after publish. A channel nothing updates is a channel that rots, and the failure mode is silent — brew keeps working, it just installs something old. Signed-off-by: Martin Vogel <martin.vogel.tech@gmail.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.
The formula still pinned 0.8.1 — five releases and two months behind — so
brew installhanded out a June binary while GitHub, npm and PyPI all served the current one. Nothing in the release pipeline touches this file, which is how it drifted that far unnoticed.Version plus all four SHA-256 digests taken from the published v0.10.3
checksums.txt.Worth its own change: have the release workflow rewrite the formula from
checksums.txtafter publish. A channel nothing updates is a channel that rots, and this failure mode is silent —brewkeeps working, it just installs something old.(Supersedes #1549, which targeted v0.10.2 and is now stale.)