Bump aws-actions/configure-aws-credentials from 3.0.2 to 4.0.0

[dependabot]

Bumps aws-actions/configure-aws-credentials from 3.0.2 to 4.0.0.

Release notes

Sourced from aws-actions/configure-aws-credentials's releases.

v4.0.0

See the changelog for details about the changes included in this release.

Changelog

Sourced from aws-actions/configure-aws-credentials's changelog.

Changelog

All notable changes to this project will be documented in this file. See standard-version for commit guidelines.

4.0.0 (2023-09-11)

• Upgraded runtime to node20 from node16

3.0.2 (2023-09-07)

Bug Fixes

• fixes #817 #819: validation logic throwing unwanted errors d78f55b

3.0.1 (2023-08-24)

Features

• Can configure special-characters-workaround to keep retrying credentials if the returned credentials have special characters (Fixes #599)

Bug Fixes

• Fixes #792: Action fails when intending to use existing credentials
• Minor typo fix from @​ubaid-ansari21

Changes to existing functionality

• Special characters are now allowed in returned credential variables unless you configure the special-characters-workaround option

3.0.0 (2023-08-21)

Features

• Can configure max-retries and disable-retry to modify retry functionality when the assume role call fails
• Set returned credentials as step outputs with output-credentials
• Clear AWS related environment variables at the start of the action with unset-current-credentials
• Unique role identifier is now printed in the workflow logs

Bug Fixes

• Can't use credentials if they contain a special character
• Retry functionality added when generating the JWT fails
• Can now use webIdentityTokenFile option
• Branch name validation too strict
• JS SDK v2 deprecation warning in workflow logs

Changes to existing functionality

• Default session duration is now 1 hour in all cases (from 6 hours in some cases)
• Account ID will not be masked by default in logs

2.2.0 (2023-05-31)

Features

• inline-session-policy prop enables assuming a role with inline session policies (d00f6c6)

... (truncated)

Commits

• 8c3f20d chore: release v4 (#840)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

GitHub Workflows (.github/workflows/*.yml)

Have you...

• pinned all affected GitHub Actions at a specific commit by SHA?
• reviewed the source code of the action at the commit you are pinning?
• confirmed that no GitHub security measures are being bypassed?
• checked for any injection of user content into protected contexts?
• reviewed Security hardening for GitHub Actions?
• reviewed GitHub Workflows?