chore: release 2.1.0 - #59
Merged
petercorke merged 2 commits intoAug 3, 2026
Merged
Conversation
Up to standards ✅🟢 Issues
|
release-please's autogenerated 2.1.0 changelog listed 13 changes twice: once for the real conventional commit, once for the "Merge pull request #N from ..." commit GitHub creates on merge, whose body happens to embed the PR title verbatim -- which release-please's parser also picks up as a second conventional commit. Removed the merge-commit duplicate in each pair, keeping the original commit.
Contributor
Author
|
🤖 Created releases: 🌻 |
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.
🤖 I have created a release beep boop
2.1.0 (2026-08-03)
Features
Bug Fixes
Documentation
This PR was generated with Release Please. See documentation.