ci: move remaining workflows to Node 24 action runtimes - #37
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.
Problem
Recent hosted-runner logs warn that DSHelm still references JavaScript actions whose declared runtime is Node 20. GitHub is already forcing those actions onto Node 24, and Node 20 is scheduled to leave hosted runners on 2026-09-16.
Change
actions/checkout@v4to@v7;actions/setup-node@v4to@v7while keeping project Node22;pnpm/action-setup@v4references to the Node-24-native@v6.1.0while keeping pnpm11.7.0;checkout@v6/setup-node@v6lines unchanged to keep this migration minimal.Scope
No Node application-runtime change, pnpm version change, package graph change, release behavior change, or DSH compatibility claim is introduced.
Closes #36