v0.3.1

v0.3.1 — verifiable release build provenance

This unstable maintenance release adds GitHub Actions artifact attestations.
There are no conversion, native API, CLI, browser/Node API or PDF behavior
changes from v0.3.0, and no new breaking changes.

Downloads and verification

The same 50 native OS/CPU/ABI archives, browser/Node JS package, standalone
WASM and ten-platform OCI archive are provided. Names use v0.3.1 for native
archives and caj2pdf-rust-0.3.1.tgz for the JS package. GHCR is
ghcr.io/rwv/caj2pdf-rust:v0.3.1; prefer its verified immutable digest.

RELEASE-PROVENANCE.sigstore.json authenticates all release payloads and
SHA256SUMS. CONTAINER-PROVENANCE.sigstore.json authenticates the registry
image digest, and is also published as an OCI attestation. These two signature
bundles are not listed in SHA256SUMS; verify their signatures with gh attestation verify. All other uploaded files are covered by the signed
checksum manifest. GitHub-generated source archives are outside this set.

See the verification guide for commands enforcing
repository, workflow, tag and commit identity. The publisher verifies every
file and the registry attestation before exposing the GitHub release. A
modified-file rejection check is mandatory. This is release-workflow provenance
from the aggregation job, not a claim of SLSA level 3 or platform code signing.
Earlier published releases are unchanged.

Existing limits

The v0.3.0 platform and format limits still apply, including
runtime/libc baselines, caller-supplied experimental HN/C8 tables and deferred
candidate architectures. Browser and Node are both supported. Native archives
include MIT dependency notices; macOS/Windows executables have no platform
code signatures. No npm, crates.io or Docker Hub publication is included.

Release CI reruns required native, WASM, JS, license, coverage and platform
checks. The private CAJSamples corpus is not shipped or run by public CI;
missing optional-corpus checks remain NOT_RUN, not compatibility passes.