docs(changelog): remove the duplicate 1.1.0 entry - #74
Merged
jdhughes-dev merged 1 commit intoAug 3, 2026
Conversation
The changelog carried two 1.1.0 headings: the changes since 1.0.0, and a cumulative list of everything back to the first pull request. Remove the cumulative one, which repeats the 1.0.0 entry below it. A repeated heading also defeated the release note extraction, because the rule that starts the capture matched the second heading before the rule that ends it. Only start on the first match.
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.
The changelog had two
## [1.1.0]headings: the real one listing changes since 1.0.0, and a cumulative list of every pull request back to #7 that duplicates the 1.0.0 entry below it. The cumulative one is removed.The repeated heading also broke the release note extraction added in #73, because the rule that starts the capture matched the second heading before the rule that ends it, so a 1.1.0 release would have picked up both blocks. The capture now only starts on the first match.