fix: run the action on node24 - #16
Merged
Merged
Conversation
GitHub Actions runners force node20 actions onto node24 and emit a deprecation warning on every run that uses this action: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/ - action.yml: using node20 -> node24 - esbuild --target=node20 -> node24 - @types/node ^20 -> ^24 - test workflow: actions/checkout v4 -> v7 (also node20) dist/ rebuilds byte-identical, so no bundle churn.
fireairforce
approved these changes
Aug 17, 2026
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
2 participants
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.
Every workflow that uses this action gets a warning on each run:
See the runner changelog. The runner already executes the action under node24, so this just makes
action.ymlsay so.action.yml:using: node20->node24esbuild --target=node20->node24@types/node^20->^24.github/workflows/test.yml:actions/checkout@v4->v7(v4 is also node20)dist/rebuilds byte-identical with the new target, so there is no bundle diff.tsc --noEmitpasses against@types/node@24.Hit this on cnpm/cnpmcore, where all 8 CI jobs carry the warning.
Note: consumers pin
utooland/setup-utoo@v1, and thev1tag currently points atmainHEAD. Thev1tag needs to be moved after this merges for the warning to actually clear.