Repository navigation
chore: prepare v2.2.5 release - #499
Merged
calvinbrewer merged 1 commit intoOct 31, 2026
Merged
Conversation
The v2.2.5 release was tagged before the version was bumped, so the release workflow's verify-release job refused it. Bump the workspace version 2.2.4 -> 2.2.5 and promote the Unreleased CHANGELOG entries to [2.2.5].
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.
Why
The v2.2.5 release run failed in Verify release metadata:
The tag was cut on
release/2.2(5f99d7e) before a prepare-release PR bumped the version.The build and publish jobs were skipped, so no 2.2.5 images were published.
What
[workspace.package] versionfrom2.2.4to2.2.5and syncCargo.lock(cargo update --workspace).[Unreleased]CHANGELOG entries to## [2.2.5] - 2026-10-30and update the compare links.Same shape as the v2.2.4 prepare commit (
a239ebc1).The workflow's version/changelog check passes locally against this commit.
After merge
mise run releaseonly runs frommain, so re-cut the release manually:--latest=falsekeepsv3.0.1as the latest release.