Exact

Exact Union RegExp

Repository files (latest commit first)

Filename	Latest commit message	Latest commit date
David Charlot d5ec1abe1b wai: run the C2PA emitter in CI, and drop its system-crypto dependency ... Two gaps in the emitter as first written, both of the same kind: a claim with nothing checking it. **The tests never ran.** `c2pa_emit` is off by default and the four-platform `cargo-classes` job builds a fixed feature list that does not include it, so the seven tests compiled locally and nowhere else. A feature no workflow enables has no coverage at all — the suite passes and the tests in it simply do not run. This adds a job that enables it. One platform, deliberately. Everything the existing matrix exists to prove is about byte-identical reconstruction across architectures; a signed manifest makes no such claim and would not become more true for being emitted on four machines. **It linked system OpenSSL.** The c2pa SDK defaults to an openssl backend plus four HTTP stacks. Every wai workflow is built on "pure Rust, no system dependencies" — that is what lets the conformance matrix run on Linux, macOS and Windows with no setup — and an openssl-linked optional feature quietly puts a system library back in the crate's reach. Switched to the SDK's `rust_native_crypto` backend with `default-features = false`, which also drops the reqwest/ureq/wstd/wasi chain that local emission never uses. `openssl`, `openssl-sys`, `reqwest` and `ureq` are all absent from the graph, and the seven tests pass unchanged. Both properties are now asserted rather than assumed, because both are the kind that decay silently: - a step fails if `openssl` or `openssl-sys` ever reaches the `c2pa_emit` graph, since an openssl-linked build would still pass every test here while making the crate undistributable to a bare runner; - a step fails if `c2pa` ever becomes reachable from `provenance`, since that would hand a large dependency tree to consumers who wanted only the binding types, and falsify the "off by default" claim in the extension. The guards were checked to discriminate, not merely to pass: `cargo tree -i` was confirmed to detect a dependency that IS present, so a guard that silently stopped working could not read as a green check. Co-Authored-By: Claude Opus 5 <[email protected]>		2026-09-06 06:26:10 -04:00
..
workflows	wai: run the C2PA emitter in CI, and drop its system-crypto dependency	2026-09-06 06:26:10 -04:00