fix(release): regenerate and stage Cargo.lock in create-release #96

Merged

David merged 2 commits from fix/VA-95-create-release-stage-lock into main

2026-07-01 00:40:19 +02:00

David commented

2026-07-01 00:29:43 +02:00

Owner

Fixes VA-95.

The create-release recipe bumped workspace.package.version in Cargo.toml but never updated Cargo.lock, leaving the 7 vervain-agent workspace crates pinned at the old version. The next --locked build (clippy in check.Dockerfile, run by the pre-commit hook on the release commit) failed with cannot update the lock file because --locked was passed, blocking both just pre-commit and just create-release.

This adds {{ compose }}run --rm build cargo update --workspace --offline after the Cargo.toml bump and stages Cargo.lock alongside it, so every future release commit carries a matching lock. The lock regeneration runs in the dev container's build service because the agent dev boxes are toolchain-less (no host cargo). cargo update --workspace is scoped to workspace members, so external deps are untouched.

Mirrors the VS-76 fix in the Vervain Server repo. The v0.2.0 release that hit this bug is unblocked separately in the Release v0.2.0 PR (its Cargo.lock was regenerated by hand).

#VA-95

Fixes VA-95. The `create-release` recipe bumped `workspace.package.version` in `Cargo.toml` but never updated `Cargo.lock`, leaving the 7 `vervain-agent` workspace crates pinned at the old version. The next `--locked` build (clippy in `check.Dockerfile`, run by the pre-commit hook on the release commit) failed with `cannot update the lock file because --locked was passed`, blocking both `just pre-commit` and `just create-release`. This adds `{{ compose }}run --rm build cargo update --workspace --offline` after the `Cargo.toml` bump and stages `Cargo.lock` alongside it, so every future release commit carries a matching lock. The lock regeneration runs in the dev container's `build` service because the agent dev boxes are toolchain-less (no host `cargo`). `cargo update --workspace` is scoped to workspace members, so external deps are untouched. Mirrors the VS-76 fix in the Vervain Server repo. The v0.2.0 release that hit this bug is unblocked separately in the Release v0.2.0 PR (its Cargo.lock was regenerated by hand). #VA-95

David added 1 commit

2026-07-01 00:29:43 +02:00

fix(release): regenerate and stage Cargo.lock in create-release

Check / fmt + clippy + tests (pull_request) Successful in 4m14s

Details

56c103dbe2

The create-release recipe bumped workspace.package.version in Cargo.toml but never updated Cargo.lock, leaving the 7 vervain-agent workspace crates pinned at the old version. The next --locked build (clippy in check.Dockerfile, run by the pre-commit hook) then failed with "cannot update the lock file because --locked was passed", blocking both just pre-commit and just create-release. Regenerate the lock via the dev container's build service (cargo update --workspace --offline, scoped to workspace members) and git add Cargo.lock alongside Cargo.toml so future release commits carry a matching lock. Mirrors the VS-76 fix in the Vervain Server repo, using the container form because the agent dev boxes are toolchain-less.

#VA-95

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

David added 1 commit

2026-07-01 00:35:43 +02:00

Merge branch 'main' into fix/VA-95-create-release-stage-lock

Check / fmt + clippy + tests (pull_request) Successful in 4m33s

Details

Create release / Create release from merged PR (pull_request) Has been skipped

Details

030c18f79b