chore(github): update actions from deprecated node-20 versions#9149
Merged
Conversation
Contributor
Author
|
docs is a pnpm project that runs a python script? wild. |
Collaborator
Yea there's no other good way to get dynamic API typings from python to be shown in the markdown. |
joshistoast
approved these changes
May 28, 2026
Collaborator
joshistoast
left a comment
There was a problem hiding this comment.
all tests pass and code changes look good
lstein
approved these changes
May 31, 2026
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
GitHub Actions have been reporting "Node.js 20 actions are deprecated." and warning that runners will use Node 24 next
monthweek (June 2nd, 2026).This updates the actions that I found triggering that warning to their current versions. I did take a look at the release notes for the actions, and didn't see breaking changes that are obviously applicable to our configuration.
QA Instructions
I'm not sure if this can entirely be tested on a PR from a fork. GitHub may limit which actions can be modified by an external PR, and some of the actions depend on triggers that don't come from a branch.