Sourced from aws-actions/configure-aws-credentials's releases.
v4.0.2
See the changelog for details about the changes included in this release.
v4.0.1
See the changelog for details about the changes included in this release.
v4.0.0
See the changelog for details about the changes included in this release.
v4
This tag tracks the latest v4.x.x release
v3.0.2
See the changelog for details about the changes included in this release.
v3.0.1
See the changelog for details about the changes included in this release.
v3.0.0
See the changelog for details about the changes included in this release.
v3
This tag tracks the latest v3.x.x release
v2.2.0
See the changelog for details about the changes included in this release.
v2.1.0
See the changelog for details about the changes included in this release.
v2.0.0
See the changelog for details about the changes included in this release.
v2
This tag tracks the latest v2.x.x release.
Sourced from aws-actions/configure-aws-credentials's changelog.
4.0.2 (2024-02-09)
- Revert 4.0.1 to remove warning
4.0.1 (2023-10-03)
Documentation
- Throw a warning when customers use long-term credentials.
4.0.0 (2023-09-11)
- Upgraded runtime to
node20
fromnode16
3.0.2 (2023-09-07)
Bug Fixes
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
option3.0.0 (2023-08-21)
Features
- Can configure
max-retries
anddisable-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
... (truncated)
e3dd6a4
chore: Bump @types/jest
from 29.5.11 to 29.5.12 (#1000)c6c400f
chore: Bump @types/node
from 20.11.5 to 20.11.16 (#999)c38ab41
chore: Bump prettier from 3.2.4 to 3.2.5 (#998)2071ebe
chore: Bump @types/node
from 20.11.3 to 20.11.5 (#986)44112af
chore: Update dist492c455
chore: Bump @aws-sdk/client-sts
from 3.490.0 to 3.496.0
(#982)13e074e
chore: Update dist5a676ce
chore: Bump @smithy/property-provider
from 2.0.17 to 2.1.1
(#985)e43a696
chore: Bump ts-jest from 29.1.1 to 29.1.2 (#983)eb98af5
chore: Bump prettier from 3.2.2 to 3.2.4 (#981)