fix(release-please): fix footer not appearing on release PRs#40
Merged
zeitlinger merged 1 commit intomainfrom Feb 20, 2026
Merged
fix(release-please): fix footer not appearing on release PRs#40zeitlinger merged 1 commit intomainfrom
zeitlinger merged 1 commit intomainfrom
Conversation
Release-please defaults `separatePullRequests` to `true` for single-package configs, which skips the Merge plugin that applies the configured `pull-request-footer`. Setting `separate-pull-requests` to `false` explicitly forces the Merge plugin to run. Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Adjusts the Release Please configuration so the pull-request-footer is applied to release PRs by ensuring the Merge plugin runs even in a single-package setup.
Changes:
- Set
separate-pull-requests: falsein the Release Please config to force the Merge plugin to run. - Restores expected behavior where
pull-request-footerappears on release PRs.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Member
Author
|
Upstream fix: googleapis/release-please#2685 |
zeitlinger
changed the title
zeitlinger
added a commit
that referenced
this pull request
Feb 20, 2026
…around (#42) ## Summary - Remove `separate-pull-requests: false` added in #40 - That workaround is only needed for Java snapshot PRs (upstream bug: googleapis/release-please#2685) - Flint uses `release-type: simple`, so the footer works without it Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
zeitlinger
pushed a commit
that referenced
this pull request
Feb 23, 2026
🤖 I have created a release *beep* *boop* --- ## [0.7.0](v0.6.0...v0.7.0) (2026-02-23) ### Features * handle line-number anchors and issue comments globally ([#56](#56)) ([cf751df](cf751df)) ### Bug Fixes * **release-please:** fix footer not appearing on release PRs ([#40](#40)) ([d7a55e4](d7a55e4)) * use remap instead of exclude for issue comment anchors ([#58](#58)) ([656f355](656f355)) --- > [!IMPORTANT] > Close and reopen this PR to trigger CI checks. Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.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.
Summary
pull-request-footerwas not being applied to release PRs becauserelease-please defaults
separatePullRequeststotrueforsingle-package configs, which skips the Merge plugin responsible for
applying the footer
separate-pull-requests: falseforces the Merge plugin to runContext
ci(release-please): fix footer not appearing on release PRs prometheus/client_java#1902
Test plan