open-standards/eoc/eoc-rs/crates/eoc-tools
Repository files (latest commit first)
Filename Latest commit message Latest commit date
David Charlot ad49173ff8
All checks were successful
jouleclaw public surface must stay documented / Public-surface audit (jouleclaw-rs) (pull_request) Successful in 58s
no-vanity-metrics / Scan committed Markdown for vanity metrics (pull_request) Successful in 3s
WAI conformance / cargo-class corpora · linux-arm64 (pull_request) Successful in 1m6s
WAI conformance / cargo-class corpora · windows (pull_request) Successful in 1m15s
WAI conformance / cross-arch byte-equality · linux-arm64 (pull_request) Successful in 23s
WAI conformance / cargo-class corpora · linux (pull_request) Successful in 28s
WAI conformance / cross-arch byte-equality · windows (pull_request) Successful in 22s
WAI conformance / cross-arch byte-equality · linux (pull_request) Successful in 14s
WAI conformance / cargo-class corpora · macos (pull_request) Successful in 2m17s
WAI conformance / cross-arch byte-equality · macos (pull_request) Successful in 24s
eoc: pin rand off 0.10.2, which does not compile
`rand 0.10.2` fails to build: its own `src/rng.rs:168` contains `use
rand::RngExt;` — a crate referring to itself by name rather than `crate::`. That
is an upstream defect in a published release, not a configuration problem, and
it reaches this workspace through `eoc-route-learned`, `eoc-spec-decode` and
`rand_distr`. Pinned to 0.10.1, which builds.

The lock is pinned rather than the manifests: the constraint is "not this exact
release", not a new minimum, and a manifest pin would outlive the broken version
and quietly hold the workspace back once upstream fixes it.

Verified pre-existing rather than assumed: 0.10.2 is in the lock at
`origin/main` and this branch's other commits touch zero `rand` lines.

The `eoc-tools` reqwest `query` feature — the other half of what kept
`cargo check --workspace` from passing — landed on main independently while this
branch was in flight, with the same fix and the same reasoning. That commit is
taken as-is here rather than duplicated.

With both in place the entire eoc-rs workspace checks clean, which is what makes
the allocation and rating work in the preceding commits verifiable in place
rather than only crate-locally.
2026-08-27 13:32:56 -04:00
..
src ingest batch 4: 9 crates · table-stakes completers across all three workspaces 2026-05-24 04:00:04 -04:00
tests ingest batch 4: 9 crates · table-stakes completers across all three workspaces 2026-05-24 04:00:04 -04:00
Cargo.toml eoc: pin rand off 0.10.2, which does not compile 2026-08-27 13:32:56 -04:00