fix: update GPG private key secret name in bump-versions workflow#64
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
Updates the bump-versions GitHub Actions workflow to use the correct repository secret name for the GPG private key when importing the signing key for automated version-bump commits/PRs.
Changes:
- Switched the GPG private key input from
secrets.GPG_PRIVATE_KEYtosecrets.BUMP_PRIVATE_GPGin the GPG import step.
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
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.
Updates the GPG private key secret name to BUMP_PRIVATE_GPG in the bump-versions workflow.