Add docs on using a new PGP keypair #48
Merged
Conversation
This file contains 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
The docs are quite long, so I've split them out into their own document.
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 was prompted by our old PGP key expiring on 29th November, causing releases to fail at the signing stage with
gpg: signing failed: Unusable secret key- thanks to @tkgnm for reporting that!I paired with @shtukas on generating the new PGP key (
EF53C0E05A7067985C09F1B2AAE7330D94C67345, which will expire in 2027), and have written up general docs in markdown for our publicgha-scala-library-release-workflowrepository in this PR.There are also some Guardian-specific docs at:
I've verified that the new PGP can be successfully used for new releases by releasing redirect-resolver v0.0.42.