Use upstream ghaction-import-gpg to fix release workflow #32
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
kylecarbs
approved these changes
Jul 18, 2022
DanielleMaywood
pushed a commit
that referenced
this pull request
Sep 5, 2024
* fix: Replace hashicorp/ghaction-import-gpg with upstream * use correct syntax for ghaction-import-gpg parameters * fix "gpg_private_key" parameter name
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.
The
.github/workflows/release.ymlworkflow is currently broken by a Github change, which caused the v0.4.3 release to fail: hashicorp/ghaction-import-gpg#11Since the
hashicorp/ghaction-import-gpgfork is deprecated, this PR follows the recommendation to switch to the upstreamcrazymax/ghaction-import-gpgaction, which has a slightly different syntax for its parameters.