You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix the bump-version-release skill so a version bump updates the workspace version in both required places, not just one.
Step 2b previously said "only change the version line — do not modify anything else", which left the internal path-dependency version requirements under [workspace.dependencies] (mega-evm, mega-state-test, mega-system-contracts) stale.
Because these crates are published to crates.io, Cargo resolves a path dependency by its version requirement (not the path) when publishing, so a stale requirement lets a published new-version crate resolve against an older sibling instead of the coordinated set.
Step 2b now requires bumping [workspace.package].version and the path-dependency requirements in lockstep, and adds a pre-commit grep -n '<old_version>' Cargo.toml check that should print nothing.
Context
The v1.6.1 release (chore: bump version to 1.6.1 #317) hit exactly this: only [workspace.package].version was bumped, and the Codex PR reviewer flagged the desync (P2). It was confirmed real and fixed in that PR before merge.
The v1.6.0 bump (be4418d) had correctly moved these same lines 1.5.1 → 1.6.0, so lockstep is the established practice.
Small, targeted fix for a real regression path. The three-crate list matches the current [workspace.dependencies] block, and the trailing grep check serves as a safety net in case new published crates are added later and the list drifts. The explanation of why version requirements matter at publish time (path is ignored, version requirement wins) is exactly the right context to give an AI agent following this skill.
Label check: The comp:misc label looks like a mismatch for this PR.
This PR only modifies .claude/skills/bump-version-release/SKILL.md, which is a markdown documentation file. The comp:doc label ("Changes in the documentation") fits better than comp:misc ("Changes to the miscellaneous part of this repo").
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
api:unchangedNo change to the public interface or APIcomp:miscChanges to the miscellaneous part of this repospec:unchangedNo change to any `mega-evm`'s behavior
2 participants
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.
RealiCZ
added
spec:unchanged
Summary
bump-version-releaseskill so a version bump updates the workspace version in both required places, not just one.versionrequirements under[workspace.dependencies](mega-evm,mega-state-test,mega-system-contracts) stale.versionrequirement (not the path) when publishing, so a stale requirement lets a published new-version crate resolve against an older sibling instead of the coordinated set.[workspace.package].versionand the path-dependency requirements in lockstep, and adds a pre-commitgrep -n '<old_version>' Cargo.tomlcheck that should print nothing.Context
[workspace.package].versionwas bumped, and the Codex PR reviewer flagged the desync (P2). It was confirmed real and fixed in that PR before merge.be4418d) had correctly moved these same lines1.5.1 → 1.6.0, so lockstep is the established practice.