chore: upgrade actions to Node 24 runtime (SHA-pinned) - #67
Open
John C. Bland II (johncblandii) wants to merge 1 commit into
Open
chore: upgrade actions to Node 24 runtime (SHA-pinned)#67John 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)
added
the
patch
Copilot started reviewing on behalf of
John C. Bland II (johncblandii)
August 13, 2026 17:04
View session
|
/spacelift summary Spacelift Triggered Stacks (1)/spacelift test-t-test-test-workspace-enabled preview |
There was a problem hiding this comment.
Pull request overview
Updates this repository’s GitHub Action dependencies to address the GitHub Actions Node runtime deprecation by moving selected uses: references to Node 24-capable releases and pinning them to specific upstream SHAs.
Changes:
- Pin
actions/checkoutto a specific SHA corresponding tov7.0.1in the composite action and test workflows. - Pin
nick-fields/assert-actionto a specific SHA corresponding tov4.0.1in assertion steps.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| action.yml | Pins actions/checkout used by the composite action to a SHA (v7.0.1). |
| .github/workflows/test-no-changes.yml | Pins actions/checkout and nick-fields/assert-action to SHAs (v7.0.1, v4.0.1). |
| .github/workflows/test-filter-workspace-enabled.yml | Pins actions/checkout to a SHA (v7.0.1). |
| .github/workflows/test-changes.yml | Pins actions/checkout and nick-fields/assert-action to SHAs (v7.0.1, v4.0.1). |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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
action.ymlto versions running on theNode 24 runtime, SHA-pinned with precise version comments:
actions/checkout@v4→@3d3c42e5...# v7.0.1nick-fields/assert-action@v2→@0efd6166...# v4.0.1Supersedes #66
Supersedes #65
why
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
references
still on Node 20
cloudposse-github-actions/install-gh-releases@v1— no Node 24 release exists yet; left as-isscope note
actions/checkout,nick-fields/assert-action). Other refs (github-action-atmos-affected-stacks@v6,setup-spacectl@v1.0.0) already run Node 24-era or composite runtimes and are left for a dedicated repo-wide pinning pass;cloudposse/.github/...@mainreusable-workflow refs stay on@mainper the org's distribution model (see chore: upgrade actions to Node 24 runtime and enforce SHA pinning .github#261's verifier exemption).