| Filename | Latest commit message | Latest commit date |
|---|---|---|
ece3d6cd18
Some checks failed
joule-code conformance gate / joule-moq-relay, its own energy on a counter (macos) (push) Successful in 49s
joule-code conformance gate / Build + round-trip C1-C4 vectors (push) Successful in 2m44s
repository checks / lockfiles, advisories, tests in CI, workflow hygiene, spec and section references, public text (push) Has been cancelled
joule-code conformance gate / joule-moq-relay, every target (push) Successful in 10m44s
joule-code conformance gate / joule-moq-ingest, every target (push) Successful in 14m39s
joule-moq-room room service / joule-moq-room · does this change touch it (push) Has been cancelled
joule-moq-room room service / joule-moq-room, every target (push) Has been cancelled
joule-moq-web browser client / joule-moq-web · does this change touch it (push) Has been cancelled
joule-moq-web browser client / joule-moq-web · browser end-to-end (macos) (push) Has been cancelled
wai-app and Create / wai-app · does this change touch it (push) Has been cancelled
wai-app and Create / wai-app · tests, clippy, the line language's verifier (linux) (push) Has been cancelled
wai-app and Create / wai-app · Create, browser end-to-end (macos) (push) Has been cancelled
WAI Studio / does this change touch it (push) Has been cancelled
WAI Studio / the catalogue's actions, the unit tests and the core · linux (push) Has been cancelled
WAI Studio / Studio in Chromium and Firefox · macos (push) Has been cancelled
WAI Studio / Studio in WebKit · linux (push) Has been cancelled
str0m =0.24.1 ran its DTLS on p256 and p384 0.13 over elliptic-curve 0.13, which holds crypto-bigint at 0.5.5 (RUSTSEC-2026-0387), and no 0.5 release is patched. str0m 0.25.0, with str0m-rust-crypto 0.7, str0m-proto 0.8 and dimpl 0.9, runs on p256 and p384 0.14 over elliptic-curve 0.14 and crypto-bigint 0.7.10: `cargo tree -p joule-moq-ingest -i [email protected]` matches nothing in joule-code-rs. The copy left in that lock and in joule-moq-room's comes through openmls (joule-moq-mls, joule-code-collab's tests), so check-advisories.py's version-pinned allowance still holds, as written. Both locks were regenerated by `cargo update -p str0m`; every crate new to them is MIT or Apache-2.0, none yanked. The gateway's code is unchanged. The README said the WebRTC stack links no C library; it builds one, aws-lc, before and after: dimpl's certificate feature makes each session's DTLS certificate with rcgen on aws-lc-rs. It now says so. Framework, Rust 1.99.1: cargo test --locked -p joule-moq-ingest --all-targets, the same with --features rist, joule-contrib --all-targets with and without rist, the link-vectors --check, joule-moq-room cargo test --locked --all-targets, check-lockfiles.sh on both, and check-advisories.py over every lock. Co-Authored-By: Claude Opus 5.5 <[email protected]> |
||
| .. | ||
| joule-code-cargo | ||
| joule-code-cascade | ||
| joule-code-collab | ||
| joule-code-conformance | ||
| joule-code-identity | ||
| joule-code-jcp | ||
| joule-code-joulecontract | ||
| joule-code-receipt | ||
| joule-code-release | ||
| joule-code-remediate | ||
| joule-code-review | ||
| joule-code-reviewer | ||
| joule-code-schema | ||
| joule-code-spec | ||
| joule-contrib | ||
| joule-moq | ||
| joule-moq-ingest | ||
| joule-moq-interop | ||
| joule-moq-mls | ||
| joule-moq-relay | ||
| joule-moq-remote | ||
| joule-moq-room | ||
| joule-moq-web | ||
| jwp | ||
| lockstep-quic | ||