feat: add release-please workflow #3
Merged
Conversation
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
This adds automated release management using Google's release-please action. The workflow will: - Create and maintain release PRs based on conventional commits - Update package.json version on release - Generate CHANGELOG.md - Create GitHub releases when release PR is merged Release-As: 1.0.0
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.
This adds automated release management using Google's release-please action.
What it does
package.jsonversion on releaseCHANGELOG.mdfrom commit historyFirst release
The commit includes
Release-As: 1.0.0footer to ensure the first release will be version 1.0.0.Usage
Once this is merged to main, release-please will: