Update release workflow to use PERSONAL_ACCESS_TOKEN for GitHub actions #311
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
bpasero
approved these changes
Jul 14, 2025
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.
This pull request updates the GitHub Actions workflow for releases by replacing the
GITHUB_TOKENwith aPERSONAL_ACCESS_TOKENfor better security and permissions management.Changes in
.github/workflows/release.yml:GITHUB_TOKENtoPERSONAL_ACCESS_TOKENin thecreate_releasestep to use a personal access token for authentication.GITHUB_TOKENtoPERSONAL_ACCESS_TOKENin theupload-release-assetstep to ensure consistent token usage across release-related actions.