fix: allow feat commits to bump minor version in pre-1.0.0 releases#49
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
This PR fixes the release-please configuration to enable proper semantic versioning for pre-1.0.0 releases by removing the bump-patch-for-minor-pre-major setting. This allows feat: commits to bump the minor version (e.g., 0.1.1 → 0.2.0) instead of only the patch version (0.1.1 → 0.1.2), making it possible to distinguish between feature releases and patch releases in version numbers.
Key Changes
- Removes the conflicting
bump-patch-for-minor-pre-major: truesetting that was preventing proper semantic versioning - Retains
bump-minor-pre-major: trueto ensure breaking changes bump the minor version for pre-1.0.0 releases
jcouball
force-pushed
the
fix-release-please-version-bump
branch
2 times, most recently
from
December 18, 2025 17:56
d2a830a to
c9ca72c
Compare
Remove bump-patch-for-minor-pre-major setting to restore standard semantic versioning behavior for pre-1.0.0 versions. With this change: - feat: commits bump minor version (0.1.1 → 0.2.0) - BREAKING CHANGE: commits bump minor version (0.1.1 → 0.2.0) - fix: commits bump patch version (0.1.1 → 0.1.2) Previously, bump-patch-for-minor-pre-major caused feat: commits to only bump patch versions, which prevented proper version signaling for new features in pre-1.0.0 releases.
jcouball
force-pushed
the
fix-release-please-version-bump
branch
from
December 18, 2025 17:59
c9ca72c to
3581f05
Compare
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
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.
Problem
Release-please was configured with
bump-patch-for-minor-pre-major: true, which causedfeat:commits to only bump the patch version (0.1.1 → 0.1.2) instead of the minor version (0.1.1 → 0.2.0) for pre-1.0.0 releases.This made it impossible to distinguish between feature releases and patch releases in version numbers.
Solution
Remove the
bump-patch-for-minor-pre-majorsetting from.release-please-config.json.Impact
After this change, version bumping will work as follows for versions < 1.0.0:
feat:BREAKING CHANGE:fix:For versions ≥ 1.0.0, standard semantic versioning applies (BREAKING CHANGE bumps major).
Next Steps
Once this PR is merged, the next release-please run should correctly suggest version 0.2.0 instead of 0.1.2 for the pending release that includes multiple feature commits.