Bump the workflow action pins off Node 20 - #91
Merged
Merged
Conversation
checkout v4 and setup-uv v5 target Node 20, which the runners now force onto Node 24 with a deprecation warning, so CI logs one per job. codecov moves up with them. setup-uv publishes no moving tag above v7, hence the exact version. The publish action stays on release/v1, which is what upstream recommends.
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 run logs a deprecation warning: checkout v4 and setup-uv v5 target Node 20 and the runners force them onto Node 24.
setup-uv publishes no moving tag above v7, so that one is pinned to an exact version and needs a deliberate bump next time.
Nothing in the changed majors touches how these are called here: v8 of setup-uv dropped an old custom version manifest format that is not used here, and v9 stopped pruning its cache, which costs a little more cache space and no behavior. The release workflow calls checkout and setup-uv with the same inputs as CI, so this run exercises the same pins a release will use.