Scripts: Update puppeteer-core dependency#64597
Conversation
…abilities by upgrading the `puppeteer-core` package to the latest version (23.1.0)
|
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. |
|
👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @jacobcassidy! In case you missed it, we'd love to have you join us in our Slack community. If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information. |
There was a problem hiding this comment.
Thank you for opening this issue. There are some details to polish related to the packages release process. I also see some CI issues reported that need to be further investigated. It looks like the changes to the package-lock.json will require some tweaks to make it work with the monorepo.
@Mamaduka and @swissspidy – do we still use Puppeteer for e2e tests in any place in Gutenebrg or WordPress core? What's the plan with the scripts powered by Puppeteer? How can we test these changes?
gziolo
left a comment
There was a problem hiding this comment.
Thank you for the follow-up commits. It's good to go.
puppeteer-core dependency
|
@gziolo Thanks for the instructions and follow-up. |
|
It looks like ESLint detected that |
What?
Upgrades the
puppeteer-corepackage to the latest version (23.1.0).Why?
This PR fixes the issue with
@wordpress/scriptshaving five high-severity vulnerabilities introduced with an older version of thepuppeteer-corepackage.See: #63771
How?
Removes the sub-dependencies versions with vulnerabilities.
Testing Instructions
npm install @wordpress/scripts path webpack-remove-empty-scripts --save-devnpm auditand you'll see a warning for 5 high-severity vulnerabilities.npm installto update the packages.