Repository navigation
Actions: move to Node 24 versions - #22
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.
Moves every action to its current major version, all running on Node 24 (GitHub is retiring Node 20 for actions). Breaking changes checked: setup-node v5–v7 (caching already explicit; no npm publish), setup-python v6–v7 (no pip-install input; versions in use still supported), artifact actions (download by name, not ID), upload-pages-artifact v4+ (drops dotfiles; none in the build), docker actions (no removed inputs used).
release.ymlonly runs on a version tag, so its new versions (artifacts, docker, setup-python) are first exercised by the next release.