joule-moq-room: its lockfile follows wai-quantum 0.6.14 (repository checks red on main since #427) #447
2026-10-22
joule-moq-room: its lockfile follows wai-quantum 0.6.14
All checks were successful
joule-moq-room room service / joule-moq-room · does this change touch it (pull_request) Successful in 6s
joule-moq-web browser client / joule-moq-web · does this change touch it (pull_request) Successful in 5s
joule-code conformance gate / Build + round-trip C1-C4 vectors (pull_request) Successful in 2m43s
joule-code conformance gate / joule-moq-ingest, every target (pull_request) Successful in 4m0s
joule-code conformance gate / joule-moq-relay, every target (pull_request) Successful in 4m16s
standards workspaces build + test / which workspaces this change touches (pull_request) Successful in 22s
repository checks / lockfiles, tests in CI, workflow hygiene, spec and section references, public text (pull_request) Successful in 2m42s
joule-moq-room room service / joule-moq-room, every target (pull_request) Successful in 1m33s
standards workspaces build + test / joule-code-rs (joule-code/joule-code-rs, joule-code-rs, linux-arm64, true) (pull_request) Successful in 4m24s
joule-moq-web browser client / joule-moq-web · browser end-to-end (macos) (pull_request) Successful in 10m17s
standards workspaces build + test / macOS energy backends (pull_request) Successful in 8m6s
#427 moved wai-quantum to 0.6.14, and joule-moq-room path-depends on it, but the room's own Cargo.lock still records 0.6.12. The lockfile step of repository checks has failed on main since then (aa61ab3b,41c5bafba), and so on every pull request, including the security update in #444. Regenerated with the command the check prints: (cd joule-code/joule-code-rs/crates/joule-moq-room && cargo update --workspace) One line changes. No registry crate moves. Co-Authored-By: Claude Opus 5.5 <[email protected]>