[obsolete] wai-pack: the lock still named wai-quantum 0.3.36 #182

Closed
dcharlot wants to merge 1 commit from fix/wai-pack-lock into main
Owner

wai-quantum went to 0.3.37 in #176; wai/wai-pack/Cargo.lock still named
0.3.36 for that path dependency. The wai-pack jobs build with --locked, so
all five of them fail:

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. cargo metadata --locked fails in a clean
checkout of main as well. It did not show up 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 — so it only surfaces on a PR whose delta does,
which is where I hit it (#165 and #177 both failed wai-pack · linux-arm64 for
this and nothing else).

One line. I checked every other tracked lock the same way: 30 pass
cargo metadata --locked --offline, and the only other that does not is
jouledesk/jouledesk-rs/vendor/libwebrtc, a vendored third-party tree no job
gates. So this is the whole of it, not one instance of a pattern.

cargo test --locked in wai/wai-pack passes with the corrected lock.

🤖 Generated with Claude Code

`wai-quantum` went to 0.3.37 in #176; `wai/wai-pack/Cargo.lock` still named 0.3.36 for that path dependency. The `wai-pack` jobs build with `--locked`, so all five of them fail: ``` 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`.** `cargo metadata --locked` fails in a clean checkout of main as well. It did not show up 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 — so it only surfaces on a PR whose delta does, which is where I hit it (#165 and #177 both failed `wai-pack · linux-arm64` for this and nothing else). One line. I checked every other tracked lock the same way: 30 pass `cargo metadata --locked --offline`, and the only other that does not is `jouledesk/jouledesk-rs/vendor/libwebrtc`, a vendored third-party tree no job gates. So this is the whole of it, not one instance of a pattern. `cargo test --locked` in `wai/wai-pack` passes with the corrected lock. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
wai-pack: the lock still named wai-quantum 0.3.36
All checks were successful
standards workspaces build + test / jouleclaw-rs (pull_request) Successful in 6m40s
standards workspaces build + test / aac-rs (pull_request) Successful in 2m47s
standards workspaces build + test / joule-code-rs (pull_request) Successful in 1m34s
standards workspaces build + test / joulecontract-rs (pull_request) Successful in 1m8s
standards workspaces build + test / map-rs (pull_request) Successful in 51s
standards workspaces build + test / mesh-rs (pull_request) Successful in 1m26s
standards workspaces build + test / openpay (pull_request) Successful in 4m12s
wai-pack / wai-pack · linux-arm64 (pull_request) Successful in 1m38s
standards workspaces build + test / jouledesk-rs (pull_request) Successful in 3m36s
standards workspaces build + test / macOS energy backends (pull_request) Successful in 5m33s
wai-pack / wai-pack · macos (pull_request) Successful in 2m18s
standards workspaces build + test / arl-rs (pull_request) Successful in 1m12s
standards workspaces build + test / eoc-rs (pull_request) Successful in 1m58s
standards workspaces build + test / jcp-rs (pull_request) Successful in 1m30s
standards workspaces build + test / joule-ui-rs (pull_request) Successful in 1m13s
standards workspaces build + test / joulehook-rs (pull_request) Successful in 1m14s
standards workspaces build + test / proof-rs (pull_request) Successful in 1m21s
standards workspaces build + test / sandbox-rs (pull_request) Successful in 2m24s
standards workspaces build + test / sense-rs (pull_request) Successful in 1m6s
standards workspaces build + test / smart-byte-rs (pull_request) Successful in 3m37s
wai-pack / wai-pack · linux (pull_request) Successful in 1m4s
wai-pack / wai-pack · independent verifier (Python) (pull_request) Successful in 1m39s
wai-pack / wai-pack · the floor through a media prober (pull_request) Successful in 28s
wai-pack / wai-pack · dependency licences (pull_request) Successful in 1m7s
787fc4fe04
`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 <[email protected]>
dcharlot changed title from wai-pack: the lock still named wai-quantum 0.3.36 to [obsolete] wai-pack: the lock still named wai-quantum 0.3.36 2026-10-08 10:26:46 -04:00
dcharlot closed this pull request 2026-10-08 10:26:47 -04:00
All checks were successful
standards workspaces build + test / jouleclaw-rs (pull_request) Successful in 6m40s
standards workspaces build + test / aac-rs (pull_request) Successful in 2m47s
standards workspaces build + test / joule-code-rs (pull_request) Successful in 1m34s
standards workspaces build + test / joulecontract-rs (pull_request) Successful in 1m8s
standards workspaces build + test / map-rs (pull_request) Successful in 51s
standards workspaces build + test / mesh-rs (pull_request) Successful in 1m26s
standards workspaces build + test / openpay (pull_request) Successful in 4m12s
wai-pack / wai-pack · linux-arm64 (pull_request) Successful in 1m38s
standards workspaces build + test / jouledesk-rs (pull_request) Successful in 3m36s
standards workspaces build + test / macOS energy backends (pull_request) Successful in 5m33s
wai-pack / wai-pack · macos (pull_request) Successful in 2m18s
standards workspaces build + test / arl-rs (pull_request) Successful in 1m12s
standards workspaces build + test / eoc-rs (pull_request) Successful in 1m58s
standards workspaces build + test / jcp-rs (pull_request) Successful in 1m30s
standards workspaces build + test / joule-ui-rs (pull_request) Successful in 1m13s
standards workspaces build + test / joulehook-rs (pull_request) Successful in 1m14s
standards workspaces build + test / proof-rs (pull_request) Successful in 1m21s
standards workspaces build + test / sandbox-rs (pull_request) Successful in 2m24s
standards workspaces build + test / sense-rs (pull_request) Successful in 1m6s
standards workspaces build + test / smart-byte-rs (pull_request) Successful in 3m37s
wai-pack / wai-pack · linux (pull_request) Successful in 1m4s
wai-pack / wai-pack · independent verifier (Python) (pull_request) Successful in 1m39s
wai-pack / wai-pack · the floor through a media prober (pull_request) Successful in 28s
wai-pack / wai-pack · dependency licences (pull_request) Successful in 1m7s

Pull request closed

Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Transaction-Science/open-standards!182
No description provided.