[GH-ISSUE #5883] Allow using node24 #1273

Closed
opened 2026-03-01 21:50:05 +03:00 by kerem · 8 comments
Owner

Originally created by @ChristopherHX on GitHub (Jul 23, 2025).
Original GitHub issue: https://github.com/nektos/act/issues/5883

Act version

N/A

Feature description

As per https://github.com/actions/runner/releases/tag/v2.327.0

I am in favour of allowing node00 - node99, so node upgrade would not affect act at all.

We do not bundle node and are not going to do this in near future.

Originally created by @ChristopherHX on GitHub (Jul 23, 2025). Original GitHub issue: https://github.com/nektos/act/issues/5883 ### Act version N/A ### Feature description As per https://github.com/actions/runner/releases/tag/v2.327.0 I am in favour of allowing node00 - node99, so node upgrade would not affect act at all. We do not bundle node and are not going to do this in near future.
kerem 2026-03-01 21:50:05 +03:00
  • closed this issue
  • added the
    kind/bug
    label
Author
Owner

@sugurutakahashi-1234 commented on GitHub (Aug 12, 2025):

GitHub Actions runner v2.327.1 supports node24, and official actions like actions/checkout@v5 have migrated to it. However, act v0.2.80 doesn't recognize node24 yet.

This forces us to stay on node20 to keep local testing working. Would be great to have node24 support in act soon.

<!-- gh-comment-id:3178217733 --> @sugurutakahashi-1234 commented on GitHub (Aug 12, 2025): GitHub Actions runner v2.327.1 supports node24, and official actions like actions/checkout@v5 have migrated to it. However, act v0.2.80 doesn't recognize node24 yet. This forces us to stay on node20 to keep local testing working. Would be great to have node24 support in act soon.
Author
Owner

@ericLemanissier commented on GitHub (Aug 12, 2025):

We are also impacted by this problem. Trying to use actions/checkout@v5 fails with The runs.using key in action.yml must be one of: [composite docker node12 node16 node20 go], got node24

<!-- gh-comment-id:3178814368 --> @ericLemanissier commented on GitHub (Aug 12, 2025): We are also impacted by this problem. Trying to use `actions/checkout@v5` fails with `The runs.using key in action.yml must be one of: [composite docker node12 node16 node20 go], got node24`
Author
Owner

@ChristopherHX commented on GitHub (Aug 12, 2025):

nektos/act CI is now broken due to the hello world js action upgraded to node24

<!-- gh-comment-id:3179779454 --> @ChristopherHX commented on GitHub (Aug 12, 2025): nektos/act CI is now broken due to the hello world js action upgraded to node24
Author
Owner

@FidelusAleksander commented on GitHub (Aug 28, 2025):

@ChristopherHX is this included in any of the tagged versions?

<!-- gh-comment-id:3232940800 --> @FidelusAleksander commented on GitHub (Aug 28, 2025): @ChristopherHX is this included in any of the tagged versions?
Author
Owner

@ChristopherHX commented on GitHub (Aug 28, 2025):

is this included in any of the tagged versions?

No, in two forks of act (actions-oss and gitea) it has been tagged a while ago.

<!-- gh-comment-id:3233779991 --> @ChristopherHX commented on GitHub (Aug 28, 2025): > is this included in any of the tagged versions? No, in two forks of act (actions-oss and gitea) it has been tagged a while ago.
Author
Owner

@FidelusAleksander commented on GitHub (Aug 28, 2025):

is this included in any of the tagged versions?

No, in two forks of act (actions-oss and gitea) it has been tagged a while ago.

@ChristopherHX I'm using act as a devcontainer feature - which downloads from this repository release assets.

Any plans on making a release on this repo so this works for the devcontainer users?

<!-- gh-comment-id:3233792929 --> @FidelusAleksander commented on GitHub (Aug 28, 2025): > > is this included in any of the tagged versions? > > No, in two forks of act (actions-oss and gitea) it has been tagged a while ago. @ChristopherHX I'm using `act` as a [devcontainer feature](https://github.com/dhoeric/features/blob/main/src/act/README.md) - which downloads from this repository release assets. Any plans on making a release on this repo so this works for the devcontainer users?
Author
Owner

@ChristopherHX commented on GitHub (Aug 28, 2025):

Next automated release on 1. September 2025 - v0.2.81 would include this.

<!-- gh-comment-id:3233900320 --> @ChristopherHX commented on GitHub (Aug 28, 2025): Next automated release on 1. September 2025 - v0.2.81 would include this.
Author
Owner

@millsks commented on GitHub (Aug 31, 2025):

I ran into this issue today with the prefix-dev/setup-pixi workflow. I downgraded their action to use node20, but I will check back in a few days when the new release is published. Thanks for updating this!

<!-- gh-comment-id:3239680179 --> @millsks commented on GitHub (Aug 31, 2025): I ran into this issue today with the [prefix-dev/setup-pixi](https://github.com/prefix-dev/setup-pixi/blob/v0.9.0/action.yml#L72) workflow. I downgraded their action to use node20, but I will check back in a few days when the new release is published. Thanks for updating this!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/act#1273
No description provided.