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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This configuration change to
"versioning": "always-bump-minor"will ensure that every release triggered from themainbranch increments the minor version (e.g., fromx.Y.ztox.(Y+1).0).This means that changes that might traditionally be considered
fix(patch-level) if on a release branch, will also result in a minor version bump when merged and released frommain.Could you confirm that this is the desired and fully understood behavior for all types of changes culminating in a release from the
mainbranch? This approach simplifies versioning onmainbut means that the semantic distinction between patch and minor changes is effectively deferred to release branches (which are configured foralways-bump-patch).