chore(release): v0.36.0 - #410
Conversation
Bump [workspace.package] version 0.35.0 -> 0.36.0 (Cargo.toml + Cargo.lock for all 23 workspace crates) and vscode-spar/package.json. Promote REQ-GUARD-FUZZ-SMOKE-001 to verified for release v0.36.0 — the fuzz-target guardrail now audits the REQUIRED fuzz-smoke context's target list, shipped in #409. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Rivet verification gate✅ 20/20 passed
Filter: Failed artifacts(none) Updated automatically by |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
Merged — v0.36.0 STAGED on All required checks passed on this PR (Mutation Testing ran ~2h and went green) and it's merged. The signed tag push is blocked: To finish, please push the signed tag from your local: Full context and the honest signing note are on #406. Generated by Claude Code |
What
Release bump for v0.36.0, cutting the fuzz-target guardrail fix shipped in #409 (merged to main as
d68fed5).[workspace.package] versioninCargo.toml:0.35.0→0.36.0Cargo.lock: all 23 workspace crates rebumped viacargo update --workspace(no third-party dependency versions changed — 79 unchanged)vscode-spar/package.json:0.35.0→0.36.0REQ-GUARD-FUZZ-SMOKE-001:implemented→verified,release: v0.36.0Why
#409 taught
tools/check_fuzz_targets.pyto audit the requiredfuzz-smokecontext's target list (ci.yml) rather than only the advisory nightly matrix — closing the list-parity hole #406 named. This release records that requirement as verified and ships it.The status flip stays within the guardrail's
{implemented, verified, accepted}claiming set, so no new verification-filter enforcement is introduced; the linkedTEST-GUARD-FUZZ-SMOKEsteps already passed green on #409.Scope
Version/lockfile/artifact metadata only — no source changes. All feature code and its oracles landed and passed full CI (incl. Mutation Testing + Lean) on #409 before merge.
🤖 Generated with Claude Code
Generated by Claude Code