fix(ci): drop double release-plz update from release:pr#276
Merged
zeitlinger merged 1 commit intomainfrom May 8, 2026
Merged
Conversation
release-plz release-pr already runs update internally. Chaining release:update as a depends made every CI run bump twice and regenerate the changelog twice, which is why release PR #242 ended up at v0.23.0 with every PR since project start in the changelog (instead of v0.22.0 with just commits since v0.21.0). release:update stays available for local manual previews. Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adjusts the release PR automation task to avoid running release-plz update twice during CI-driven release PR updates.
Changes:
- Removes the
release:updatedependency from the.miserelease:prtask to prevent a secondupdaterun duringrelease-plz release-pr.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
1
to
4
| #!/usr/bin/env bash | ||
| #MISE description="Open or update the release PR" | ||
| #MISE depends=["release:update"] | ||
| #USAGE flag "--git-token <token>" help="GitHub token used by release-plz" | ||
|
|
martincostello
approved these changes
May 8, 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
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
#MISE depends=["release:update"]from.mise/tasks/release/pr.Why
release-plz release-pralready runsupdateinternally. Chainingrelease:updateas adependsmade every CI run bump and regenerate the changelog twice.Visible symptom: release PR #242 currently shows
v0.23.0with every PR since project start in the changelog. The first successful release-plz run after #274 merged actually computed the right thing — the run log shows:…and then the chained second
update(viarelease-plz release-pr's internal call) bumped 0.22.0 → 0.23.0 on top of an already-bumped tree, regenerating the whole CHANGELOG.release:updatestays available for local manual previews.After merge
The next push to
mainshould refresh #242 tov0.22.0with only commits sincev0.21.0.Test plan
chore: release v0.22.0and changelog scope shrinks to commits sincev0.21.0