playwright/packages/playwright-core/browsers.json

59 lines
1.3 KiB
JSON
Raw Normal View History

{
"comment": "Do not edit this file, use utils/roll_browser.js",
"browsers": [
{
"name": "chromium",
"revision": "1064",
"installByDefault": true,
"browserVersion": "114.0.5735.35"
},
{
"name": "chromium-with-symbols",
"revision": "1064",
"installByDefault": false,
"browserVersion": "114.0.5735.35"
},
{
"name": "chromium-tip-of-tree",
"revision": "1115",
"installByDefault": false,
"browserVersion": "115.0.5773.0"
},
{
"name": "firefox",
"revision": "1408",
"installByDefault": true,
"browserVersion": "113.0"
},
{
"name": "firefox-beta",
"revision": "1410",
"installByDefault": false,
"browserVersion": "114.0b3"
},
{
"name": "webkit",
"revision": "1848",
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,
"revisionOverrides": {
"mac10.14": "1446",
"mac10.15": "1616",
"mac11": "1816",
"mac11-arm64": "1816",
"ubuntu18.04": "1728"
},
"browserVersion": "16.4"
},
{
"name": "ffmpeg",
"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
},
{
"name": "android",
"revision": "1000",
"installByDefault": false
}
]
}