Repository navigation
chore: update Node.js runtime to node24 - #12
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Update
runs.usingin action.yml fromnode20tonode24.Impact assessment
node24has been supported since actions/runner v2.327.0 (July 2025). GitHub switched the default runtime to Node 24 on June 16, 2026, so this change simply aligns the declaration with the actual runtime@actions/core@1.10.1/@actions/github@6.0.1/valibot@1.2.0) have noenginesconstraints and work on Node 24.tool-versionsalready pinsnodejs 24.12.0, so CI and local builds/tests already run on Node 24