Skip to content

github-actions: bump aws-actions/configure-aws-credentials from 5 to 6 - #733

Merged
bgentry merged 2 commits into
masterfrom
dependabot/github_actions/aws-actions/configure-aws-credentials-6
Nov 1, 2026
Merged

bgentry merged 2 commits into
masterfrom
dependabot/github_actions/aws-actions/configure-aws-credentials-6

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 1, 2026

Copy link
Copy Markdown
Contributor

Bumps aws-actions/configure-aws-credentials from 5 to 6.

Release notes

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

v6.0.0

6.0.0 (2026-02-04)

⚠ BREAKING CHANGES

  • Update action to use node24 Note this requires GitHub action runner version v2.327.1 or later (#1632) (a7a2c11)

Features

Bug Fixes

  • properly output aws-account-id and authenticated-arn when using role-chaining (#1633) (7ceaf96)

v5.1.1

5.1.1 (2025-11-24)

Miscellaneous Chores

  • release 5.1.1 (56d6a58)
  • various dependency updates

v5.1.0

5.1.0 (2025-10-06)

Features

Bug Fixes

Changelog

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

6.2.1 (2026-06-26)

Bug Fixes

  • enforce allowed-account-ids on all auth paths (#1847) (4d281fb)

6.2.0 (2026-06-01)

Features

Bug Fixes

  • skip credential check on output-env-credentials: false (#1778) (58e7c47)
  • assumeRole failing from session tag size too large (#1808) (d6f5dc3)

6.1.3 (2026-05-28)

Bug Fixes

  • fix: allow kubelet token symlink in #1805

6.1.2 (2026-05-26)

Bug Fixes

Commits
  • e125382 chore(main): release 6.3.0 (#1963)
  • 438100a chore: add link to GH security docs (#1962)
  • e92ebcc chore: Update dist
  • 57b8365 feat: add translate-env-variables option (#1961)
  • cc49fa7 chore(docs): README main branch guidance (#1960)
  • 866cb16 chore(deps-dev): bump smol-toml from 1.7.0 to 1.7.2 (#1958)
  • 6782cb1 chore(deps-dev): bump generate-license-file from 4.2.4 to 4.2.5 (#1951)
  • c20509a chore: Update dist
  • 7a41fc6 chore(deps): bump @​aws-sdk/client-sts from 3.1121.0 to 3.1127.0 (#1954)
  • 726b713 chore(deps-dev): bump @​biomejs/biome from 2.5.11 to 2.5.12 (#1957)
  • Additional commits viewable in compare view

Dependabot compatibility score

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 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)

Bumps [aws-actions/configure-aws-credentials](https://github.com/aws-actions/configure-aws-credentials) from 5 to 6.
- [Release notes](https://github.com/aws-actions/configure-aws-credentials/releases)
- [Changelog](https://github.com/aws-actions/configure-aws-credentials/blob/main/CHANGELOG.md)
- [Commits](aws-actions/configure-aws-credentials@v5...v6)

---
updated-dependencies:
- dependency-name: aws-actions/configure-aws-credentials
  dependency-version: '6'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github-actions labels Nov 1, 2026

@bgentry bgentry left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 Codex review: Dependency security review is clear for the configured workflow; merge remains blocked by required Pro image CI.

Upgrade

  • aws-actions/configure-aws-credentials: v5 → v6 (resolved package 5.1.1 → 6.3.0).
  • Reviewed head: 5140b895d00ab8af9b7de7bf506842b3b6829a7d; base: 310c675a1dfe6eb9d22b0018c8c2e91aa0837042.

Security Review

  • Compared canonical upstream source, action metadata, both shipped main/cleanup bundles, packaging workflow, runtime dependency churn, registry sources and integrity metadata. No unexpected credential harvesting, exfiltration destination, process execution, or same-version integrity rewrite was found.
  • Resolved v5 to 61815dcd50bd041e203e49132bacad1fd04d2708, and v6/v6.3.0 to e1253824e5c10ff9df46874f81ed3ec929e19cfd. New main bundle SHA-256: e1382249ca353dce3a303062c504f875bedd09a1b4232b989a22967b8f87dff3; cleanup: 7534512a93c0785e46c461fe3fc850637d0e776593e20e07c46c8153cfdc29fe.
  • The existing OIDC role-assumption flow and credential cleanup remain. New profile writes, custom endpoints, custom session tags, and skip-cleanup behavior are unused by the supplied inputs. Node 24's runner requirement is compatible with the GitHub-hosted Ubuntu runners used here.
  • This is a routine major upgrade with hardening, not a confirmed advisory-driven security update. Existing application dependency overrides are unaffected.

Compatibility Verification

  • actionlint .github/workflows/docker-riverproui.yaml and git diff --check — passed.
  • Clean npm ci, npm run lint, npm run test:once (37 files / 278 tests), and npm run build — passed on Node 24.19.0 using an isolated checkout with byte-identical frontend/dependency inputs. Current-head CI independently passes the full six-job Go/PostgreSQL matrix, Go lint, sqlc verification, frontend checks on Node 24.21.0, release builds, and public image builds/manifests.
  • A maintainer-triggered retry of the failed Pro workflow still fails before building with Could not assume role with OIDC: Not authorized to perform sts:AssumeRoleWithWebIdentity. This also occurs on the v5 PRs. Required Pro AMD64 build and manifest checks remain failed/cancelled/skipped. AWS authorization must be repaired and these checks must pass before merge; local results do not bypass the rule.

Residual Risk

  • Upstream runtime audit reports advisories in [email protected], [email protected], and [email protected] plus their parent entries. No affected path was identified in this workflow: OIDC uses Node HTTPS, STS uses Smithy NodeHttpHandler, the action does not call the Undici dispatcher helper, and no PAC/FTP proxy or IP security allowlist is configured. These are remaining upstream exposures, not a claim of zero risk.
  • Bundles were statically inspected rather than independently rebuilt. Mutable major action tags remain an existing trust limitation. Successful real AWS authentication remains unverified until required Pro CI passes.

Bot-triggered image workflows cannot assume the publishing role, and a
rerun preserves the original actor context.

Create a maintainer-triggered branch update so the unchanged reviewed
tree can complete required image verification with the normal Actions
credentials.

@bgentry bgentry left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 Codex review: Approved after current-head dependency security and compatibility review.

Upgrade

  • aws-actions/configure-aws-credentials: v5 → v6, currently resolving to 5.1.1 → 6.3.0.
  • Reviewed head: 55c8119c4f66d621c922dc839f319627570bd817.

Security Review
Reused the exact upstream source/bundle, dependency graph, integrity and advisory evidence from the earlier review. v6 was re-resolved immediately before approval: annotated tag 4a1596c86fd706dc0521e32f0121ad1a6d1adb74 still peels to reviewed commit e1253824e5c10ff9df46874f81ed3ec929e19cfd. The main/cleanup bundle digests remain e1382249ca353dce3a303062c504f875bedd09a1b4232b989a22967b8f87dff3 / 7534512a93c0785e46c461fe3fc850637d0e776593e20e07c46c8153cfdc29fe.

The only head delta is verification-only commit 55c8119; Git confirms its tree is byte-identical to the initially reviewed head. No new artifact, hook, credential path, generated output, manifest or workflow rule is introduced. Expected OIDC role assumption and cleanup remain; optional profile/custom endpoint/PAC features stay unused. Node 24 is compatible with the hosted runners. Application overrides remain unaffected; their separate cleanup is handled in the addon upgrade.

Compatibility Verification

  • Local actionlint .github/workflows/docker-riverproui.yaml and git diff --check passed.
  • Clean frontend installation, lint, 278 tests and production build passed with identical frontend inputs. Tree-identical checks are reused; no source changed in the verification commit.
  • Every required current-head check passes, including all six Go/PostgreSQL jobs, Go lint, sqlc verification, frontend checks, release builds, CodeQL, public/Pro image builds on both architectures and both manifest jobs. The release-only Pro registry prefetch job is expected to skip on a pull request.
  • The maintainer-triggered update runs the normal workflow and successfully authenticates to AWS. It resolves the earlier Dependabot execution-context limitation without changing credentials, workflows, required checks or branch rules.

Residual Risk
Upstream runtime audit reports advisories in [email protected], [email protected] and [email protected] and parent entries. No affected path is identified here: OIDC uses Node HTTPS, STS uses Smithy NodeHttpHandler, the Undici dispatcher helper is unused, and no PAC/FTP proxy or IP security allowlist is configured. Generated bundles were statically inspected, not independently rebuilt; mutable major tags retain their existing trust limitation. No blocking issue is identified for this workflow.

@bgentry
bgentry merged commit 36b8f46 into master Nov 1, 2026
22 checks passed
@bgentry
bgentry deleted the dependabot/github_actions/aws-actions/configure-aws-credentials-6 branch November 1, 2026 23:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file github-actions

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant