fix(release): regenerate Cargo.lock for v2.2.0 (unbreak --locked CI builds)

The v2.2.0 version bump (2.1.27 -> 2.2.0) updated the crate Cargo.toml files
but not Cargo.lock, leaving the lockfile pinning vestige-core/vestige-mcp at
2.1.27. The Release workflow builds with `cargo build --locked`, which refuses
to update the lockfile, so every platform target failed with:

  error: cannot update the lock file ... because --locked was passed

Regenerated via `cargo update -w` (workspace members only, no dependency bumps).
Verified: `cargo build --locked -p vestige-mcp --release` now succeeds.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Sam Valladares 2026-06-29 15:38:57 -05:00
parent b91a7e0bb7
commit 3bcd466744

4
Cargo.lock generated
View file

@ -4897,7 +4897,7 @@ checksum = "0b928f33d975fc6ad9f86c8f283853ad26bdd5b10b7f1542aa2fa15e2289105a"
[[package]]
name = "vestige-core"
version = "2.1.27"
version = "2.2.0"
dependencies = [
"argon2",
"blake3",
@ -4938,7 +4938,7 @@ dependencies = [
[[package]]
name = "vestige-mcp"
version = "2.1.27"
version = "2.2.0"
dependencies = [
"anyhow",
"axum",