Skip to content

chore: upgrade actions to Node 24 runtime (SHA-pinned) - #54

Open
John C. Bland II (johncblandii) wants to merge 1 commit into
mainfrom
chore/node24-runtime-upgrade
Open

John C. Bland II (johncblandii) wants to merge 1 commit into
mainfrom
chore/node24-runtime-upgrade

Conversation

@johncblandii

Copy link
Copy Markdown

what

  • Bump GitHub Actions references in the workflows to versions running on the Node 24 runtime,
    SHA-pinned with precise version comments:
    • actions/checkout@v4 → @3d3c42e5... # v7.0.1
    • actions/setup-node@v4 → @82076278... # v7.0.0
    • nick-fields/assert-action@v2 → @0efd6166... # v4.0.1
    • cloudposse/github-action-setup-atmos@v2 → @60878d48... # v3.5.0
    • hashicorp/setup-terraform@v3 → @dfe3c3f8... # v4.0.1
    • aws-actions/configure-aws-credentials@v4 → @e6de0542... # v6.2.3
  • aws-actions/configure-aws-credentials v5+ requires strict booleans: rewrote
    mask-aws-account-id: "no" → "false" in action.yml

why

  • GitHub is deprecating the Node 20 runtime; affected workflows emit a deprecation warning and
    are already being force-migrated to Node 24
  • SHA pinning with a verified tag comment makes the upgrade deliberate and supply-chain-safe,
    matching the org's direction in chore: upgrade actions to Node 24 runtime and enforce SHA pinning .github#261
  • Every pinned SHA was verified against its upstream tag

Supersedes #53
Supersedes #52
Supersedes #51
Supersedes #49
Supersedes #48
Supersedes #47

references

still on Node 20

  • cloudposse-github-actions/install-gh-releases@v1 — no Node 24 release exists yet

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Pull request overview

This PR updates the repository’s GitHub Actions usage to align with the Node 24 runtime deprecation timeline by switching key actions to Node 24–capable releases and pinning them to verified commit SHAs (with version comments) to improve supply-chain integrity. It also adjusts an AWS credentials action input to use the expected boolean-like value.

Changes:

  • SHA-pin actions/checkout, actions/setup-node, cloudposse/github-action-setup-atmos, hashicorp/setup-terraform, aws-actions/configure-aws-credentials, and nick-fields/assert-action to Node 24–compatible versions (with tag/version comments).
  • Update mask-aws-account-id to "false" to meet aws-actions/configure-aws-credentials v5+ strict boolean parsing expectations.
  • Apply the checkout/assert-action pins across the repo’s validation and test workflows.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.

Show a summary per file
File Description
action.yml Pins composite-action dependencies to Node 24–compatible SHAs and updates mask-aws-account-id.
.github/workflows/validate-codeowners.yml Pins actions/checkout to a verified SHA for Node 24 runtime compatibility.
.github/workflows/test-positive.yml Pins actions/checkout and nick-fields/assert-action to verified SHAs.
.github/workflows/test-matrix-3-levels.yml Pins actions/checkout and nick-fields/assert-action to verified SHAs.
.github/workflows/test-matrix-2-levels.yml Pins actions/checkout and nick-fields/assert-action to verified SHAs.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

patch A minor, backward compatible change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants