v0.3.6

svlens v0.3.6 release notes

Release-pipeline patch over v0.3.5. No source-code changes vs. v0.3.5;
the v0.3.5 binary surface ships verbatim. This release exists to fix
two release-infrastructure issues that v0.3.5 surfaced:

1. softprops/action-gh-release@v2 was still on Node.js 20, so
   v0.3.5's release-artifacts run produced new deprecation
   annotations even though the prior Node 24 migration had cleared
   actions/upload-artifact and codecov/codecov-action. v0.3.6
   bumps softprops to v3, which defaults to Node 24, and
   eliminates the last Node 20 surface in our workflows ahead of the
   2026-06-02 hosted-runner cutover.

2. GitHub Releases body was effectively empty. v0.3.5 used
   generate_release_notes: true, which only summarizes PR-merged
   commits since the last tag. svlens lands changes via direct
   main push (no PR), so the auto-generated body for v0.3.5 was
   one line linking back to v0.2.5. v0.3.6 switches to
   body_path: docs/releases/${{ github.ref_name }}.md so the
   release page now publishes the full hand-written release notes
   we commit alongside the version bump. The v0.3.5 release page
   was also retroactively backfilled via gh release edit so the
   existing tag is not silently behind the new convention.

What's in v0.3.6

• All of v0.3.5 (see v0.3.5) — same binary, same tests,
  same schema.
• release.yml now uses softprops/action-gh-release@v3 and
  body_path: docs/releases/${{ github.ref_name }}.md for tag-push
  release publication.

YAML schema additions

None. Identical to v0.3.5.

Test count

make test reports 571/571 passing — same as v0.3.5. Smoke
suites unchanged. Verified by CI on the v0.3.6 push to main before
the v0.3.6 tag.

Migration notes

No public API or schema changes vs. v0.3.5. If you maintain a fork
that copies release.yml, mirror the two softprops/action-gh-release
inputs change to keep the GitHub Releases page useful.

If you tag a release without a corresponding
docs/releases/v<tag>.md, the new body_path will be missing and
the release attach step will fail loudly rather than publish an empty
release body — this is the intended forcing function so future
release notes never get skipped.

Known follow-ups

Same list as v0.3.4 and v0.3.5; none of
those items closed in this patch.

Recommended validation

make test
ctest --test-dir build --output-on-failure

Optional, requires network and ~2 GiB scratch:

make bench