chore: fix generated files workflow by using newer node but pinning npm 10 - #2764
Merged
Conversation
|
Assigned |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the scheduled “Update automatically generated files” GitHub Actions workflow to run on a newer Node.js runtime while avoiding known breakages introduced by npm 11 (per the linked context from PR #2604).
Changes:
- Bump the cron-tasks workflow Node.js version from
20.xto24.x. - Add an explicit step to install and use
npm@10for the remainder of the workflow.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
nbbeeken
added
the
no-title-validation
dkwncho
approved these changes
Jul 8, 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.
#2604
The gyp bump causes an issue on node 20, in the PR above is when Kevin had to downgrade this flow to 20 to avoid issues but the real problem is with npm@11, we should be able to unblock for now on just a node upgrade.