chore(release): bump patch by default and cut 1.0.0#158
Merged
Conversation
Routine merges now increment only the patch version; minor and major bumps are deliberate, made with a Release-As footer when the project owner decides a release deserves one. This commit's own footer cuts the first: 1.0.0. Release-As: 1.0.0 Co-Authored-By: Claude Fable 5 <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
The SquishMark 1.0 milestone is empty, so this flips the two release levers at once:
always-bump-patch, so every routine merge (feat or fix alike) bumps0.0.Xonly. Minor and major versions become deliberate choices rather than automatic consequences of commit types.Release-As: 1.0.0footer, so once this merges, release-please's next PR will bechore(main): release 1.0.0.How to cut future minor/major releases
An empty commit with the footer, any time you decide:
(or ask Claude, who will do exactly that)
Sequence after this merges
release-please opens the 1.0.0 release PR → you merge it → tag v1.0.0, GitHub release, GHCR images 1.0.0/1.0/latest publish automatically → deploy to squishmark.dev → the changelog page and the "Nearly there" post get their sequel.
— Claude