Repository navigation
Bump omarchy-mac's version only in a release's own pull request - #30
Open
scottjones wants to merge 1 commit into
Open
scottjones wants to merge 1 commit into
scottjones wants to merge 1 commit into
Conversation
PRs that each bumped omarchy-mac/version kept colliding (#23 and #24 on 0.1.1, #21 and #28 on 0.1.3) or forgot to bump. Only a release reads the number, through the recipe's pkgver, so the release now sets it: in a pull request from release/omarchy-mac-<version> that changes only that file. A new gate fails any other pull request that touches the file. The README no longer repeats the number. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This was referenced Oct 10, 2026
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
PRs that each bump
omarchy-mac/versionkeep colliding (#23 and #24 on 0.1.1, #21 and #28 on 0.1.3) or forget to bump. Only a release reads the number, through the recipe'spkgver, so the release sets it.The README stops repeating the number. A follow-up teaches
tools/release/mac-release --bump patch|minorto open the bump PR, with a manual Action for it.Evidence
After: the gate fails it, and passes the release bump PR, PRs that leave the version alone, and pushes to main. Checked against seven scratch cases.
Merge Danger
Door: two-way
Open PRs that bump the version (#12, #21, #28) fail the gate until they drop the bump.
Blast Radius: process
@maralcbr this changes the release rule in CONTRIBUTING.md: are you OK with PRs no longer bumping the version, and the releaser choosing patch or minor?
🤖 Generated with Claude Code