-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Scripts: Upgrade puppeteer dependency #20268
Conversation
d5d7c2a
to
de405ea
Compare
There are the same errors reported as in #20215
|
It's a known issue in Puppeteer, related issues: puppeteer/puppeteer#5363, puppeteer/puppeteer#5420. We will have to wait for |
Feel free to request my review once the fixed version of Puppeteer is released and this pull request is updated. |
Looking at the install script code, if the issue is caused by newer version of Chromium, I wonder if we could pin it to a revision from an earlier version (e.g. the version we're currently on).
|
de405ea
to
3e7f08c
Compare
Interesting idea. Trying with 3e7f08c. |
Size Change: 0 B Total Size: 856 kB ℹ️ View Unchanged
|
Unfortunately, it still fails even though it downloads Chromium pinned to Puppeteer 2.0: https://travis-ci.com/github/WordPress/gutenberg/jobs/297678868#L327
Update 1: Something went wrong, it's the latest version 🙃 Only the following works: PUPPETEER_CHROMIUM_REVISION=706915 npm install I will try with the original PR. Update 2:
|
It looks like we can do the upgrade together with switching to |
Description
I have some trouble with upgrading Puppeteer in #20215 so I want to do it in smaller steps.
The bundled
puppeteer
dependency has been updated from requiring^2.0.0
to requiring^2.1.1
. It uses Chromium v80 instead of Chromium v79. See the full list of changes.