wavefnd / wavefnd/Wave

Update GitHub Actions to Node.js 24-native releases

Open Beginner friendly
#426 0 comments 0 reactions 0 assignees View on GitHub
build good first issue
Dominant language
Rust
Stars
53
Forks
16
Avg merge
4h 22m
Merged PRs (30d)
46

Description

## Summary

Current CI runs emit deprecation notices because several official GitHub Actions still select a Node.js 20 runtime and GitHub transparently forces Node.js 24.

## Relevant workflows

- `.github/workflows/rust.yml`
- `.github/workflows/release.yml`

The repeated actions include checkout, Python setup, and artifact upload steps.

## Scope

Move each official action to an upstream release that declares a supported Node.js 24 runtime. Preserve the current workflow behavior, permissions, cache keys, artifact names, and target matrix.

## Acceptance criteria

- Official action versions are updated consistently in both workflows.
- CI no longer reports Node.js 20 forced-upgrade warnings for those actions.
- Rust, corpus, cross-target, native example, and release jobs keep their current behavior.
- Action inputs are checked against the selected upstream release notes.
- No unrelated workflow refactor is included.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing .github/workflows/rust.yml and .github/workflows/release.yml, focusing on the checkout, Python setup, and artifact upload actions. Check the selected upstream releases and their input compatibility, then run the relevant CI workflows. Done means both workflows use Node.js 24-native action releases without changing permissions, caches, artifacts, matrices, or job behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd
Issue type
Refactor
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
78/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.