-
Notifications
You must be signed in to change notification settings - Fork 4.6k
Try regenerating package lock #72991
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
|
Size Change: 0 B Total Size: 2.45 MB ℹ️ View Unchanged
|
|
I'll go ahead and merge this, see if it works. I think some of the CI jobs that run on trunk don't run on PR, so there's a chance it won't fix things. |
|
Thanks, @talldan! |
|
Flaky tests detected in 92296ed. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/19093541313
|
|
It didn't work for node 24 jobs. I'm trying again in #72991, but this time it's an even bigger diff. 🤷♂️ |
What?
Tries regenerating the package-lock.json to see if it fixes the issue here - #72980 (comment).
There are a lot of changes 🤷♂️