Skip to content

Update usages of GPG public keys with new rotated key#754

Merged
yerzhan7 merged 2 commits into
awslabs:mainfrom
renanmagagnin:add-new-release-gpg-key
Mar 23, 2026
Merged

Update usages of GPG public keys with new rotated key#754
yerzhan7 merged 2 commits into
awslabs:mainfrom
renanmagagnin:add-new-release-gpg-key

Conversation

@renanmagagnin
Copy link
Copy Markdown
Contributor

Issue #, if available:

Description of changes: We have a new GPG public key because the old one will expire soon. In this PR we update the usages of the public keys with the new one.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Signed-off-by: Renan Magagnin <renanmag@amazon.co.uk>
@renanmagagnin renanmagagnin force-pushed the add-new-release-gpg-key branch from d926fef to c9c8f42 Compare March 20, 2026 15:03
@renanmagagnin renanmagagnin requested a review from a team as a code owner March 20, 2026 15:03
Comment thread Dockerfile
# Import the key and validate it has the fingerprints we expect
RUN gpg --import KEYS && \
(gpg --fingerprint mountpoint-s3@amazon.com | grep "673F E406 1506 BB46 9A0E F857 BE39 7A52 B086 DA5A")
(gpg --fingerprint mountpoint-s3@amazon.com | grep "8AEF E705 EBE3 29C0 948C 75A6 6F1C 3B3A EF4B 030B") && \
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

QQ: why are we using &&? Since we're rotating the GPG keys not adding a new one, perhaps this should be || ? (or that we have 2 keys in transition period?)

@yerzhan7 yerzhan7 merged commit 000854d into awslabs:main Mar 23, 2026
23 of 32 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants