fix: Chrome for Testing downloads have a new URL

[OrKoN]

See GoogleChromeLabs/chrome-for-testing#108

Closes #11925

To make the older releases of @puppeteer/browsers to work with the new endpoint: use the --base-url https://storage.googleapis.com/chrome-for-testing-public parameter on the command line or the baseUrl on the InstallOptions https://pptr.dev/browsers-api/browsers.installoptions.

[mathiasbynens]

LGTM once the tests pass (which would mean the old assets have been copied over to the new bucket)

[worenga]

related #11925

[christian-bromann]

@OrKoN is it possible to release this soonish? This is currently breaking all WebdriverIO tests for people that don't have a specific browser version defined. Also could you please backport this change to @puppeteer/browser@v1.x since we can't update @puppeteer/browser due to the fact that it dropped support for Node.js v16. WebdriverIO v8 can't drop Node.js v16 support.

[ngan]

You can work around this for now, like so:

npx @puppeteer/browsers install chrome@stable --path /usr/local --base-url https://storage.googleapis.com/chrome-for-testing-public

[OrKoN]

@christian-bromann tests do not pass yet, meaning the binaries are not back-filled at the new endpoint.

@mathiasbynens have you resumed dashboard updates before the sync was done?

[OrKoN]

@mathiasbynens looks like it is been partially back-filled.

[renemadsen]

@OrKoN Will there be a new npm package soon, so we can fix all our broken ci/cd which uses WebdriverIO and in turn puppeteer?

[mathiasbynens]

@mathiasbynens have you resumed dashboard updates before the sync was done?

The sync was completed last night, after which I resumed dashboard updates.

However, any existing software that uses the CfT API to get version numbers (e.g. “which version is the latest Canary?”) but hardcodes the old URL format instead of using the -with-downloads endpoints might now receive a version number for which the downloads are not available on the old host. This software must be updated.

Thanks for updating Puppeteer!

[christian-bromann]

You can work around this for now, like so:

Thanks a lot, this will allow us to move forward without having to backport this change to v1.x.