AST-171789 Fetch GPG signing key from standalone AWS secret - #501
Merged
cx-lior-poterman merged 1 commit intoSep 24, 2026
Merged
Conversation
The signing key's line breaks were lost when it lived inside a combined JSON secret, breaking GPG import during release. Move it to its own plaintext AWS secret, which preserves line breaks, and have the release workflow fetch it under the same env var name it already reads so no other line needs to change. The old copy inside the combined secret has been removed. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
cx-sumit-morchhale
approved these changes
Sep 24, 2026
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
3 participants
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.
GPG import was failing because the signing key's line breaks were lost when it lived inside a combined JSON secret. It now lives in its own plaintext AWS secret, which preserves them.
This adds one line so the release workflow also fetches that new secret, exported under the same environment variable name it already reads, so nothing else needs to change. The old copy inside the combined secret has been removed, leaving one source of truth for the key.