chore: [REL-4161] write deploy key to file instead of adding contents directly #553
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
launchdarkly-upra
bot
changed the title
blaqbern
changed the title
sheldonmartin
approved these changes
Aug 5, 2025
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.
Since private keys are multiple lines, it's recommended to write them to a file instead of passing the contents directly to an env variable to avoid escaping issues \n characters being handled incorrectly, etc. Goreleaser supports (and probably prefers) writing private keys to a file, so I'm hopeful this will get us there. Hopefully, the private key is not malformed before writing to the file, but I guess we'll find out 😬.
Related Jira issue: REL-4161: Migrate ld-find-code-refs from Releaser to GHA