ci: Upgrade AWS credentials action - #726
Closed
jygong-amazon wants to merge 1 commit into
Closed
jygong-amazon wants to merge 1 commit into
jygong-amazon wants to merge 1 commit into
Conversation
Move the daily metric-publishing OIDC step from configure-aws-credentials v2 to v6.3.0. The supported release runs natively on Node 24 and preserves the existing role and region inputs.
Contributor
Author
|
Superseded by #727, which applies the same one-line credential-action upgrade directly to master from a clean master-based branch. |
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
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.
ℹ️ Description
Upgrade
aws-actions/configure-aws-credentialsfrom v2 to v6.3.0 in the daily workflow. Version 2 runs under GitHub's forced Node 24 compatibility mode and masks some OIDC failures withCannot read properties of undefined (reading 'message'). Version 6.3.0 declares Node 24 and preserves the existingrole-to-assumeandaws-regioninputs.Issue #, if available
Related: scheduled run 35337891143 and ORR action item
Type of change
🧪 How Has This Been Tested?
role-to-assumeandaws-regioninputs.permissions: id-token: writeand the existing role/region values are unchanged.development; the role trust policy does not authorize feature-branch subjects.Unit test coverage
Not applicable to a one-line workflow dependency update.
Additional Manual Test
📱 Screenshots, if available
Not applicable.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.