Transaction-Science/open-standards
Watch
1
0
Fork
You've already forked open-standards
 0
Code Issues Pull requests Projects Releases 15 Packages Wiki Activity Actions 7

[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
pull from: fix/wai-pack-lock
merge into: Transaction-Science:main
Conversation 0 Commits 1 Files changed 1 +1 -1

2026-10-07

Transaction Science
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
Details
standards workspaces build + test / aac-rs (pull_request) Successful in 2m47s
Details
standards workspaces build + test / joule-code-rs (pull_request) Successful in 1m34s
Details
standards workspaces build + test / joulecontract-rs (pull_request) Successful in 1m8s
Details
standards workspaces build + test / map-rs (pull_request) Successful in 51s
Details
standards workspaces build + test / mesh-rs (pull_request) Successful in 1m26s
Details
standards workspaces build + test / openpay (pull_request) Successful in 4m12s
Details
wai-pack / wai-pack · linux-arm64 (pull_request) Successful in 1m38s
Details
standards workspaces build + test / jouledesk-rs (pull_request) Successful in 3m36s
Details
standards workspaces build + test / macOS energy backends (pull_request) Successful in 5m33s
Details
wai-pack / wai-pack · macos (pull_request) Successful in 2m18s
Details
standards workspaces build + test / arl-rs (pull_request) Successful in 1m12s
Details
standards workspaces build + test / eoc-rs (pull_request) Successful in 1m58s
Details
standards workspaces build + test / jcp-rs (pull_request) Successful in 1m30s
Details
standards workspaces build + test / joule-ui-rs (pull_request) Successful in 1m13s
Details
standards workspaces build + test / joulehook-rs (pull_request) Successful in 1m14s
Details
standards workspaces build + test / proof-rs (pull_request) Successful in 1m21s
Details
standards workspaces build + test / sandbox-rs (pull_request) Successful in 2m24s
Details
standards workspaces build + test / sense-rs (pull_request) Successful in 1m6s
Details
standards workspaces build + test / smart-byte-rs (pull_request) Successful in 3m37s
Details
wai-pack / wai-pack · linux (pull_request) Successful in 1m4s
Details
wai-pack / wai-pack · independent verifier (Python) (pull_request) Successful in 1m39s
Details
wai-pack / wai-pack · the floor through a media prober (pull_request) Successful in 28s
Details
wai-pack / wai-pack · dependency licences (pull_request) Successful in 1m7s
Details 
`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]>
787fc4fe04
2026-10-07 14:29:08 -04:00