Add Lockfile CI Check Verifying Cargo.lock Is Up-to-Date
Description
No CI step verifies Cargo.lock is up-to-date with Cargo.toml. Adding or removing dependencies without updating the lockfile could cause unreproducible builds. Should run cargo check --locked.
Requirements & Context
Add cargo check --locked step. Fail CI if lockfile is stale. Add workflow_dispatch trigger for manual lockfile updates.
Suggested Execution
Branch: ix/ci-lockfile-check
Implement Changes
(1) Add cargo check --locked to contract-ci.yml (2) Add cargo check --locked to release.yml (3) Document lockfile maintenance (4) Add step comment
Test & Commit
Modify Cargo.toml without updating Cargo.lock, verify CI fails.
Example Commit Message
ix(ci): add cargo check --locked step to verify Cargo.lock is up-to-date with Cargo.toml
Guidelines
- Run cargo check --locked before building
- Fail CI if lockfile is stale
Add Lockfile CI Check Verifying Cargo.lock Is Up-to-Date
Description
No CI step verifies Cargo.lock is up-to-date with Cargo.toml. Adding or removing dependencies without updating the lockfile could cause unreproducible builds. Should run cargo check --locked.
Requirements & Context
Add cargo check --locked step. Fail CI if lockfile is stale. Add workflow_dispatch trigger for manual lockfile updates.
Suggested Execution
Branch: ix/ci-lockfile-check
Implement Changes
(1) Add cargo check --locked to contract-ci.yml (2) Add cargo check --locked to release.yml (3) Document lockfile maintenance (4) Add step comment
Test & Commit
Modify Cargo.toml without updating Cargo.lock, verify CI fails.
Example Commit Message
ix(ci): add cargo check --locked step to verify Cargo.lock is up-to-date with Cargo.toml
Guidelines