chore: release v0.22.0#242
Closed
github-actions[bot] wants to merge 2 commits intomainfrom
Closed
Conversation
github-actions
Bot
force-pushed
the
release-plz-2026-04-27T12-26-53Z
branch
3 times, most recently
from
af86887 to
c63fedc
Compare
2 tasks
zeitlinger
added a commit
that referenced
this pull request
May 8, 2026
## Summary - Pass `--git-token` and `--forge github` to `release-plz release` and `release-plz release-pr` from the workflow as usage args. - Extract `release:pr` from inline `mise.toml` to `.mise/tasks/release/pr` so it can forward variadic args the same way `release:create` already does. ## Why release-plz 0.3.x requires explicit `--git-token` and `--forge` for both `release` and `release-pr`. Without them, both fail with: ```text ERROR git release not configured. Did you specify git-token and forge? ``` Every release-plz workflow run since [#234](#234) has been failing for that reason, leaving release PR [#242](#242) stuck on its 2026-04-28 snapshot. After this merges, the next push to `main` will refresh #242 with all merged commits since. ## Test plan - [ ] CI green on this PR - [ ] After merge, next push to `main` refreshes #242 with all merged commits + correct version bump (note: `#270` was `refactor!` so the bump should be a major increment per release-plz semantics) --------- Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
github-actions
Bot
force-pushed
the
release-plz-2026-04-27T12-26-53Z
branch
from
c63fedc to
12fe759
Compare
2 tasks
zeitlinger
added a commit
that referenced
this pull request
May 8, 2026
## Summary - Drop `#MISE depends=["release:update"]` from `.mise/tasks/release/pr`. ## Why `release-plz release-pr` already runs `update` internally. Chaining `release:update` as a `depends` made every CI run bump and regenerate the changelog **twice**. Visible symptom: release PR [#242](#242) currently shows `v0.23.0` with every PR since project start in the changelog. The first successful release-plz run after [#274](#274) merged actually computed the right thing — the run log shows: ``` INFO determining next version for flint 0.21.0 INFO flint: next version is 0.22.0 * flint: 0.21.0 -> 0.22.0 ``` …and then the chained second `update` (via `release-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:update` stays available for local manual previews. ## After merge The next push to `main` should refresh #242 to `v0.22.0` with only commits since `v0.21.0`. ## Test plan - [ ] CI green on this PR - [ ] After merge, release PR #242 retitles to `chore: release v0.22.0` and changelog scope shrinks to commits since `v0.21.0` Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
github-actions
Bot
force-pushed
the
release-plz-2026-04-27T12-26-53Z
branch
from
12fe759 to
e130a0f
Compare
Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
2 tasks
zeitlinger
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
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.
🤖 New release
flint: 0.21.0 -> 0.22.0Changelog
This PR was generated with release-plz.