ci(release): skip homebrew tap and mcp registry on prerelease tags - #381
Merged
Conversation
Mark GitHub releases as prerelease when the version contains a hyphen (e.g. 2.4.0-beta.1), and gate the update_homebrew_tap and mcp_registry jobs on stable versions only. Without this, a beta tag would overwrite the main Homebrew formula and push beta builds onto every brew install user, and would publish the prerelease to the MCP Registry as if it were the canonical version.
commit: |
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.
Mark GitHub releases as prereleases when the tag carries a SemVer prerelease suffix (e.g.
2.4.0-beta.1), and skip theupdate_homebrew_tapandmcp_registryjobs for those tags.Without this, pushing a beta tag would:
Formula/xcodebuildmcp.rbin thehomebrew-xcodebuildmcptap, pushing everybrew install/brew upgradeuser onto the beta build, andnpm continues to publish under the
beta/alpha/rcdist-tag (the resolver inResolve npm tag from versionis unchanged), and the portable tarballs are still attached to the GitHub release. Only the channels that have no separate prerelease lane are gated.The condition uses
contains(..., '-')because every SemVer prerelease has a-and no stable release does, matching the validation regex inGet version from tag or input.