v0.4.0

@libid/claim and @libid/claim-full 0.4.0.

• Circuit assets follow the libid-circuits v0.2.0 rename: the X circuit stages as x_token.json and the default circuitUrl is /circuits/x_token.json (breaking for integrators who hardcode the old filename — restage assets with npx libid-claim-assets after upgrading).
• claim-full pins: circuits v0.2.0, notary v0.2.0 (tlsn-wasm 0.2.0).
• The vk and proving behavior are unchanged (byte-identical vk across the rename).

🤖 Generated with Claude Code

v0.3.0

@libid/claim consumes the countersignature-free GitHub proof: VerifyResponse drops backendSignature and userAddress, and @libid/contracts moves to ^0.5.0 (12-field FullTlsProof). Pairs with identity-backend 0.2.0 and libid-contracts 0.5.0; breaking against identity-backend 0.1.x.

v0.2.0

@libid/claim 0.2.0 + @libid/claim-full 0.2.0 (new)

• New package @libid/claim-full: every static proving asset (tlsn wasm bundle, released circuits sha256-verified against the manifest, noir acvm/abi wasm) inside the npm tarball. npx libid-claim-assets <public-dir> stages them; ./assets/* subpath imports work under vite and next.
• @libid/claim 0.2.0 (breaking): the OIDC circuit-input conversion is pure TypeScript (the Rust/wasm helper is gone, wasmUrl options removed); the X circuit default path moved from /circuit/ to /circuits/ (per-call override kept).
• Toolchain pins (@aztec/bb.js nightly + @noir-lang beta.20) are locked to the libid-circuits v0.1.0 release manifest and enforced at build and test time.

v0.1.1

@libid/claim 0.1.1: the dynamic wasm imports are opaque to both webpack/Turbopack and Vite; the integration harness moves to the factory-world deterministic addresses (identical to production on every network).

v0.1.0

First release: @libid/claim — the browser OAuth/handle-claim library (GitHub, X, Google flows on MPC-TLS/zkTLS), plus the buttons demo UI and the docker-compose integration harness.