Skip to content

chore(release): v0.36.0 - #410

Merged
avrabe merged 1 commit into
mainfrom
release/v0.36.0
Aug 8, 2026
Merged

chore(release): v0.36.0#410
avrabe merged 1 commit into
mainfrom
release/v0.36.0

Conversation

@avrabe

@avrabe avrabe commented Aug 8, 2026

Copy link
Copy Markdown
Contributor

What

Release bump for v0.36.0, cutting the fuzz-target guardrail fix shipped in #409 (merged to main as d68fed5).

  • [workspace.package] version in Cargo.toml: 0.35.00.36.0
  • Cargo.lock: all 23 workspace crates rebumped via cargo update --workspace (no third-party dependency versions changed — 79 unchanged)
  • vscode-spar/package.json: 0.35.00.36.0
  • REQ-GUARD-FUZZ-SMOKE-001: implementedverified, release: v0.36.0

Why

#409 taught tools/check_fuzz_targets.py to audit the required fuzz-smoke context'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 linked TEST-GUARD-FUZZ-SMOKE steps 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

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>
@github-actions

github-actions Bot commented Aug 8, 2026

Copy link
Copy Markdown

Rivet verification gate

20/20 passed

count
Passed 20
Failed 0
Skipped (no steps) 0

Filter: (and (= type "feature") (or (has-tag "v093") (has-tag "v0100")))

Failed artifacts

(none)

Updated automatically by tools/post_verification_comment.py. Source of truth: artifacts/verification.yaml.

@codecov

codecov Bot commented Aug 8, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@avrabe
avrabe merged commit 686a23a into main Aug 8, 2026
21 checks passed
@avrabe
avrabe deleted the release/v0.36.0 branch August 8, 2026 09:11

avrabe commented Aug 8, 2026

Copy link
Copy Markdown
Contributor Author

Merged — v0.36.0 STAGED on main (686a23a); needs a maintainer tag push.

All required checks passed on this PR (Mutation Testing ran ~2h and went green) and it's merged. The signed tag push is blocked: git push origin v0.36.0 returns HTTP 403 Forbidden from GitHub's git-receive-pack (a v* tag-protection ruleset — branch pushes from the same identity succeed, and the proxy relayed cleanly). release.yml has not triggered.

To finish, please push the signed tag from your local:

git fetch origin main
git tag -s v0.36.0 686a23a -m 'spar v0.36.0'
git push origin v0.36.0

Full context and the honest signing note are on #406.


Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants