ci: switch to using default GITHUB_TOKEN secret#281
Merged
Conversation
A custom GH_TOKEN is currently used to checkout the repository and perform release operations in the release workflow. However, it is likely that we will be able to use the default GITHUB_TOKEN secret. This PR attempts to switch to this default secret.
fidelcanojr
approved these changes
Jun 12, 2026
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
2 participants
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.
Rationale for this change
A custom GH_TOKEN is currently used to checkout the repository and perform release operations in the release workflow. However, it is likely that we will be able to use the default GITHUB_TOKEN secret. This PR attempts to switch to this default secret.
What changes are included in this PR?
Switch to
GITHUB_TOKEN(with some special permissions) in release workflow for semantic-release and checkout.Are these changes tested?
These changes do not affect existing functionality, which should be verified by existing tests.