Fix version mismatch breaking Homebrew upgrades#19
Merged
bluestreak01 merged 1 commit intomasterfrom Apr 15, 2026
Merged
Conversation
…w formula
The compiled binary, .deb, and .rpm packages were all stuck at the
Cargo.toml version (0.1.0) regardless of the release tag. This broke
Homebrew upgrades because the formula version didn't match the binary,
and prevented `brew upgrade` from working.
- Patch Cargo.toml version from the release tag before building
(both build and linux-packages jobs)
- Accept tags with or without `v` prefix (e.g. 0.1.2 and v0.1.2)
- Use actual RELEASE_TAG in Homebrew download URLs instead of
hardcoded `v{{VERSION}}` to handle both tag styles
Co-Authored-By: Claude Opus 4.6 (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.
Summary
buildandlinux-packagesjobs, so the compiled binary (CARGO_PKG_VERSION),.deb, and.rpmpackages all carry the correct release version instead of the stale0.1.0vprefix — the workflow now triggers on bothv0.1.3and0.1.3style tags{{RELEASE_TAG}}in Homebrew formula download URLs instead of hardcodedv{{VERSION}}, so the URLs always match the actual GitHub release tag regardless of prefix styleProblem
Homebrew formula version was set correctly from the git tag, but the installed binary reported
0.1.0(from Cargo.toml which was never bumped). This version mismatch causedbrew upgradeto malfunction. Additionally,.deb/.rpmpackages were always versioned as0.1.0.Test plan
v0.1.3) and verify the release workflow passesCARGO_PKG_VERSIONbrew upgrade questdb/middle-manager/mmworks after the tap PR is merged.deband.rpmfilenames contain the release version🤖 Generated with Claude Code