starred/act

Fork 0

mirror of https://github.com/nektos/act.git synced 2026-04-26 09:25:54 +03:00

[GH-ISSUE #1967] Allow node20 in action.yml as action runtime #941

New issue

Closed

opened 2026-03-01 21:47:36 +03:00 by kerem · 8 comments

kerem commented

2026-03-01 21:47:36 +03:00

Owner

Originally created by @ChristopherHX on GitHub (Aug 14, 2023).
Original GitHub issue: https://github.com/nektos/act/issues/1967

Act version

v0.2.49

Feature description

See https://github.com/actions/runner/releases/tag/v2.308.0

Since act doesn't care about the version behind node why not just exec all node<number> via node?

Originally created by @ChristopherHX on GitHub (Aug 14, 2023). Original GitHub issue: https://github.com/nektos/act/issues/1967 ### Act version v0.2.49 ### Feature description See https://github.com/actions/runner/releases/tag/v2.308.0 Since act doesn't care about the version behind `node` why not just exec all `node<number>` via `node`?

kerem

2026-03-01 21:47:36 +03:00

closed this issue
added the
kind/feature-request
label

kerem commented

2026-03-01 21:47:37 +03:00

Author

Owner

@gilzow commented on GitHub (Sep 13, 2023):

Just ran into this issue as well where one of the actions in my workflow has updated to node20, but act now reports:

The runs.using key in action.yml must be one of: [composite docker node12 node16], got node20

and fails the action

@gilzow commented on GitHub (Sep 13, 2023): Just ran into this issue as well where one of the actions in my workflow has updated to node20, but act now reports: ``` The runs.using key in action.yml must be one of: [composite docker node12 node16], got node20 ``` and fails the action

kerem commented

2026-03-01 21:47:37 +03:00

Author

Owner

@mahmudz commented on GitHub (Sep 13, 2023):

Same issue here

Error: The runs.using key in action.yml must be one of: [composite docker node12 node16], got node20
OS: Mac 15 Sonoma Beta 7
Act Version: 0.2.50
Docker Version: 4.21.1

@mahmudz commented on GitHub (Sep 13, 2023): Same issue here ` Error: The runs.using key in action.yml must be one of: [composite docker node12 node16], got node20 ` OS: Mac 15 Sonoma Beta 7 Act Version: 0.2.50 Docker Version: 4.21.1

kerem commented

2026-03-01 21:47:37 +03:00

Author

Owner

@MichelFR commented on GitHub (Sep 14, 2023):

Same issue here, any workaround?
Using in gitea actions

Edit:

Okay found a workaround for now, needed to turn all versions back of the actions

@MichelFR commented on GitHub (Sep 14, 2023): Same issue here, any workaround? Using in gitea actions Edit: Okay found a workaround for now, needed to turn all versions back of the actions

kerem commented

2026-03-01 21:47:37 +03:00

Author

Owner

@mahmudz commented on GitHub (Sep 14, 2023):

@MichelFR Whats the procedure?

@mahmudz commented on GitHub (Sep 14, 2023): @MichelFR Whats the procedure?

kerem commented

2026-03-01 21:47:37 +03:00

Author

Owner

@NexZhu commented on GitHub (Sep 15, 2023):

@MichelFR Same issue here. Could you explain in detail?

@NexZhu commented on GitHub (Sep 15, 2023): @MichelFR Same issue here. Could you explain in detail?

kerem commented

2026-03-01 21:47:37 +03:00

Author

Owner

@teffcz commented on GitHub (Sep 17, 2023):

I have same problem with
"The runs.using key in action.yml must be one of: [composite docker node12 node16 go], got node20"

running basic CI job for building docker image using:
docker/setup-qemu-action@master
docker/setup-buildx-action@master
docker/login-action@master
docker/build-push-action@master

with docker image ghcr.io/catthehacker/ubuntu:act-20.04, but i tried sereval others (even node:20-bullseye) and nothing helped

from logs it looks it is failing at check docker/setup-qemu-action@master

@teffcz commented on GitHub (Sep 17, 2023): I have same problem with "The runs.using key in action.yml must be one of: [composite docker node12 node16 go], got node20" running basic CI job for building docker image using: docker/setup-qemu-action@master docker/setup-buildx-action@master docker/login-action@master docker/build-push-action@master with docker image ghcr.io/catthehacker/ubuntu:act-20.04, but i tried sereval others (even node:20-bullseye) and nothing helped from logs it looks it is failing at check docker/setup-qemu-action@master

kerem commented

2026-03-01 21:47:37 +03:00

Author

Owner

@renepyo commented on GitHub (Sep 21, 2023):

Same issue here, any workaround? Using in gitea actions

Edit:

Okay found a workaround for now, needed to turn all versions back of the actions

Can you tell me how to apply this workaround?

@renepyo commented on GitHub (Sep 21, 2023): > Same issue here, any workaround? Using in gitea actions > > Edit: > > Okay found a workaround for now, needed to turn all versions back of the actions Can you tell me how to apply this workaround?

kerem commented

2026-03-01 21:47:37 +03:00

Author

Owner

@jcarpenter12 commented on GitHub (Nov 7, 2023):

Same issue here, any workaround? Using in gitea actions
Edit:
Okay found a workaround for now, needed to turn all versions back of the actions

Can you tell me how to apply this workaround?

I had this issue this morning but the new version of act now supports node20 so it now works after upgrading act, unless I have misunderstood your question

@jcarpenter12 commented on GitHub (Nov 7, 2023): > > Same issue here, any workaround? Using in gitea actions > > Edit: > > Okay found a workaround for now, needed to turn all versions back of the actions > > Can you tell me how to apply this workaround? I had this issue this morning but the new version of act now supports node20 so it now works after upgrading act, unless I have misunderstood your question

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#941

No description provided.

Rows
Columns