Closed
Conversation
github-actions
bot
force-pushed
the
release-please--branches--main
branch
from
c8c2d07 to
a280fe1
Compare
github-actions
bot
force-pushed
the
release-please--branches--main
branch
3 times, most recently
from
8ed33fa to
8c44220
Compare
1 task
zeitlinger
added a commit
that referenced
this pull request
Feb 20, 2026
## Summary - `pull-request-footer` was not being applied to release PRs because release-please defaults `separatePullRequests` to `true` for single-package configs, which skips the Merge plugin responsible for applying the footer - Setting `separate-pull-requests: false` forces the Merge plugin to run ## Context - This is a workaround for an upstream bug in release-please where `pull-request-footer` is silently ignored for single-package repos - Affects both regular release PRs and Java SNAPSHOT PRs - Same issue exists in grafana/flint and likely any single-package repo using `pull-request-footer` ## Test plan - [ ] After merging, verify PR #1896 gets updated with the footer on the next release-please run Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
github-actions
bot
changed the title
github-actions
bot
force-pushed
the
release-please--branches--main
branch
from
8c44220 to
ae2d20f
Compare
1 task
zeitlinger
added a commit
that referenced
this pull request
Mar 18, 2026
## Summary - Remove `always-bump-patch` from release-please config so version bumps follow conventional commits (feat → minor, fix → patch) - This fixes the broken release-please PR #1896 which had an empty diff and generic title due to version mismatch ## Context The previous `always-bump-patch` setting conflicted with the manual `1.6.0-SNAPSHOT` bump, causing release-please to get stuck. With default versioning, release-please will correctly propose `1.6.0` based on the `feat:` commits since `1.5.0`. ## Test plan - [ ] After merge, verify release-please creates a new PR with correct version and changelog Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.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.
🤖 I have created a release beep boop
1.5.1-SNAPSHOT
Updating meta-information for bleeding-edge SNAPSHOT release.
Important
Close and reopen this PR to trigger CI checks.