Bump checkout and setup-node to v7 - #260
Merged
Merged
Conversation
Both actions targeted Node 20, which runners now force onto Node 24 with a deprecation warning on every run.
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 workflow run printed a deprecation warning:
actions/checkout@v4andactions/setup-node@v4target Node 20, which runners already force onto Node 24.checkout@v4and 2setup-node@v4pins moved to@v7, across all 4 workflowsv7major tagsetup-python@v5in validate-plugins is untouched, it raises no warning yet