Open
Conversation
GitHub is forcing Node 24 on runners June 2 and removing Node 20 support on September 16. Both action.yml files declared `using: node20`, which would break the action on that date. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
3 tasks
ronens88
added a commit
that referenced
this pull request
May 8, 2026
Backport of #115 to the v0 line. GitHub forces Node 24 on runners June 2 and removes Node 20 support September 16, after which the action would fail to start on Node-20-pinned runtimes. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Summary
action.ymlfiles declaredusing: node20. GitHub is forcing Node 24 on hosted runners on June 2, 2026 and removing Node 20 support on September 16, 2026 — without this bump, the action breaks on that date.node20→node24in the rootaction.ymlandattest/action.yml. No source/dist rebuild needed (action runtime is declared independently of the bundled JS).Risk
actions/runnerthat ships Node 24. Customers on older runners will fail with "Node 24 not found." Same constraint applies to GHES.dist/*.jsisncc-transpiled; runtime-compatible with Node 24. The existingscripts/fix-esm-require.jsshim (added in 1bec56a for Node 20+ ESM/require interop) remains effective.v0.10.xasv0.10.1so customers pinned to@v0are not stranded.Test plan
verify-prworkflow passes on this PR@chore/node24-bump(or wait for first run on a Node 24 runner post-merge)v1floating tag and announce the runner-version requirement to customers