docs(changelog): record the nine fixes that merged after the v3.10.0 tag - #1612
Merged
Conversation
The `deploy_checklist.md` post-release block asks for regressions and limitations to be recorded. Nine defect fixes (PR #1603) merged into `main` *after* `v3.10.0` was tagged at `5b69202`, so the published 3.10.0 artifacts do not contain any of them — and the changelog said nothing about that. A user who reads the 3.10.0 notes and hits #1582 or #1586 currently has no way to tell whether the fix exists. A new `## [Unreleased]` section lists all nine with the defect, not just the ticket number, and states plainly at the top that none of it ships in 3.10.0. Second, the file already had a `## [Unreleased] — Sprint R35 (2026-08-12)` heading sitting *inside* the 3.9.19 block. That content is long since released — its own #1508 entry also appears under 3.9.20 — so the heading claimed the opposite of the truth and would have collided with the real Unreleased section. It becomes `### Sprint R35 (2026-08-12) — shipped in the 3.9.x line`, which matches where it already sits without asserting an exact version it landed in. Documentation only; no code, no behavior change. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
deploy_checklist.md→ After publishing local artifacts → "Record regressions or limitations with a reproducible local artifact."Nine defect fixes (#1603) merged into
mainafterv3.10.0was tagged at5b69202, so the published 3.10.0 artifacts contain none of them — and the changelog said nothing about it. Someone reading the 3.10.0 notes after hitting #1582 or #1586 currently cannot tell whether a fix exists at all.What this changes
A
## [Unreleased]section at the top ofCHANGELOG.md, describing each of the nine defects (not just the ticket numbers) and stating up front that none of it is in the 3.10.0 artifacts.It also fixes a second, older problem in the same file: a heading
## [Unreleased] — Sprint R35 (2026-08-12)sat inside the 3.9.19 block. That content has long since shipped — its own #1508 entry appears again under 3.9.20 — so the heading claimed the opposite of the truth, and a real Unreleased section would have collided with it. It becomes### Sprint R35 (2026-08-12) — shipped in the 3.9.x line, which matches where it already sits without asserting a precise version.Documentation only. No code, no behavior change.
Release-checklist status for v3.10.0, for the record
Verified against the published artifacts while writing this:
SHA256SUMSvs downloaded artifactecd77397…matchesrelease-manifest.jsonvsSHA256SUMSchecksums_sha256matcheslean-ctx-bin/pi-lean-ctx3.10.0lean-ctx doctor🤖 Generated with Claude Code