Drop the empty Unreleased heading from the changelog - #18
Merged
Conversation
An Unreleased section with nothing under it, sitting directly above 3.0, reads as though 3.0 were unreleased. Add it back when there is something in it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SrD1CtCf7ERCCtH2k7LzK3
16 tasks
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.
## [Unreleased]had nothing under it and sat directly above## [3.0], so the two headings rantogether and 3.0 read as unreleased.
Removed. It goes back when there is something in it.
Verified the release-notes fallback still selects the right block: 104 lines, sections
Breaking, Upgrade notes, Security, Fixed, Added, Changed. Documentation only, no PHP changed.