Skip to content

ci: refresh Cargo.lock in release workflow#54

Merged
ian-pascoe merged 2 commits intomainfrom
feat/cargo-lock-release-workflow-pr
Feb 25, 2026
Merged

ci: refresh Cargo.lock in release workflow#54
ian-pascoe merged 2 commits intomainfrom
feat/cargo-lock-release-workflow-pr

Conversation

@ian-pascoe
Copy link
Contributor

Summary

  • add a lockfile refresh stage to .github/workflows/release-please.yml that checks out code, sets up stable Rust, runs cargo update --workspace, validates with cargo check --workspace --locked, and conditionally commits only Cargo.lock
  • guard Run release-please to avoid self-trigger loops when the workflow-generated lockfile commit is the head commit
  • include the cargo-lock release workflow plan documents from the main workspace under .agents/plans/

Test Plan

  • rg \"Refresh Cargo.lock|cargo check --workspace --locked|chore\\(lockfile\\): refresh Cargo.lock for release\" .github/workflows/release-please.yml
  • rg \"if: .*lockfile.*|if: .*steps\\..*lock_changed\" .github/workflows/release-please.yml
  • python3 -m venv /tmp/crosspack-yaml-verify && /tmp/crosspack-yaml-verify/bin/pip install pyyaml && /tmp/crosspack-yaml-verify/bin/python -c \"import yaml; yaml.safe_load(open('.github/workflows/release-please.yml')); print('ok')\"
  • rustup run stable cargo test --workspace

@ian-pascoe ian-pascoe merged commit fdf08d7 into main Feb 25, 2026
4 checks passed
@ian-pascoe ian-pascoe deleted the feat/cargo-lock-release-workflow-pr branch February 25, 2026 15:35
@crosspack-bot crosspack-bot bot mentioned this pull request Feb 25, 2026
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