Skip to content

docs(changelog): file the message-trigger entry under [4.8.2] - #245

Merged
kevintseng merged 1 commit into
mainfrom
docs/changelog-4.8.2-message
Aug 29, 2026
Merged

docs(changelog): file the message-trigger entry under [4.8.2]#245
kevintseng merged 1 commit into
mainfrom
docs/changelog-4.8.2-message

Conversation

@kevintseng

Copy link
Copy Markdown
Contributor

Pre-release check for v4.8.2 found PR #244's CHANGELOG entry under [Unreleased] while the code it describes ships in the 4.8.2 tag. This moves the entry verbatim into [4.8.2] > Changed; [Unreleased] is empty again.

Pure move: content lines of CHANGELOG.md before/after differ only by the ### Changed heading removed from [Unreleased].

Evidence (this tree): eg check PASS 1/1 (static check that the entry appears once in [4.8.2] and [Unreleased] has no entries; check-doc-claims passes; mutation removing the entry turns the check red and is restored).

PR #244 landed on main after the [4.8.2] section was cut, so its entry
sat under [Unreleased] while the code it describes ships in the 4.8.2
tag. Moved verbatim into [4.8.2] > Changed; [Unreleased] is empty again.
@kevintseng
kevintseng merged commit b6487f8 into main Aug 29, 2026
13 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