chore: use release-please to automate versioning, changelogs and GitHub releases #165
Conversation
This file contains 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
…ub releases Using this action, as long as contributors follow the [conventional commit guidelines](https://www.conventionalcommits.org/en/v1.0.0/) new versions, releases and changelog updates can be automated. This action can also be extended to [automate npm publishing](https://github.com/googleapis/release-please-action#automating-publication-to-npm) on version-up. For maintainers this reduces a lot of overhead in the "admin" of new releases, and for consumers it increases clarity on new changes. Note that for the PRs created by release-please to be able to trigger further GitHub actions, a `token` will need to be provided. In this case I've pointed to a secret called `RELEASE_PLEASE_TOKEN`. See https://github.com/googleapis/release-please-action#github-credentials for more information on this.
|
@ibalosh Can you take a look at this? I think it will be a nice improvement. |
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.
Using this action, as long as contributors follow the conventional commit guidelines new versions, releases and changelog updates can be automated. This action can also be extended to automate npm publishing on version-up. For maintainers, this reduces a lot of overhead in the "admin" of new releases, and for consumers, it increases clarity on new changes. Note that for the PRs created by release-please to be able to trigger further GitHub actions, a
tokenwill need to be provided. In this case, I've pointed to a secret calledRELEASE_PLEASE_TOKEN. See https://github.com/googleapis/release-please-action#github-credentials for more information on this.