chore(changelog): move v0.13.0 entries out of Unreleased#1283
Open
danielmeppiel wants to merge 1 commit into
Open
chore(changelog): move v0.13.0 entries out of Unreleased#1283danielmeppiel wants to merge 1 commit into
danielmeppiel wants to merge 1 commit into
Conversation
All 6 PRs listed under '## [Unreleased]' (#1268, #1270, #1271, #1272, #1274, #1276) merged into commits reachable from the v0.13.0 tag (final retag at 9216516). Move them into the [0.13.0] ### Fixed section so the public changelog reflects what actually shipped. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Moves six changelog entries that were already included in the v0.13.0 tag from ## [Unreleased] into the ## [0.13.0] release notes, keeping the entry text intact and ordering #1268 first as the only user-visible fix.
Changes:
- Removed six
### Fixedentries from## [Unreleased] - Added the same six entries under
## [0.13.0] → ### Fixed, with#1268listed first - Preserved existing
[0.13.0]entry order otherwise
Show a summary per file
| File | Description |
|---|---|
| CHANGELOG.md | Relocates already-shipped v0.13.0 items out of Unreleased into the 0.13.0 Fixed section. |
Copilot's findings
- Files reviewed: 1/1 changed files
- Comments generated: 0
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
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.
Problem
The
## [Unreleased]section currently lists 6 PRs that already shipped in the v0.13.0 tag (92165163, the final retag). The v0.13.0 tag was retagged 4 times during the release to absorb post-tag fixes (Windows runner stabilization, transient MCP registry flake, the macOS git 2.53.0 fix), and each retag re-pointed at then-current main HEAD. As a result, every PR merged between the original tag and the final retag is reachable fromv0.13.0but was never moved out of Unreleased.Verification
For each PR I ran
gh pr view <PR> --json mergeCommit -q .mergeCommit.oidthengit tag --contains <SHA>:src/changeChange
Move all 6 entries verbatim from
## [Unreleased]into## [0.13.0] ### Fixed.#1268goes first (only user-visible behavior change); the 5 tests-only entries follow. Existing[0.13.0]ordering is preserved otherwise.Per repo convention (
.apm/instructions/changelog.instructions.md): every PR gets one concise line, and entries move out of Unreleased only at release time -- this PR closes that gap retroactively for v0.13.0.How to test
Should show only the 6 entries relocated; no wording or PR numbers altered.