ci: update leaderboard workflow for Node 24#6654
Open
Thecesar85 wants to merge 1 commit into
Open
Conversation
Author
|
Given how close the Node 24 switchover date is, I decided to clean this warning path up proactively. This keeps the leaderboard workflow quieter now and reduces the chance of a near-term maintenance surprise once GitHub flips the default runtime. |
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.
Summary
actions/checkoutfromv4tov5in theupdate-pr-leaderboardworkflowWhy
GitHub is close to switching JavaScript actions to Node 24 by default, and the current workflow emits a deprecation warning for
actions/checkout@v4. Since the transition date is close, I decided to improve the workflow now and remove that warning path before it becomes operational noise or a future breakage point.Validation