chore: bypass obsolete RELEASE_PLEASE_TOKEN in bump-version workflow#1000
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
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.
This pull request makes a small update to the version bump workflow. The change ensures that only the
BUMP_VERSION_TOKENor the default GitHub token is used for authentication when creating a pull request, removing the use of theRELEASE_PLEASE_TOKEN.bump-version.ymlworkflow to use onlyBUMP_VERSION_TOKENorgithub.tokenfor the pull request creation step, removingRELEASE_PLEASE_TOKENfrom the token selection.