Skip to content

docs: date v0.6.6 guide changelog, repoint eval links to main - #28

Merged
ddsha441981 merged 1 commit into
mainfrom
docs/v0.6.6-link-date-fixups
Oct 10, 2026
Merged

ddsha441981 merged 1 commit into
mainfrom
docs/v0.6.6-link-date-fixups

Conversation

@ddsha441981

Copy link
Copy Markdown
Owner

Pre-release doc audit fixups (shipped mdBook guide):

  • docs/src/changelog.md — was ## Unreleased (v0.6.6); root CHANGELOG is now [0.6.6] — 2026-10-10 and merged, so date the guide entry to match.
  • docs/src/benchmarks.md (×2) — the evaluation workspace + paired-report links pointed at the staging/v0.6.6 branch, which 404s once that branch is deleted after release. Repointed to main (consistent with the existing blob/main/CHANGELOG.md link in these docs).

Audit verdict for the record: 18/22 docs/src files were already clean (semantics, API signatures, intro/usage, benchmark numbers all verified against src/ and the measured evaluation; the old ~5ns claim is gone). Only these staleness items remained. Historical v0.6.1/v0.6.2 changelog figures left as dated history.

docs/src/changelog.md said 'Unreleased (v0.6.6)' after the root CHANGELOG
was dated and merged; set it to v0.6.6 (2026-10-10). benchmarks.md linked
the evaluation workspace and paired report on the staging/v0.6.6 branch,
which 404s once that branch is deleted post-release; point both at main
(matches the existing blob/main CHANGELOG link convention in these docs).
@ddsha441981
ddsha441981 merged commit 46d619c into main Oct 10, 2026
24 checks passed
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.

1 participant