From 787fc4fe044eba0410ebb9a2ce27e69da47a27f8 Mon Sep 17 00:00:00 2001 From: Transaction Science Date: Wed, 7 Oct 2026 14:29:08 -0400 Subject: [PATCH] wai-pack: the lock still named wai-quantum 0.3.36 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit `wai-quantum` went to 0.3.37 in #176; `wai/wai-pack/Cargo.lock` still carried 0.3.36 for that path dependency. The `wai-pack` jobs build with `--locked`, so every one of them failed: error: cannot update the lock file .../wai/wai-pack/Cargo.lock because --locked was passed to prevent this This is a gate failure on **main**, not on any branch — `cargo metadata --locked` fails in a clean checkout of main too. It did not surface on main's own run because the `wai-pack` workflow is `paths:`-filtered and the merge that bumped the version did not touch the filtered paths; it surfaces on any PR whose delta does, which is where I hit it (#165, #177). One line. Checked the other tracked locks the same way: 30 of them pass `--locked --offline`, and the only other that does not is `jouledesk/jouledesk-rs/vendor/libwebrtc`, a vendored third-party tree that no job gates. So this is the whole of it rather than one instance of a pattern. `cargo test --locked` in `wai/wai-pack` passes with it. Co-Authored-By: Claude Opus 5 --- wai/wai-pack/Cargo.lock | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/wai/wai-pack/Cargo.lock b/wai/wai-pack/Cargo.lock index e0160c91d..d180e0582 100644 --- a/wai/wai-pack/Cargo.lock +++ b/wai/wai-pack/Cargo.lock @@ -682,7 +682,7 @@ dependencies = [ [[package]] name = "wai-quantum" -version = "0.3.36" +version = "0.3.37" dependencies = [ "blake3", "ed25519-dalek", -- 2.54.0 (Apple Git-157)