docs: bring the unreleased changelog entries to the released style - #836
Conversation
Code ReviewRisk: Low — The changelog-only formatting update is safe to merge. Rewrites the eight unreleased entries as concise, one-line entries with pull-request references, while preserving their substantive change descriptions. It also removes the Vitest 5 planning note as described in the intent. Review usage: 5,476 in (3,056 cached) / 179 out tokens — $0.0022 (openrouter/openai/gpt-5.6-luna, thinking: low) Reviewed by @weareikko/code-review v0.9.5 for commit 78cb8df. Previous review runsPrevious run archived 2026-08-16T19:42:03ZCode ReviewRisk: Low — This documentation-only change is safe to merge; no blocking issues were found. Updates the eight unreleased changelog entries to the one-line format used by released entries and adds pull-request references for each. It also removes the Vitest 5 planning note, consistent with the stated intent that changelogs document changes rather than future plans. Review usage: 5,475 in (3,056 cached) / 187 out tokens — $0.0022 (openrouter/openai/gpt-5.6-luna, thinking: low) Reviewed by @weareikko/code-review v0.9.5 for commit a11dfdc. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #836 +/- ##
=======================================
Coverage 97.17% 97.17%
=======================================
Files 170 170
Lines 4143 4143
Branches 1152 1151 -1
=======================================
Hits 4026 4026
Misses 106 106
Partials 11 11
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Every entry under a released heading is one line ending in its pull request; the unreleased ones were paragraphs with no reference. They now match, and the detail they carried lives in the pull requests, which is where a reader who wants the mechanism will look anyway. One line of detail was dropped rather than moved: the note that Vitest 5 is blocked on `bench()` becoming `context.bench`. That is a plan, not a change, so it does not belong in a changelog. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011nNdFD3aQhzfdm3EsCSbS9
a11dfdc to
78cb8df
Compare
Every entry under a released heading is one line ending in its pull request:
Every entry under
[Unreleased]was a paragraph with no reference. After #833 landed a short linked entry, the section read two ways at once.All eight now match. The detail they carried is in the pull requests — #777 for the build and toolchain moves, #830 for the benchmark migration — which is where a reader who wants the mechanism looks anyway, and where it stays correct as the code moves.
One line was dropped rather than shortened: the note that Vitest 5 is blocked on
bench()becomingcontext.bench. That is a plan, not a change, and a changelog is the wrong place for it. It is in #777 if anyone needs it.Nothing but
CHANGELOG.mdis touched.🤖 Generated with Claude Code
https://claude.ai/code/session_011nNdFD3aQhzfdm3EsCSbS9