Move the GitHub actions off the deprecated Node 20 - #2
Merged
Conversation
checkout v4 to v7, setup-python v5 to v7, upload-artifact v4 to v7. All three declared Node 20, which the runners now force onto Node 24 while warning on every job. Nothing was broken by it, but 'forced' is the stage before removal, and the one workflow that must not break when it happens is release.yml. pypa/gh-action-pypi-publish stays on release/v1: it is a rolling tag and is already current. Co-Authored-By: Claude Opus 5 (1M context) <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.
Every CI job has been warning:
actions/checkoutactions/setup-pythonactions/upload-artifactpypa/gh-action-pypi-publish@release/v1is unchanged — a rolling tag, already current at v1.14.2.Nothing was broken by the warning, but "forced" is the stage before removal, and the workflow that must not break when that happens is
release.yml.Checking the run on this PR is the verification: it exercises every changed pin except the
upload-artifactbump, which the acceptance job covers, andrelease.yml, which only a tag triggers. The remaining Node 20 warnings should be gone.I reviewed the release notes for all three; none of the majors crossed here change any input this repo passes.
🤖 Generated with Claude Code