chore: [REL-4161] use elevated token for git stuff #562
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
blaqbern
commented
Aug 11, 2025
blaqbern
commented
Aug 11, 2025
blaqbern
commented
Aug 11, 2025
cjhensen
approved these changes
Aug 11, 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.
The GITHUB_TOKEN that's built-in to the GHA is not authorized to push directly to main. We need to do this in order to push up our committed changes to the remote repo so we can create the release. I had a new SSM parameter added that will allow this, so we should be able to cut the release now with this new token. I needed to get a little creative since the value is not known until after the
get secretsstep runs, but I think what I have here should work.Related Jira issue: REL-4161: Migrate ld-find-code-refs from Releaser to GHA