2020-04-28 20:37:23 +03:00
|
|
|
{
|
2020-07-02 01:22:29 +03:00
|
|
|
"comment": "Do not edit this file, use utils/roll_browser.js",
|
2020-04-28 20:37:23 +03:00
|
|
|
"browsers": [
|
|
|
|
|
{
|
|
|
|
|
"name": "chromium",
|
2024-06-06 21:02:58 +03:00
|
|
|
"revision": "1122",
|
2022-05-05 14:17:13 +03:00
|
|
|
"installByDefault": true,
|
2024-06-06 21:02:58 +03:00
|
|
|
"browserVersion": "126.0.6478.36"
|
2020-04-28 20:37:23 +03:00
|
|
|
},
|
2022-04-22 19:43:57 +03:00
|
|
|
{
|
|
|
|
|
"name": "chromium-tip-of-tree",
|
2024-06-06 17:49:45 +03:00
|
|
|
"revision": "1229",
|
2022-05-05 14:17:13 +03:00
|
|
|
"installByDefault": false,
|
2024-06-06 17:49:45 +03:00
|
|
|
"browserVersion": "127.0.6523.0"
|
2022-04-22 19:43:57 +03:00
|
|
|
},
|
2020-04-28 20:37:23 +03:00
|
|
|
{
|
|
|
|
|
"name": "firefox",
|
2024-06-07 10:22:08 +03:00
|
|
|
"revision": "1453",
|
2022-05-05 14:17:13 +03:00
|
|
|
"installByDefault": true,
|
2024-05-19 17:28:32 +03:00
|
|
|
"browserVersion": "126.0"
|
2020-04-28 20:37:23 +03:00
|
|
|
},
|
2021-04-20 07:26:33 +03:00
|
|
|
{
|
2021-06-08 19:34:17 +03:00
|
|
|
"name": "firefox-beta",
|
2024-06-07 10:22:22 +03:00
|
|
|
"revision": "1453",
|
2022-05-05 14:17:13 +03:00
|
|
|
"installByDefault": false,
|
2024-05-19 17:28:32 +03:00
|
|
|
"browserVersion": "127.0b3"
|
2021-04-20 07:26:33 +03:00
|
|
|
},
|
2020-04-28 20:37:23 +03:00
|
|
|
{
|
|
|
|
|
"name": "webkit",
|
2024-06-06 21:17:17 +03:00
|
|
|
"revision": "2022",
|
fix(installer): retain browsers installed via Playwrigth CLI (#5904)
Browser registry is responsible for 3 things:
1. Remove downloaded browsers if there are no packages that refer to them
2. Install default browsers needed for the current package
3. Install browsers on-demand when used through Playwright CLI
Currently, registry relies on a single "download" field in `browsers.json`
to carry both (1) and (2). However, browsers in (3) are marked as
`download: false` so that they aren't installed automatically in (2), so
auto-remove procedure in (1) removes them on subsequent installation.
One possible approach to fix this would be modifying package's `browsers.json` to
change `download: false` to `true` when browsers are installed with
Playwright CLI. This approach was explored here:
https://github.com/microsoft/playwright/commit/bc04a51800d6d6322e43b7d147fc0ec42181e084
We decided against this since we have a history of issues related to
package modifications after NPM installation. This breaks all
sorts of yarn/npm caching mechanisms.
Instead, this patch is a two-step refactor:
- remove the "download" field in `browsers.json`. Now, all registries
(including old ones from previously-released versions) will retain any
browsers that are mentioned in the `browsers.json`.
- add a new flag "installByDefault", that is **only used** for default
installation.
With this change, the registry tasks are done like this:
- (1) auto-removal: if browser has a back reference, it is retained,
otherwise it is removed from registry
- (2) default installation: use only `installByDefault` to carry default installations
- (3) CLI installation: simply installs browsers. Since we retain
everythings that's referenced in (1), browsers aren't removed.
Fixes #5902
2021-03-22 21:43:29 +03:00
|
|
|
"installByDefault": true,
|
2021-03-17 19:34:09 +03:00
|
|
|
"revisionOverrides": {
|
2022-03-16 02:09:56 +03:00
|
|
|
"mac10.14": "1446",
|
2022-10-20 20:52:34 +03:00
|
|
|
"mac10.15": "1616",
|
2023-03-29 03:34:39 +03:00
|
|
|
"mac11": "1816",
|
2024-05-16 21:10:27 +03:00
|
|
|
"mac11-arm64": "1816",
|
|
|
|
|
"mac12": "2009",
|
|
|
|
|
"mac12-arm64": "2009"
|
2022-05-05 14:17:13 +03:00
|
|
|
},
|
2023-10-11 00:49:49 +03:00
|
|
|
"browserVersion": "17.4"
|
2021-02-03 20:19:11 +03:00
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"name": "ffmpeg",
|
2023-04-27 11:37:39 +03:00
|
|
|
"revision": "1009",
|
fix(installer): retain browsers installed via Playwrigth CLI (#5904)
Browser registry is responsible for 3 things:
1. Remove downloaded browsers if there are no packages that refer to them
2. Install default browsers needed for the current package
3. Install browsers on-demand when used through Playwright CLI
Currently, registry relies on a single "download" field in `browsers.json`
to carry both (1) and (2). However, browsers in (3) are marked as
`download: false` so that they aren't installed automatically in (2), so
auto-remove procedure in (1) removes them on subsequent installation.
One possible approach to fix this would be modifying package's `browsers.json` to
change `download: false` to `true` when browsers are installed with
Playwright CLI. This approach was explored here:
https://github.com/microsoft/playwright/commit/bc04a51800d6d6322e43b7d147fc0ec42181e084
We decided against this since we have a history of issues related to
package modifications after NPM installation. This breaks all
sorts of yarn/npm caching mechanisms.
Instead, this patch is a two-step refactor:
- remove the "download" field in `browsers.json`. Now, all registries
(including old ones from previously-released versions) will retain any
browsers that are mentioned in the `browsers.json`.
- add a new flag "installByDefault", that is **only used** for default
installation.
With this change, the registry tasks are done like this:
- (1) auto-removal: if browser has a back reference, it is retained,
otherwise it is removed from registry
- (2) default installation: use only `installByDefault` to carry default installations
- (3) CLI installation: simply installs browsers. Since we retain
everythings that's referenced in (1), browsers aren't removed.
Fixes #5902
2021-03-22 21:43:29 +03:00
|
|
|
"installByDefault": true
|
2022-11-01 02:08:26 +03:00
|
|
|
},
|
|
|
|
|
{
|
|
|
|
|
"name": "android",
|
|
|
|
|
"revision": "1000",
|
|
|
|
|
"installByDefault": false
|
2020-04-28 20:37:23 +03:00
|
|
|
}
|
|
|
|
|
]
|
|
|
|
|
}
|
