Skip to content

ci: assert the root Cargo.lock is in sync #7589

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
matthewevans merged 1 commit into from
Aug 21, 2026
+7 −1
Merged

ci: assert the root Cargo.lock is in sync #7589

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion .github/workflows/ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,8 +57,14 @@ jobs:
- name: Check formatting
run: cargo fmt --all -- --check

# `--locked` costs nothing here (this step already resolves the whole
# workspace) and asserts the committed root Cargo.lock is in sync with the
# manifests. Without it, dropping a crate leaves dead entries in the lock,
# every later cargo invocation silently rewrites the file, and Nightly
# Release dies on `cargo release`'s dirty-tree check -- which is exactly
# what #7556 did. `--locked` is already used for the Tauri manifest below.
- name: Clippy
run: cargo clippy --workspace --exclude phase-tauri --all-targets --features engine/proptest -- -D warnings
run: cargo clippy --locked --workspace --exclude phase-tauri --all-targets --features engine/proptest -- -D warnings

- name: Interaction bindings are current
run: ./scripts/check-interaction-bindings.sh --check
Expand Down
Loading