Repository navigation
Move the CI actions off deprecated Node 20 - #45
Merged
Merged
Conversation
Every run was printing the same deprecation warning: checkout, setup-python, setup-node, and the artifact actions all still target Node 20, which the runners now force onto Node 24 and will stop supporting. This bumps each to the major that ships on Node 24 — checkout v5, setup-python v6, setup-node v5, upload/download-artifact v5 — so the warning goes away before the forcing becomes a failure. No workflow logic changes. The `cache:` and `cache-dependency-path:` options these steps rely on exist unchanged in the new majors, and upload- and download-artifact move together so the tag build and its publish job still speak the same artifact format. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Every CI and Release run printed the same deprecation warning:
actions/checkout,actions/setup-python,actions/setup-node, and the artifact actions still target Node 20, which the runners now force onto Node 24 and will eventually drop.Bumps each to the current Node 24 major:
No workflow logic changes. The
cache:/cache-dependency-path:options exist unchanged in the new majors, and upload/download-artifact move together so the tag build and its publish job still share one artifact format.🤖 Generated with Claude Code