ci: authenticate with default github token in release workflows #35
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
Currently, the release workflows attempt to pull github authentication from 1password. However, this workflow is only intended for use in non-public SxT workflows. Since we do not need access to private SxT information to perform these releases, using the secret github token should suffice for now.
What changes are included in this PR?
Steps that attempt to use custom github authentication are removed or now use
secrets.GH_TOKEN
.Are these changes tested?
No. These changes do not affect existing functionality.