chore: pin GitHub Actions to Node 24 runtimes - #45
Merged
Conversation
The v4/v5 majors of checkout, setup-python, cache, and the artifact actions still run on Node.js 20, which GitHub deprecates and force- migrates to Node 24 on 2026-06-16. Pin to the latest patch tag of each action whose action.yml declares `using: node24`: - actions/checkout v4 -> v6.0.3 - actions/setup-python v5 -> v6.2.0 - actions/cache v4 -> v5.0.5 - actions/upload-artifact v4 -> v7.0.1 - actions/download-artifact v4 -> v8.0.1 Verified each pinned tag's action.yml runs on node24. Artifact actions included because they emit the identical Node 20 deprecation warning. Co-Authored-By: Claude Sonnet 4.6 <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
1 participant
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
CI emits Node.js 20 deprecation warnings. GitHub force-migrates Node 20 actions to Node 24 on 2026-06-16, so the pinned action majors need to move to versions whose
action.ymldeclaresusing: node24.Important: as of 2026-06-02 the
v4/v5majors named in the original report still run Node 20 — a patch bump is not enough; the major version has to move. Each target tag below was verified by reading itsaction.ymlruns.usingfield.Changes
actions/checkoutv4v6.0.3node24actions/setup-pythonv5v6.2.0node24actions/cachev4v5.0.5node24actions/upload-artifactv4v7.0.1node24actions/download-artifactv4v8.0.1node24The artifact actions were included because they emit the identical Node 20 deprecation warning; leaving them on
v4would not fully clear the warnings..github/workflows/ci.ymlactions/checkout@v4->@v6.0.3(test job)actions/setup-python@v5->@v6.2.0(test job)actions/checkout@v4->@v6.0.3(integration job)actions/setup-python@v5->@v6.2.0(integration job)actions/cache@v4->@v5.0.5(integration job, embedding-model cache).github/workflows/publish.ymlactions/checkout@v4->@v6.0.3actions/setup-python@v5->@v6.2.0actions/upload-artifact@v4->@v7.0.1actions/download-artifact@v4->@v8.0.1All tags are exact patch versions (no floating majors), per pinning best practice.
Validation
Do not merge yet — opened so CI can validate the bumped actions run cleanly.
🤖 Generated with Claude Code