Skip to content

fix: no duplicate changelog entries - #471

Merged
wraithgar merged 1 commit into
npm:mainfrom
lukekarrys:lk/duplicate-changelog
Aug 26, 2024
Merged

wraithgar merged 1 commit into
npm:mainfrom
lukekarrys:lk/duplicate-changelog

Conversation

@lukekarrys

Copy link
Copy Markdown
Contributor

release-please will re-inject the entire changelog when looking
for the existing dependencies section in some cases. Have multiple
newlines between sections of the changelog triggers that behavior
because it looks for lines that do no start with '*' but it does
not account for empty lines

release-please will re-inject the entire changelog when looking
for the existing dependencies section in some cases. Have multiple
newlines between sections of the changelog triggers that behavior
because it looks for lines that do no start with '*' but it does
not account for empty lines
@lukekarrys
lukekarrys requested a review from a team as a code owner August 26, 2024 18:53
@wraithgar
wraithgar merged commit a102a8b into npm:main Aug 26, 2024
@github-actions github-actions Bot mentioned this pull request Aug 26, 2024
wraithgar pushed a commit that referenced this pull request Aug 26, 2024
🤖 I have created a release *beep* *boop*
---


##
[4.23.3](v4.23.2...v4.23.3)
(2024-08-26)
### Bug Fixes
*
[`a102a8b`](a102a8b)
[#471](#471) no duplicate
changelog entries (#471) (@lukekarrys)

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@lukekarrys
lukekarrys deleted the lk/duplicate-changelog branch August 29, 2024 03:05
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.

2 participants