chore(ci): bump mlugg/setup-zig once it ships a Node-24 action
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 52/100
Research direction
Start by reading release.yml and checking the mlugg/setup-zig releases for a version whose action.yml targets Node 24. When one is available, update the action pin and verify the workflow still uses the intended setup; if upstream has not shipped one before Node 20 is removed, evaluate the alternatives listed in the issue.
Written by the indexing model from the issue text.
Description
Context
release.yml uses mlugg/setup-zig@v2 (cargo-zigbuild's cross-linker for the musl builds). CI emits:
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24:
mlugg/setup-zig@v2.
(https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/)
We're already on the latest @v2 (resolves to v2.2.1) — the warning is upstream's own action.yml still declaring using: node20, so there's nothing for us to bump yet. It's a warning, not a failure: the runner force-runs it on Node 24 today.
Why file it
When GitHub removes Node 20 from the runners, an action still targeting node20 will break. So this must be resolved before that removal date.
Action (later)
- Watch
mlugg/setup-zigfor a release whoseaction.ymltargetsnode24; bump the pin when it lands. - If upstream stalls past the Node-20 removal window, evaluate an alternative (e.g.
goto-bus-stop/setup-zig,korandoru/setup-zig, or install Zig directly in arun:step).
Discovered while wiring the release → homebrew/apt dispatch (#137).
- Dominant language
- Rust
- Stars
- 17
- Forks
- 2
- Avg merge
- 41m
- Merged PRs (30d)
- 389
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Tripstack-Corp/spyc
-
area:fs type:fix
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Tripstack-Corp/spyc#1002 ·
Maintainers usually reply within 1 day
-
area:fs type:fix
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Tripstack-Corp/spyc#1005 ·
Maintainers usually reply within 1 day
-
area:fs type:fix
Difficulty 4/5 1-2 days Newbie friendliness 57/100
Tripstack-Corp/spyc#1004 ·
Maintainers usually reply within 1 day
-
area:shell type:fix
Difficulty 4/5 3-5 days Newbie friendliness 53/100
Tripstack-Corp/spyc#1003 ·
Maintainers usually reply within 1 day
-
area:agent type:fix
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Tripstack-Corp/spyc#1000 ·
Maintainers usually reply within 1 day
All issues in Tripstack-Corp/spyc
Similar issues
-
A match arm above the largest i64 is compared as 0Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
DioxusLabs/dioxus#6063 ·
Maintainers usually reply within 1 day
-
`nsh-core` fails to compile when taffy's default `calc` feature is enabled elsewhere in the graphOpen
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
longbridge/nsh#966 ·
Maintainers usually reply within 1 day
-
Windows docs: pin a tested ConPTY version for Kitty graphics; 1.25.260930003 corrupts large uploadsOpen
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
raphamorim/rio#2021 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
non7top/sigstore-shell#38 ·
Maintainers usually reply within 1 day