Skip to content

feat(release-candidate): bump_command for lockfiles and lockstep versions - #25

Merged
Troublor merged 1 commit into
mainfrom
troublor/feat/bump-command
Sep 8, 2026
Merged

Troublor merged 1 commit into
mainfrom
troublor/feat/bump-command

Conversation

@Troublor

@Troublor Troublor commented Sep 7, 2026

Copy link
Copy Markdown
Collaborator

Needed by every repo in the core-migration scope (salt, stateless-validator, mega-evm, mega-reth): a single version-file rewrite leaves Cargo.lock stale, and mega-evm pins three path dependencies to the workspace version.

  • New bump_command input on release-candidate: runs after the version-file rewrite, in the repo root, under bash -euo pipefail, with OLD_VERSION / NEW_VERSION in the environment. Whatever it changes is committed with the bump.
  • Guard: the action re-reads the version file afterwards and fails if the command undid the bump.
  • Toolchain is the caller's job (composite action runs in the caller's job) — e.g. install Rust before the step for cargo update --workspace.
  • Template comment + README.

YAML + shellcheck clean; release-tools tests unchanged (15 pass).

🤖 Generated with Claude Code

…ions

A single version-file rewrite is not enough for most Rust repos: Cargo.lock
must follow, and workspaces that pin path dependencies (mega-evm) carry the
version in several lines. bump_command runs after the rewrite with
OLD_VERSION/NEW_VERSION set; whatever it changes ships in the candidate
commit. The action re-reads the version file afterwards so a command
cannot silently undo the bump.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013eLFMaDpEwgDzyDBzCQzLH
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant