Repository navigation
chore(ci): move off the actions still running on Node 20 #skip-changeset - #47
Merged
Merged
Conversation
- GitHub deprecated Node 20 on its runners and was forcing checkout, setup-node and the three Pages actions onto Node 24 - Bumped only the five the annotations actually named, each to its current major; the inputs are unchanged because the usage is vanilla - changesets/action stays on v1 on purpose: it was not flagged, and it is the release path — a major bump there earns nothing and risks the version pull request
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.
GitHub deprecated Node 20 on its runners and was forcing these onto Node 24, with an annotation on every run.
Bumped, each to its current major:
actions/checkoutactions/setup-nodeactions/configure-pagesactions/upload-pages-artifactactions/deploy-pagesThe list comes from the annotations themselves, per workflow, not from a guess:
upload-artifact@v4was also named, and it is whatupload-pages-artifact@v3uses internally, so bumping the wrapper is what clears it.changesets/actionstays on v1. It was not flagged, and it is the release path — a major bump there earns nothing and risks the version pull request, which is how every release starts.No input changed: the usage is vanilla throughout (
checkoutwith no inputs,setup-nodewithnode-versionandcache, the Pages actions in the documented order). This is a CI-only change, so the blast radius is this pull request — which is also what proves it.