release: publish v0.8.0#604
Conversation
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (47)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Post-release audit for v0.8.0: pass. Release visible at https://github.com/EffortlessMetrics/uselesskey/releases/tag/v0.8.0 with the hand-written fixture-layer boundary. Tag |
Summary
TLS contract-pack and public crate-surface cleanup release. Bumps workspace from v0.7.x to v0.8.0.
What's new
TLS contract pack
Task-first user docs sweep
Five new how-to pages: Vault KV export (#590), build.rs materialize (#591), WebAuthn ceremony validation (#592), PKCS#11 mock fixtures (#593), webhook signature validation (#594).
Public crate-surface cleanup
29 published-internal shim crates removed. v0.7.0 folded their content into owner crate `srp::*` modules; v0.7.x kept the shims as compatibility re-exports; v0.8.0 removes them entirely. The v0.7.x crate versions remain on crates.io as historical records.
Publish-system hardening
Toolchain
No MSRV change. v0.8.0 stays on Rust 1.95.
Claim boundary
`uselesskey` is a test-fixture layer. It is not production key management, scanner evasion, or cryptographic assurance.
Validation
Local validation (worktree):
CI will run the full `xtask pr` lane (bdd, full test matrix, fuzz build, clippy, etc.) plus the rest of `release-evidence --version 0.8.0 --summary` (TLS contract-pack proof, scanner-safe proof, OIDC proof, economics, audit-surface, perf, mutants-nightly --scope public). The local lane couldn't complete the fuzz build because the agent ran from a worktree where `cargo fuzz` resolves `fuzz/Cargo.toml` against the main-checkout workspace root.
Post-merge
References
Test plan