fix: versioning scheme — patch bump for all commits except feat#100
Merged
Conversation
…except feat Change version bumping strategy: - feat: → minor version bump (0.11.0 → 0.12.0) - Any other conventional commit (refactor, fix, chore, docs, perf, etc.) → patch bump (0.11.0 → 0.11.1) - Breaking changes → major bump (capped to minor for pre-1.0) - No conventional commits → no release This ensures that housekeeping commits (refactor, docs, chore) still trigger a patch release, keeping changelogs and releases up-to-date with all work.
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
Update auto-release versioning to treat all conventional commits equally for patch bumping:
This ensures every merged PR (including refactors, docs, chores) gets a release, keeping version numbers and changelogs properly synchronized with actual work merged.
Test plan