chore: upgrade actions to Node 24 runtime (SHA-pinned) - #106
Open
John C. Bland II (johncblandii) wants to merge 1 commit into
Open
John C. Bland II (johncblandii) wants to merge 1 commit into
John C. Bland II (johncblandii) wants to merge 1 commit into
Conversation
John C. Bland II (johncblandii)
added
the
patch
John C. Bland II (johncblandii)
requested review from
Veronika Gnilitska (gberenice) and
Kevin (kevcube)
August 13, 2026 17:04
John C. Bland II (johncblandii)
added
the
patch
Copilot started reviewing on behalf of
John C. Bland II (johncblandii)
August 13, 2026 17:04
View session
There was a problem hiding this comment.
Pull request overview
Updates this repository’s composite action and test workflow to use SHA-pinned GitHub Actions versions that run on the Node 24 Actions runtime, aligning with the Node 20 deprecation and improving supply-chain safety via immutable pins.
Changes:
- SHA-pin
actions/setup-node,actions/cache,hashicorp/setup-terraform,aws-actions/configure-aws-credentials, andcloudposse/github-action-setup-atmoswith verified-tag comments inaction.yml. - Update
aws-actions/configure-aws-credentialsinputs to use strict boolean strings ("false") formask-aws-account-id. - SHA-pin
nick-fields/assert-actionin thetest-atmos_proworkflow.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| action.yml | Pins key third-party actions to Node 24–runtime SHAs and updates strict boolean input values for AWS credentials steps. |
| .github/workflows/test-atmos_pro.yml | Pins nick-fields/assert-action to a Node 24–runtime SHA with a version comment. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Kevin (kevcube)
approved these changes
Aug 13, 2026
This branch has not been deployed
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.
what
SHA-pinned with precise version comments:
actions/setup-node@v4→@82076278...# v7.0.0actions/cache@v4→@55cc8345...# v6.1.0nick-fields/assert-action@v2→@0efd6166...# v4.0.1cloudposse/github-action-setup-atmos@v2→@60878d48...# v3.5.0hashicorp/setup-terraform@v3→@dfe3c3f8...# v4.0.1aws-actions/configure-aws-credentials@v4→@e6de0542...# v6.2.3aws-actions/configure-aws-credentialsv5+ requires strict booleans: rewrotemask-aws-account-id: "no"→"false"in the three credential steps ofaction.ymlwhy
are already being force-migrated to Node 24
matching the org's direction in chore: upgrade actions to Node 24 runtime and enforce SHA pinning .github#261
Supersedes #105
Supersedes #104
Supersedes #102
Supersedes #99
Supersedes #98
Supersedes #97
references
still on Node 20
cloudposse-github-actions/install-gh-releases@v1— no Node 24 release exists yet