Skip to content

fix: sync release Cargo.lock on scheduled and manual runs - #115

Merged
owjs3901 merged 1 commit into
mainfrom
fix/release-lock-sync-events
Nov 2, 2026
Merged

owjs3901 merged 1 commit into
mainfrom
fix/release-lock-sync-events

Conversation

@owjs3901

@owjs3901 owjs3901 commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

Problem

CI run https://github.com/dev-five-git/devup-mcp/actions/runs/41421038728 fails at cargo metadata --locked: version PR #109 bumped the workspace to 0.19.0 but left all four workspace packages at 0.18.2 in Cargo.lock.

The version PR was generated by scheduled run https://github.com/dev-five-git/devup-mcp/actions/runs/41398519998. Its changepacks step had DEVUP_RELEASE_LOCK_SYNC: false: our synchronization was restricted to push events, while changepacks/action creates version commits whenever it runs on the base branch, including schedule and workflow_dispatch.

Changes

  • Enable the Rust toolchain and existing same-commit lockfile adapter for all main-branch events, matching changepacks/action's behavior.
  • Synchronize the four workspace package versions in Cargo.lock to 0.19.0. External dependencies are unchanged.

Validation

  • Reproduced the original cargo metadata --locked --format-version 1 failure before the fix; it passes after the fix.
  • python .github/scripts/test_release_lock.py: passed (real Git/Cargo version commit, no external dependency churn).
  • JavaScript tests used by CI: 79 passed.
  • cargo fmt --all -- --check and git diff --check: passed.
  • cargo test --locked --workspace --all-features: blocked before tests by the local Clang C compiler failing to compile libwebp-sys 0.9.6 SIMD intrinsics (missing ssse3/sse4.1 target features). Full Rust verification remains for PR CI.

@owjs3901
owjs3901 merged commit 6cdd6d4 into main Nov 2, 2026
9 checks passed
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