Remove old GPG fingerprints #6014
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
tzununbekov
requested review from
soffokl,
Waldz,
tadaskay,
mdomasevicius,
Snawoot and
Guillembonet
as code owners
tzununbekov
force-pushed
the
new-gpg-key
branch
from
42f56e9 to
8799b79
Compare
tzununbekov
changed the title
mdomasevicius
approved these changes
Mar 14, 2024
soffokl
approved these changes
Mar 14, 2024
tzununbekov
force-pushed
the
new-gpg-key
branch
from
8799b79 to
6ddebe9
Compare
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.
As we created a new GPG key, a workaround to extend the old key lifetime is not needed anymore