From b8b4fdbcd40fe68bbf1f2a633f184506656d7df3 Mon Sep 17 00:00:00 2001 From: Tom Keller <1083460+kellertk@users.noreply.github.com> Date: Mon, 4 Aug 2025 13:38:59 -0700 Subject: [PATCH 1/4] Update CHANGELOG.md --- CHANGELOG.md | 18 ++++++------------ 1 file changed, 6 insertions(+), 12 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 33396b281..20b3e5b7f 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,18 +2,6 @@ All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines. -## [4.3.0](https://github.com/aws-actions/configure-aws-credentials/compare/v4.3.0...v4.3.0) (2025-08-04) - - -### Bug Fixes - -* properly set proxy environment variable ([cbea708](https://github.com/aws-actions/configure-aws-credentials/commit/cbea70821e4ab985ad3be0e5a93390523e257cde)) - - -### Miscellaneous Chores - -* release 4.3.0 ([3f7c218](https://github.com/aws-actions/configure-aws-credentials/commit/3f7c2187213bafaa1ea60a850b27082cbf55dda0)) - ## [4.3.0](https://github.com/aws-actions/configure-aws-credentials/compare/v4.2.1...v4.3.0) (2025-08-04) @@ -27,6 +15,12 @@ All notable changes to this project will be documented in this file. See [standa * **docs:** readme samples versioning ([5b3c895](https://github.com/aws-actions/configure-aws-credentials/commit/5b3c89504689ea1ea2b6000b23a6a2aac463662a)) * the wrong example region for China partition in README ([37fe9a7](https://github.com/aws-actions/configure-aws-credentials/commit/37fe9a740bcb30ee8cccd96feb90666c937311f2)) +* properly set proxy environment variable ([cbea708](https://github.com/aws-actions/configure-aws-credentials/commit/cbea70821e4ab985ad3be0e5a93390523e257cde)) + + +### Miscellaneous Chores + +* release 4.3.0 ([3f7c218](https://github.com/aws-actions/configure-aws-credentials/commit/3f7c2187213bafaa1ea60a850b27082cbf55dda0)) ## [4.2.1](https://github.com/aws-actions/configure-aws-credentials/compare/v4.2.0...v4.2.1) (2025-05-14) From 83a7f061975431d1818e942cc6a15cf063f17995 Mon Sep 17 00:00:00 2001 From: Michael Lehmann Date: Mon, 4 Aug 2025 13:52:04 -0700 Subject: [PATCH 2/4] Update README.md update readme with latest version --- README.md | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/README.md b/README.md index 95d8dd707..d012df647 100644 --- a/README.md +++ b/README.md @@ -143,7 +143,7 @@ See [action.yml](./action.yml) for more detail. | role-skip-session-tagging | Skips session tagging if set. | No | | inline-session-policy | You may further restrict the assumed role policy by defining an inline policy here. | No | | managed-session-policies | You may further restrict the assumed role policy by specifying a managed policy here. | No | -| output-credentials | When set, outputs fetched credentials as action step output. (Outputs aws-access-key-id, aws-secret-access-key, aws-session-token, aws-account-id, and aws-expiration). Defaults to false. | No | +| output-credentials | When set, outputs fetched credentials as action step output. (Outputs aws-access-key-id, aws-secret-access-key, aws-session-token, aws-account-id, authenticated-arn, and aws-expiration). Defaults to false. | No | | output-env-credentials | When set, outputs fetched credentials as environment variables (AWS_REGION, AWS_DEFAULT_REGION, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN). Defaults to true. Set to false if you need to avoid setting/changing env variables. You'd probably want to use output-credentials if you disable this. (NOTE: Setting to false will prevent the aws-account-id from being exported as a step output). | No | | unset-current-credentials | When set, attempts to unset any existing credentials in your action runner. | No | | disable-retry | Disabled retry/backoff logic for assume role calls. By default, retries are enabled. | No | @@ -178,7 +178,7 @@ this action will always consider the `HTTP_PROXY` environment variable. Manually configured proxy: ```yaml -uses: aws-actions/configure-aws-credentials@v4.2.1 +uses: aws-actions/configure-aws-credentials@v4.3.0 with: aws-region: us-east-2 role-to-assume: my-github-actions-role @@ -249,13 +249,13 @@ line. Inline session policy examples ```yaml - uses: aws-actions/configure-aws-credentials@v4.2.1 + uses: aws-actions/configure-aws-credentials@v4.3.0 with: inline-session-policy: '{"Version":"2012-10-17","Statement":[{"Sid":"Stmt1","Effect":"Allow","Action":"s3:List*","Resource":"*"}]}' ``` Or we can have a nicely formatted JSON as well: ```yaml - uses: aws-actions/configure-aws-credentials@v4.2.1 + uses: aws-actions/configure-aws-credentials@v4.3.0 with: inline-session-policy: >- { @@ -281,13 +281,13 @@ the role. Managed session policy examples ```yaml - uses: aws-actions/configure-aws-credentials@v4.2.1 + uses: aws-actions/configure-aws-credentials@v4.3.0 with: managed-session-policies: arn:aws:iam::aws:policy/AmazonS3ReadOnlyAccess ``` And we can pass multiple managed policies likes this: ```yaml - uses: aws-actions/configure-aws-credentials@v4.2.1 + uses: aws-actions/configure-aws-credentials@v4.3.0 with: managed-session-policies: | arn:aws:iam::aws:policy/AmazonS3ReadOnlyAccess @@ -325,7 +325,7 @@ You can specify the audience through the `audience` input: ```yaml - name: Configure AWS Credentials for China region audience - uses: aws-actions/configure-aws-credentials@v4.2.1 + uses: aws-actions/configure-aws-credentials@v4.3.0 with: audience: sts.amazonaws.com.cn aws-region: cn-northwest-1 @@ -399,7 +399,7 @@ Examples ### AssumeRoleWithWebIdentity ```yaml - name: Configure AWS Credentials - uses: aws-actions/configure-aws-credentials@v4.2.1 + uses: aws-actions/configure-aws-credentials@v4.3.0 with: aws-region: us-east-2 role-to-assume: arn:aws:iam::123456789100:role/my-github-actions-role @@ -413,13 +413,13 @@ environment variable and use it to assume the role ### AssumeRole with role previously assumed by action in same workflow ```yaml - name: Configure AWS Credentials - uses: aws-actions/configure-aws-credentials@v4.2.1 + uses: aws-actions/configure-aws-credentials@v4.3.0 with: aws-region: us-east-2 role-to-assume: arn:aws:iam::123456789100:role/my-github-actions-role role-session-name: MySessionName - name: Configure other AWS Credentials - uses: aws-actions/configure-aws-credentials@v4.2.1 + uses: aws-actions/configure-aws-credentials@v4.3.0 with: aws-region: us-east-2 role-to-assume: arn:aws:iam::987654321000:role/my-second-role @@ -434,7 +434,7 @@ role, `arn:aws:iam::987654321000:role/my-second-role`. ### AssumeRole with static IAM credentials in repository secrets ```yaml - name: Configure AWS Credentials - uses: aws-actions/configure-aws-credentials@v4.2.1 + uses: aws-actions/configure-aws-credentials@v4.3.0 with: aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }} aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }} @@ -453,7 +453,7 @@ name, like `role-to-assume: my-github-actions-role`. ```yaml - name: Configure AWS Credentials 1 id: creds - uses: aws-actions/configure-aws-credentials@v4.2.1 + uses: aws-actions/configure-aws-credentials@v4.3.0 with: aws-region: us-east-2 role-to-assume: arn:aws:iam::123456789100:role/my-github-actions-role @@ -462,7 +462,7 @@ name, like `role-to-assume: my-github-actions-role`. run: | aws sts get-caller-identity - name: Configure AWS Credentials 2 - uses: aws-actions/configure-aws-credentials@v4.2.1 + uses: aws-actions/configure-aws-credentials@v4.3.0 with: aws-region: us-east-2 aws-access-key-id: ${{ steps.creds.outputs.aws-access-key-id }} From be2e7ad815e27b890489a89ce2717b0f9e26b56e Mon Sep 17 00:00:00 2001 From: Tom Keller <1083460+kellertk@users.noreply.github.com> Date: Mon, 4 Aug 2025 16:17:49 -0700 Subject: [PATCH 3/4] fix: update readme to 4.3.1 (#1424) This is a fix instead of a chore to force a 4.3.1 tag Release-as: 4.3.1 --- README.md | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/README.md b/README.md index d012df647..4a7ac973f 100644 --- a/README.md +++ b/README.md @@ -178,7 +178,7 @@ this action will always consider the `HTTP_PROXY` environment variable. Manually configured proxy: ```yaml -uses: aws-actions/configure-aws-credentials@v4.3.0 +uses: aws-actions/configure-aws-credentials@v4.3.1 with: aws-region: us-east-2 role-to-assume: my-github-actions-role @@ -249,13 +249,13 @@ line. Inline session policy examples ```yaml - uses: aws-actions/configure-aws-credentials@v4.3.0 + uses: aws-actions/configure-aws-credentials@v4.3.1 with: inline-session-policy: '{"Version":"2012-10-17","Statement":[{"Sid":"Stmt1","Effect":"Allow","Action":"s3:List*","Resource":"*"}]}' ``` Or we can have a nicely formatted JSON as well: ```yaml - uses: aws-actions/configure-aws-credentials@v4.3.0 + uses: aws-actions/configure-aws-credentials@v4.3.1 with: inline-session-policy: >- { @@ -281,13 +281,13 @@ the role. Managed session policy examples ```yaml - uses: aws-actions/configure-aws-credentials@v4.3.0 + uses: aws-actions/configure-aws-credentials@v4.3.1 with: managed-session-policies: arn:aws:iam::aws:policy/AmazonS3ReadOnlyAccess ``` And we can pass multiple managed policies likes this: ```yaml - uses: aws-actions/configure-aws-credentials@v4.3.0 + uses: aws-actions/configure-aws-credentials@v4.3.1 with: managed-session-policies: | arn:aws:iam::aws:policy/AmazonS3ReadOnlyAccess @@ -325,7 +325,7 @@ You can specify the audience through the `audience` input: ```yaml - name: Configure AWS Credentials for China region audience - uses: aws-actions/configure-aws-credentials@v4.3.0 + uses: aws-actions/configure-aws-credentials@v4.3.1 with: audience: sts.amazonaws.com.cn aws-region: cn-northwest-1 @@ -399,7 +399,7 @@ Examples ### AssumeRoleWithWebIdentity ```yaml - name: Configure AWS Credentials - uses: aws-actions/configure-aws-credentials@v4.3.0 + uses: aws-actions/configure-aws-credentials@v4.3.1 with: aws-region: us-east-2 role-to-assume: arn:aws:iam::123456789100:role/my-github-actions-role @@ -413,13 +413,13 @@ environment variable and use it to assume the role ### AssumeRole with role previously assumed by action in same workflow ```yaml - name: Configure AWS Credentials - uses: aws-actions/configure-aws-credentials@v4.3.0 + uses: aws-actions/configure-aws-credentials@v4.3.1 with: aws-region: us-east-2 role-to-assume: arn:aws:iam::123456789100:role/my-github-actions-role role-session-name: MySessionName - name: Configure other AWS Credentials - uses: aws-actions/configure-aws-credentials@v4.3.0 + uses: aws-actions/configure-aws-credentials@v4.3.1 with: aws-region: us-east-2 role-to-assume: arn:aws:iam::987654321000:role/my-second-role @@ -434,7 +434,7 @@ role, `arn:aws:iam::987654321000:role/my-second-role`. ### AssumeRole with static IAM credentials in repository secrets ```yaml - name: Configure AWS Credentials - uses: aws-actions/configure-aws-credentials@v4.3.0 + uses: aws-actions/configure-aws-credentials@v4.3.1 with: aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }} aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }} @@ -453,7 +453,7 @@ name, like `role-to-assume: my-github-actions-role`. ```yaml - name: Configure AWS Credentials 1 id: creds - uses: aws-actions/configure-aws-credentials@v4.3.0 + uses: aws-actions/configure-aws-credentials@v4.3.1 with: aws-region: us-east-2 role-to-assume: arn:aws:iam::123456789100:role/my-github-actions-role @@ -462,7 +462,7 @@ name, like `role-to-assume: my-github-actions-role`. run: | aws sts get-caller-identity - name: Configure AWS Credentials 2 - uses: aws-actions/configure-aws-credentials@v4.3.0 + uses: aws-actions/configure-aws-credentials@v4.3.1 with: aws-region: us-east-2 aws-access-key-id: ${{ steps.creds.outputs.aws-access-key-id }} From 7474bc4690e29a8392af63c5b98e7449536d5c3a Mon Sep 17 00:00:00 2001 From: AWS SDKs and Tools bot <45836109+aws-sdk-osds@users.noreply.github.com> Date: Mon, 4 Aug 2025 16:18:24 -0700 Subject: [PATCH 4/4] chore(main): release 4.3.1 --- .release-please-manifest.json | 2 +- CHANGELOG.md | 7 +++++++ package-lock.json | 4 ++-- package.json | 2 +- 4 files changed, 11 insertions(+), 4 deletions(-) diff --git a/.release-please-manifest.json b/.release-please-manifest.json index 0ae5eb18e..01b387dac 100644 --- a/.release-please-manifest.json +++ b/.release-please-manifest.json @@ -1,5 +1,5 @@ { ".release-please-manifest.json": "4.0.2", "package.json": "4.0.2", - ".": "4.3.0" + ".": "4.3.1" } diff --git a/CHANGELOG.md b/CHANGELOG.md index 20b3e5b7f..ba7e5f19f 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,6 +2,13 @@ All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines. +## [4.3.1](https://github.com/aws-actions/configure-aws-credentials/compare/v4.3.0...v4.3.1) (2025-08-04) + + +### Bug Fixes + +* update readme to 4.3.1 ([#1424](https://github.com/aws-actions/configure-aws-credentials/issues/1424)) ([be2e7ad](https://github.com/aws-actions/configure-aws-credentials/commit/be2e7ad815e27b890489a89ce2717b0f9e26b56e)) + ## [4.3.0](https://github.com/aws-actions/configure-aws-credentials/compare/v4.2.1...v4.3.0) (2025-08-04) diff --git a/package-lock.json b/package-lock.json index 104370c07..e43616aed 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,12 +1,12 @@ { "name": "configure-aws-credentials", - "version": "4.3.0", + "version": "4.3.1", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "configure-aws-credentials", - "version": "4.3.0", + "version": "4.3.1", "license": "MIT", "dependencies": { "@actions/core": "^1.11.1", diff --git a/package.json b/package.json index ceedc8477..ee2d8337a 100644 --- a/package.json +++ b/package.json @@ -1,7 +1,7 @@ { "name": "configure-aws-credentials", "description": "A GitHub Action to configure AWS credentials", - "version": "4.3.0", + "version": "4.3.1", "scripts": { "build": "tsc", "lint": "biome check --error-on-warnings ./src",