Repository navigation
ci: add release-please - #15
Merged
Merged
Conversation
The manifest starts at the latest release v2.3.1, and bootstrap-sha points at its commit so the first release PR collects only later changes. Assisted-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
What was changed
master(release-type: php, tagsvX.Y.Zas before).2.3.1;bootstrap-shais thev2.3.1commit, so the first release PR will contain only the changes merged after it (feat: sort imports alphabetically and shorten names resolvable by imports #14 →2.4.0).Why?
Releases and the changelog are generated from conventional commits instead of being cut by hand.
Checklist