chore: use default versioning for release-please#1949
Merged
zeitlinger merged 1 commit intomainfrom Mar 18, 2026
Merged
Conversation
Remove `always-bump-patch` so release-please uses conventional commits to determine the version bump (feat → minor, fix → patch). Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
jaydeluca
approved these changes
Mar 17, 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
2 participants
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
always-bump-patchfrom release-please config so version bumps follow conventional commits (feat → minor, fix → patch)Context
The previous
always-bump-patchsetting conflicted with the manual1.6.0-SNAPSHOTbump, causing release-please to get stuck. With default versioning, release-please will correctly propose1.6.0based on thefeat:commits since1.5.0.Test plan