You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Update Node runtime to Node24 due to upcoming retirement on Node20 #35
I understand people would like to see this happen. And I also think the sooner the better. And I appreciate people showing that they consider this an important issue.
That said, GitHubs own timeline for migrating actions is the fall of this year. So there's no extreme haste required either. Taking that into account along with the fact that I have a job and maintain a large amount of other open source projects too, and I actually have things to do unrelated to computers, I have been waiting for someone to open a PR.
So if somesone feels this needs to be done faster than GitHub's own timeline, please do open a PR to hurry things along.
I know that this may break out-of-date self-hosted runners pinned to v2. But on the other hand, its going to prevent breakage for up-to-date runners pinned to v2 once node20 is dropped. Self-hosted runners can pin to v2.1 instead to stick with the node20 version (this is also mentioned in the README).
Activity
de-vri-es commentedon Mar 18, 2026
Thanks for opening the issue! I think someone already started working on this, so I will give them a little time to submit a PR before I do it myself!
dannywpjr commentedon Apr 8, 2026
Hope this is completed soon
Manoj1723 commentedon Apr 17, 2026
When will this be available? It's been a month since this issue is opened.
de-vri-es commentedon Apr 17, 2026
Hey all,
I understand people would like to see this happen. And I also think the sooner the better. And I appreciate people showing that they consider this an important issue.
That said, GitHubs own timeline for migrating actions is the fall of this year. So there's no extreme haste required either. Taking that into account along with the fact that I have a job and maintain a large amount of other open source projects too, and I actually have things to do unrelated to computers, I have been waiting for someone to open a PR.
So if somesone feels this needs to be done faster than GitHub's own timeline, please do open a PR to hurry things along.
de-vri-es commentedon Apr 17, 2026
I started on it anyway: #36
Turns out it was more work than anticipated thanks to a heap of churn in the nodejs and actions ecosystem. But what else is new ^_^
de-vri-es commentedon Apr 17, 2026
Fixed with #36 and released as
v2.2.0.I know that this may break out-of-date self-hosted runners pinned to
v2. But on the other hand, its going to prevent breakage for up-to-date runners pinned tov2once node20 is dropped. Self-hosted runners can pin tov2.1instead to stick with thenode20version (this is also mentioned in the README).de-vri-es commentedon Apr 17, 2026
Thanks again for reporting the issue!