Date released versions and record post-merge fixes in CHANGELOG - #11
Merged
Conversation
1.2.0, 1.4.0 and 1.5.0 shipped to master via PRs #4-#6, #8; date each with its actual merge day and a short subtitle, matching the convention every earlier version already follows. Also folds in three fixes that landed after their feature's PR merged, in the same spirit as 1.2.0's existing CodeMirror-tooltip entry (a fix for an unrelated pre-existing bug, recorded where it was actually fixed rather than attributed to an unshipped patch version): - 1.4.0: the "N entries seen" double-counting bug (PR #10). - 1.5.0: the transient-layout wiring gap and the persistent/transient previousValueHex leak, both caught by an independent Codex + Gemini review and verified against source before fixing (folded into PR #8 before merge); and the Trace State pane column-bleed CSS bug (PR #9), an unrelated regression from the v1.1 cockpit redesign. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
1.2.0, 1.4.0 and 1.5.0 were still marked "unreleased" even though they've
shipped to master (and to production, since every merge auto-deploys). Dates
each with its actual merge day and a short subtitle, matching every earlier
version's format.
Also records three fixes that landed after their feature's PR merged, in the
same spirit as 1.2.0's existing CodeMirror-tooltip entry:
previousValueHexleak, both caught by an independent Codex + Geminireview and folded into PR Transient storage as its own address space #8 before it merged; and the Trace → State
column-bleed CSS bug (PR Fix trace State pane words bleeding across Stack/Memory/Calldata columns #9), an unrelated regression from the v1.1
cockpit redesign.
Docs-only change; no code touched.
format:checkrelease:verify🤖 Generated with Claude Code