Repository navigation
ci: let release-please use a PAT so created tags trigger workflows - #24
Merged
Merged
Conversation
Tags and releases created with the default GITHUB_TOKEN do not trigger other workflows, so the Release workflow (binaries + crates.io publish) never ran for release-please tags. Use RELEASE_PLEASE_TOKEN when set, falling back to GITHUB_TOKEN.
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.
Description
Tags/releases created by release-please with the default
GITHUB_TOKENdo not trigger other workflows, so the Release workflow (binary builds +cargo publish) never ran forv0.3.0.This passes
secrets.RELEASE_PLEASE_TOKENto release-please when available, falling back toGITHUB_TOKEN. Create a fine-grained PAT with Contents: Read and write + Pull requests: Read and write namedRELEASE_PLEASE_TOKENto enable automatic release builds.Type of change
Checklist