fix: avoid using GitHub Personal Access Token while publishing a new release #30
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
…release to force open bump version PRs as GitHub bot
Merged
Merged
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.
Why: force open bump version PRs as GitHub bot
Why we were using GH PACs before: it is the recommendation by Release please to be able to run further GitHub Actions triggered by the PR opened by Release please. However, we are not interested in that behavior because we do not have CI test workflows in this repository, and even in that case, that tests would have already run in their corresponding PRs.
PS: Sorry for using
fixSemVer type. It should be aci, but we are testing out the automated release process and need to trigger it to create a PR 🙏