-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Update package-lock.json to match 16.4.0 version number #53499
Conversation
Size Change: 0 B Total Size: 1.5 MB ℹ️ View Unchanged
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for fixing this! Looks like the version bump didn't go through due to conflicts after the node version upgrade; more info on this Slack thread
Thanks for catching! |
Thanks folks! I'll open up a follow-up PR to look at updating the Github workflow for version bumps so that the new nested version prop gets updated, too, in subsequent releases. |
Follow-up PR to update the |
What?
Update plugin version in
package-lock.json
to be 16.4.0.Why?
It looks like one line of the bump plugin version in #53489 might have been missed, as the static analysis Github action is currently failing with the following:
I'm wondering if this is related to the npm upgrade in #53426? CC: @youknowriad
How?
Update the affected line.
Separately, in a follow-up we might need to update the
Update plugin version
step in Github workflows, too:gutenberg/.github/workflows/build-plugin-zip.yml
Line 125 in eb6c362
However, for now, let's see if updating this line allows the Github actions to pass again.
Testing Instructions
Check that Github actions pass, specifically the static analysis job.