Update dependency playwright-chromium to v1.38.1 #189

renovate · 2023-09-30T04:35:09Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
playwright-chromium (source)	`1.28.1` -> `1.38.1`

Release Notes

Microsoft/playwright (playwright-chromium)

`v1.38.1`

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/27071 - expect(value).toMatchSnapshot() deprecation announcement on V1.38
https://github.com/microsoft/playwright/issues/27072 - [BUG] PWT trace viewer fails to load trace and throws TypeErrorhttps://github.com/microsoft/playwright/issues/270733 - [BUG] RangeError: Invalid time valuhttps://github.com/microsoft/playwright/issues/2708787 - [REGRESSION]: npx playwright test --list prints all tests twihttps://github.com/microsoft/playwright/issues/27113113 - [REGRESSION]: No longer able to extend PlaywrightTest.Matchers type for locators and pahttps://github.com/microsoft/playwright/issues/271447144 - [BUG]can not display thttps://github.com/microsoft/playwright/issues/2716327163 - [REGRESSION] Single Quote Wrongly Escaped by Locator When Using Unicodehttps://github.com/microsoft/playwright/issues/27181/27181 - [BUG] evaluate serializing fails at 1.38

Browser Versions

Chromium 117.0.5938.62
Mozilla Firefox 117.0
WebKit 17.0

This version was also tested against the following stable channels:

Google Chrome 116
Microsoft Edge 116

`v1.38.0`

Compare Source

UI Mode Updates

Zoom into time range.
Network panel redesign.

New APIs

[browserContext.on('weberror')][browserContext.on('weberror')]
[locator.pressSequentially()][locator.pressSequentially()]
The [reporter.onEnd()][reporter.onEnd()] now reports startTime and total run duration.

Deprecations

The following methods were deprecated: [page.type()][page.type()], [frame.type()][frame.type()], [locator.type()][locator.type()] and [elementHandle.type()][elementHandle.type()].
Please use [locator.fill()][locator.fill()] instead which is much faster. Use [locator.pressSequentially()][locator.pressSequentially()] only if there is a
special keyboard handling on the page, and you need to press keys one-by-one.

Breaking Changes: Playwright no longer downloads browsers automatically

[!NOTE]
If you are using @playwright/test package, this change does not affect you.

Playwright recommends to use @playwright/test package and download browsers via npx playwright install command. If you are following this recommendation, nothing has changed for you.

However, up to v1.38, installing the playwright package instead of @playwright/test did automatically download browsers. This is no longer the case, and we recommend to explicitly download browsers via npx playwright install command.

v1.37 and earlier

playwright package was downloading browsers during npm install, while @playwright/test was not.

v1.38 and later

playwright and @playwright/test packages do not download browsers during npm install.

Recommended migration

Run npx playwright install to download browsers after npm install. For example, in your CI configuration:

- run: npm ci
- run: npx playwright install --with-deps

Alternative migration option - not recommended

Add @playwright/browser-chromium, @playwright/browser-firefox and @playwright/browser-webkit as a dependency. These packages download respective browsers during npm install. Make sure you keep the version of all playwright packages in sync:

// package.json
{
  "devDependencies": {
    "playwright": "1.38.0",
    "@&#8203;playwright/browser-chromium": "1.38.0",
    "@&#8203;playwright/browser-firefox": "1.38.0",
    "@&#8203;playwright/browser-webkit": "1.38.0"
  }
}

Browser Versions

Chromium 117.0.5938.62
Mozilla Firefox 117.0
WebKit 17.0

This version was also tested against the following stable channels:

Google Chrome 116
Microsoft Edge 116

`v1.37.1`

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/26496 - [REGRESSION] webServer stdout is always getting printedhttps://github.com/microsoft/playwright/issues/264922 - [REGRESSION] test.only with project dependency is not working

Browser Versions

Chromium 116.0.5845.82
Mozilla Firefox 115.0
WebKit 17.0

This version was also tested against the following stable channels:

Google Chrome 115
Microsoft Edge 115

`v1.37.0`

Compare Source

Watch the overview: Playwright 1.36 & 1.37

✨ New tool to merge reports

If you run tests on multiple shards, you can now merge all reports in a single HTML report (or any other report)
using the new merge-reports CLI tool.

Using merge-reports tool requires the following steps:

Adding a new "blob" reporter to the config when running on CI:
```
export default defineConfig({
  testDir: './tests',
  reporter: process.env.CI ? 'blob' : 'html',
});
```
The "blob" reporter will produce ".zip" files that contain all the information
about the test run.
Copying all "blob" reports in a single shared location and running npx playwright merge-reports:
```
npx playwright merge-reports --reporter html ./all-blob-reports
```

📚 Debian 12 Bookworm Support

Playwright now supports Debian 12 Bookworm on both x86_64 and arm64 for Chromium, Firefox and WebKit.
Let us know if you encounter any issues!

Linux support looks like this:

	Ubuntu 20.04	Ubuntu 22.04	Debian 11	Debian 12
Chromium	✅	✅	✅	✅
WebKit	✅	✅	✅	✅
Firefox	✅	✅	✅	✅

🌈 UI Mode Updates

UI Mode now respects project dependencies. You can control which dependencies to respect by checking/unchecking them in a projects list.
Console logs from the test are now displayed in the Console tab.

Browser Versions

Chromium 116.0.5845.82
Mozilla Firefox 115.0
WebKit 17.0

This version was also tested against the following stable channels:

Google Chrome 115
Microsoft Edge 115

`v1.36.2`: 1.36.2

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/24316 - [REGRESSION] Character classes are not working in globs in 1.36

Browser Versions

Chromium 115.0.5790.75
Mozilla Firefox 115.0
WebKit 17.0

This version was also tested against the following stable channels:

Google Chrome 114
Microsoft Edge 114

`v1.36.1`

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/24184 - [REGRESSION]: Snapshot name contains some random string after test name when tests are run in container

Browser Versions

Chromium 115.0.5790.75
Mozilla Firefox 115.0
WebKit 17.0

This version was also tested against the following stable channels:

Google Chrome 114
Microsoft Edge 114

`v1.36.0`

Compare Source

Watch the overview: Playwright 1.36 & 1.37

Highlights

🏝️ Summer maintenance release.

Browser Versions

Chromium 115.0.5790.75
Mozilla Firefox 115.0
WebKit 17.0

This version was also tested against the following stable channels:

Google Chrome 114
Microsoft Edge 114

`v1.35.1`

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/23622 - [Docs] Provide a description how to correctly use expect.configure with poll parameterhttps://github.com/microsoft/playwright/issues/236666 - [BUG] Live Trace does not work with Codespacehttps://github.com/microsoft/playwright/issues/2369393 - [BUG] attachment steps are not hidden inside expect.toHaveScreenshot()

Browser Versions

Chromium 115.0.5790.13
Mozilla Firefox 113.0
WebKit 16.4

This version was also tested against the following stable channels:

Google Chrome 114
Microsoft Edge 114

`v1.35.0`

Compare Source

Playwright v1.35 updates

Highlights

UI mode is now available in VSCode Playwright extension via a new "Show trace viewer" button:
UI mode and trace viewer mark network requests handled with page.route() and browserContext.route() handlers, as well as those issued via the API testing:
New option maskColor for methods page.screenshot(), locator.screenshot(), expect(page).toHaveScreenshot() and expect(locator).toHaveScreenshot() to change default masking color:
```
await page.goto('https://playwright.dev');
await expect(page).toHaveScreenshot({
  mask: [page.locator('img')],
  maskColor: '#&#8203;00FF00', // green
});
```

New uninstall CLI command to uninstall browser binaries:

$ npx playwright uninstall # remove browsers installed by this installation
$ npx playwright uninstall --all # remove all ever-install Playwright browsers

Both UI mode and trace viewer now could be opened in a browser tab:

$ npx playwright test --ui-port 0 # open UI mode in a tab on a random port
$ npx playwright show-trace --port 0 # open trace viewer in tab on a random port

⚠️ Breaking changes

playwright-core binary got renamed from playwright to playwright-core. So if you use playwright-core CLI, make sure to update the name:
```
$ npx playwright-core install # the new way to install browsers when using playwright-core
```
This change does not affect @playwright/test and playwright package users.

Browser Versions

Chromium 115.0.5790.13
Mozilla Firefox 113.0
WebKit 16.4

This version was also tested against the following stable channels:

Google Chrome 114
Microsoft Edge 114

`v1.34.3`

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/23228 - [BUG] Getting "Please install @playwright/test package..." after upgrading from 1.34.0 to 1.34.1

Browser Versions

Chromium 114.0.5735.26
Mozilla Firefox 113.0
WebKit 16.4

This version was also tested against the following stable channels:

Google Chrome 113
Microsoft Edge 113

`v1.34.2`

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/23225 - [BUG] VSCode Extension broken with Playwright 1.34.1

Browser Versions

Chromium 114.0.5735.26
Mozilla Firefox 113.0
WebKit 16.4

This version was also tested against the following stable channels:

Google Chrome 113
Microsoft Edge 113

`v1.34.1`

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/23186 - [BUG] Container image for v1.34.0 missing library for webkithttps://github.com/microsoft/playwright/issues/232066 - [BUG] Unable to install supported browsers for v1.34.0 from playwright-corhttps://github.com/microsoft/playwright/issues/2320707 - [BUG] importing ES Module JSX component is broken since 1.34

Browser Versions

Chromium 114.0.5735.26
Mozilla Firefox 113.0
WebKit 16.4

This version was also tested against the following stable channels:

Google Chrome 113
Microsoft Edge 113

`v1.34.0`

Compare Source

Playwright v1.33 & v1.34 updates

Highlights

UI Mode now shows steps, fixtures and attachments:

New property testProject.teardown to specify a project that needs to run after this
and all dependent projects have finished. Teardown is useful to cleanup any resources acquired by this project.

A common pattern would be a setup dependency with a corresponding teardown:

// playwright.config.ts
import { defineConfig } from '@&#8203;playwright/test';

export default defineConfig({
  projects: [
    {
      name: 'setup',
      testMatch: /global.setup\.ts/,
      teardown: 'teardown',
    },
    {
      name: 'teardown',
      testMatch: /global.teardown\.ts/,
    },
    {
      name: 'chromium',
      use: devices['Desktop Chrome'],
      dependencies: ['setup'],
    },
    {
      name: 'firefox',
      use: devices['Desktop Firefox'],
      dependencies: ['setup'],
    },
    {
      name: 'webkit',
      use: devices['Desktop Safari'],
      dependencies: ['setup'],
    },
  ],
});

New method expect.configure to create pre-configured expect instance with its own defaults such as timeout and soft.

const slowExpect = expect.configure({ timeout: 10000 });
await slowExpect(locator).toHaveText('Submit');

// Always do soft assertions.
const softExpect = expect.configure({ soft: true });

New options stderr and stdout in testConfig.webServer to configure output handling:

// playwright.config.ts
import { defineConfig } from '@&#8203;playwright/test';

export default defineConfig({
  // Run your local dev server before starting the tests
  webServer: {
    command: 'npm run start',
    url: 'http://127.0.0.1:3000',
    reuseExistingServer: !process.env.CI,
    stdout: 'pipe',
    stderr: 'pipe',
  },
});

New locator.and() to create a locator that matches both locators.

const button = page.getByRole('button').and(page.getByTitle('Subscribe'));

New events browserContext.on('console') and browserContext.on('dialog') to subscribe to any dialogs
and console messages from any page from the given browser context. Use the new methods consoleMessage.page()
and dialog.page() to pin-point event source.

⚠️ Breaking changes

npx playwright test no longer works if you install both playwright and @playwright/test. There's no need
to install both, since you can always import browser automation APIs from @playwright/test directly:
```
// automation.ts
import { chromium, firefox, webkit } from '@&#8203;playwright/test';
/* ... */
```
Node.js 14 is no longer supported since it reached its end-of-life on April 30, 2023.

Browser Versions

Chromium 114.0.5735.26
Mozilla Firefox 113.0
WebKit 16.4

This version was also tested against the following stable channels:

Google Chrome 113
Microsoft Edge 113

`v1.33.0`

Compare Source

Playwright v1.33 & v1.34 updates

Locators Update

Use [locator.or()][locator.or()] to create a locator that matches either of the two locators.
Consider a scenario where you'd like to click on a "New email" button, but sometimes a security settings dialog shows up instead.
In this case, you can wait for either a "New email" button, or a dialog and act accordingly:
```
const newEmail = page.getByRole('button', { name: 'New' });
const dialog = page.getByText('Confirm security settings');
await expect(newEmail.or(dialog)).toBeVisible();
if (await dialog.isVisible())
  await page.getByRole('button', { name: 'Dismiss' }).click();
await newEmail.click();
```

Use new options hasNot and hasNotText in [locator.filter()][locator.filter()]
to find elements that do not match certain conditions.

const rowLocator = page.locator('tr');
await rowLocator
    .filter({ hasNotText: 'text in column 1' })
    .filter({ hasNot: page.getByRole('button', { name: 'column 2 button' }) })
    .screenshot();

Use new web-first assertion [locatorAssertions.toBeAttached()][locatorAssertions.toBeAttached()] to ensure that the element
is present in the page's DOM. Do not confuse with the [locatorAssertions.toBeVisible()][locatorAssertions.toBeVisible()] that ensures that
element is both attached & visible.

New APIs

[locator.or()][locator.or()]
New option hasNot in [locator.filter()][locator.filter()]
New option hasNotText in [locator.filter()][locator.filter()]
[locatorAssertions.toBeAttached()][locatorAssertions.toBeAttached()]
New option timeout in [route.fetch()][route.fetch()]
[reporter.onExit()][reporter.onExit()]

⚠️ Breaking change

The mcr.microsoft.com/playwright:v1.33.0 now serves a Playwright image based on Ubuntu Jammy.
To use the focal-based image, please use mcr.microsoft.com/playwright:v1.33.0-focal instead.

Browser Versions

Chromium 113.0.5672.53
Mozilla Firefox 112.0
WebKit 16.4

This version was also tested against the following stable channels:

Google Chrome 112
Microsoft Edge 112

`v1.32.3`

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/22144 - [BUG] WebServer only starting after timeouthttps://github.com/microsoft/playwright/pull/221911 - chore: allow reusing browser between the testshttps://github.com/microsoft/playwright/issues/222155 - [BUG] Tests failing in toPass often marked as passed

Browser Versions

Chromium 112.0.5615.29
Mozilla Firefox 111.0
WebKit 16.4

This version was also tested against the following stable channels:

Google Chrome 111
Microsoft Edge 111

`v1.32.2`

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/21993 - [BUG] Browser crash when using Playwright VSC extension and trace-viewer enabled in confighttps://github.com/microsoft/playwright/issues/220033 - [Feature] Make Vue component mount props less restrictivhttps://github.com/microsoft/playwright/issues/2208989 - [REGRESSION]: Tests failing with "Error: tracing.stopChunk"

Browser Versions

Chromium 112.0.5615.29
Mozilla Firefox 111.0
WebKit 16.4

This version was also tested against the following stable channels:

Google Chrome 111
Microsoft Edge 111

`v1.32.1`

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/21832 - [BUG] Trace is not opening on specific broken locatorhttps://github.com/microsoft/playwright/issues/218977 - [BUG] --ui fails to open with error reading mainFrame from an undefined this._pahttps://github.com/microsoft/playwright/issues/21918918 - [BUG]: UI mode, skipped tests not being fohttps://github.com/microsoft/playwright/issues/219411941 - [BUG] UI mode does not show webServer startup erhttps://github.com/microsoft/playwright/issues/2195321953 - [BUG] Parameterized tests are not displayed in the UI mode

Browser Versions

Chromium 112.0.5615.29
Mozilla Firefox 111.0
WebKit 16.4

This version was also tested against the following stable channels:

Google Chrome 111
Microsoft Edge 111

`v1.32.0`

Compare Source

📣 Introducing UI Mode (preview)

Playwright v1.32 updates

New UI Mode lets you explore, run and debug tests. Comes with a built-in watch mode.

Engage with a new flag --ui:

npx playwright test --ui

New APIs

New options option: updateMode and option: updateContent in page.routeFromHAR() and browserContext.routeFromHAR().
Chaining existing locator objects, see locator docs for details.
New property TestInfo.testId.
New option name in method Tracing.startChunk().

⚠️ Breaking change in component tests

Note: component tests only, does not affect end-to-end tests.

@playwright/experimental-ct-react now supports React 18 only.
If you're running component tests with React 16 or 17, please replace
@playwright/experimental-ct-react with @playwright/experimental-ct-react17.

Browser Versions

Chromium 112.0.5615.29
Mozilla Firefox 111.0
WebKit 16.4

This version was also tested against the following stable channels:

Google Chrome 111
Microsoft Edge 111

`v1.31.2`

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/20784 - [BUG] ECONNREFUSED on GitHub Actions with Node 18https://github.com/microsoft/playwright/issues/211455 - [REGRESSION]: firefox-1378 times out on await page.reload() when URL contains a #hashttps://github.com/microsoft/playwright/issues/2122626 - [BUG] Playwright seems to get stuck when using shard option and last test is skipphttps://github.com/microsoft/playwright/issues/21227227 - Using the webServer config with a Vite dev servehttps://github.com/microsoft/playwright/issues/21312312 - throw if defineConfig is not used for component testing

Browser Versions

Chromium 111.0.5563.19
Mozilla Firefox 109.0
WebKit 16.4

This version was also tested against the following stable channels:

Google Chrome 110
Microsoft Edge 110

`v1.31.1`

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/21093 - [Regression v1.31] Headless Windows shows cascading cmd windowshttps://github.com/microsoft/playwright/pull/211066 - fix(loader): experimentalLoader with node@18

Browser Versions

Chromium 111.0.5563.19
Mozilla Firefox 109.0
WebKit 16.4

This version was also tested against the following stable channels:

Google Chrome 110
Microsoft Edge 110

`v1.31.0`

Compare Source

New APIs

New property TestProject.dependencies to configure dependencies between projects.

Using dependencies allows global setup to produce traces and other artifacts,
see the setup steps in the test report and more.

// playwright.config.ts
import { defineConfig } from '@&#8203;playwright/test';

export default defineConfig({
  projects: [
    {
      name: 'setup',
      testMatch: /global.setup\.ts/,
    },
    {
      name: 'chromium',
      use: devices['Desktop Chrome'],
      dependencies: ['setup'],
    },
    {
      name: 'firefox',
      use: devices['Desktop Firefox'],
      dependencies: ['setup'],
    },
    {
      name: 'webkit',
      use: devices['Desktop Safari'],
      dependencies: ['setup'],
    },
  ],
});

New assertion expect(locator).toBeInViewport() ensures that locator points to an element that intersects viewport, according to the intersection observer API.

const button = page.getByRole('button');

// Make sure at least some part of element intersects viewport.
await expect(button).toBeInViewport();

// Make sure element is fully outside of viewport.
await expect(button).not.toBeInViewport();

// Make sure that at least half of the element intersects viewport.
await expect(button).toBeInViewport({ ratio: 0.5 });

Miscellaneous

DOM snapshots in trace viewer can be now opened in a separate window.
New method defineConfig to be used in playwright.config.
New option maxRedirects for method Route.fetch.
Playwright now supports Debian 11 arm64.
Official docker images now include Node 18 instead of Node 16.

⚠️ Breaking change in component tests

Note: component tests only, does not affect end-to-end tests.

playwright-ct.config configuration file for component testing now requires calling defineConfig.

// Before

import { type PlaywrightTestConfig, devices } from '@&#8203;playwright/experimental-ct-react';
const config: PlaywrightTestConfig = {
  // ... config goes here ...
};
export default config;

Replace config variable definition with defineConfig call:

// After

import { defineConfig, devices } from '@&#8203;playwright/experimental-ct-react';
export default defineConfig({
  // ... config goes here ...
});

Browser Versions

Chromium 111.0.5563.19
Mozilla Firefox 109.0
WebKit 16.4

This version was also tested against the following stable channels:

Google Chrome 110
Microsoft Edge 110

`v1.30.0`

Compare Source

🎉 Happy New Year 🎉

Maintenance release with bugfixes and new browsers only. We are baking some nice features for v1.31.

Browser Versions

Chromium 110.0.5481.38
Mozilla Firefox 108.0.2
WebKit 16.4

This version was also tested against the following stable channels:

Google Chrome 109
Microsoft Edge 109

`v1.29.2`

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/19661 - [BUG] 1.29.1 browserserver + page.goto = net::ERR_SOCKS_CONNECTION_FAILED

Browser Versions

Chromium 109.0.5414.46
Mozilla Firefox 107.0
WebKit 16.4

This version was also tested against the following stable channels:

Google Chrome 108
Microsoft Edge 108

`v1.29.1`

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/18928 - [BUG] Electron firstWindow times out after upgrading to 1.28.0https://github.com/microsoft/playwright/issues/192466 - [BUG] Electron firstWindow times out after upgrading to 1.28.https://github.com/microsoft/playwright/issues/1941212 - [REGRESSION]: 1.28 does not work with electron-serve anymorhttps://github.com/microsoft/playwright/issues/19540540 - [BUG] electron.app.getAppPath() returns the path one level higher if you run electron pointing to the directhttps://github.com/microsoft/playwright/issues/195489548 - [REGRESSION]: Ubuntu 18 LTS not supported anymore

Browser Versions

Chromium 109.0.5414.46
Mozilla Firefox 107.0
WebKit 16.4

This version was also tested against the following stable channels:

Google Chrome 108
Microsoft Edge 108

`v1.29.0`

Compare Source

New APIs

New method route.fetch() and new option json for route.fulfill():

await page.route('**/api/settings', async route => {
  // Fetch original settings.
  const response = await route.fetch();

  // Force settings theme to a predefined value.
  const json = await response.json();
  json.theme = 'Solorized';

  // Fulfill with modified data.
  await route.fulfill({ json });
});

New method locator.all() to iterate over all matching elements:

// Check all checkboxes!
const checkboxes = page.getByRole('checkbox');
for (const checkbox of await checkboxes.all())
  await checkbox.check();

Locator.selectOption matches now by value or label:

<select multiple>
  <option value="red">Red</div>
  <option value="green">Green</div>
  <option value="blue">Blue</div>
</select>

await element.selectOption('Red');

Retry blocks of code until all assertions pass:

await expect(async () => {
  const response = await page.request.get('https://api.example.com');
  await expect(response).toBeOK();
}).toPass();

Miscellaneous

Playwright Test now respects jsconfig.json.
New options args and proxy for androidDevice.launchBrowser().
Option postData in method route.continue() now supports serializable values.
Ubuntu 18.04 is not supported anymore

Browser Versions

Chromium 109.0.5414.46
Mozilla Firefox 107.0
WebKit 16.4

This version was also tested against the following stable channels:

Google Chrome 108
Microsoft Edge 108

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

stackblitz · 2023-09-30T04:35:12Z

Run & review this pull request in StackBlitz Codeflow.

changeset-bot · 2023-09-30T04:35:13Z

⚠️ No Changeset found

Latest commit: 260dab8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Update dependency playwright-chromium to v1.38.1

260dab8

kodiakhq bot merged commit 395888e into 01-30-Add_test_for_issue_45393 Sep 30, 2023
1 check passed

kodiakhq bot deleted the renovate/playwright-monorepo branch September 30, 2023 04:35

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update dependency playwright-chromium to v1.38.1 #189

Update dependency playwright-chromium to v1.38.1 #189

renovate bot commented Sep 30, 2023

stackblitz bot commented Sep 30, 2023

changeset-bot bot commented Sep 30, 2023

Update dependency playwright-chromium to v1.38.1 #189

Update dependency playwright-chromium to v1.38.1 #189

Conversation

renovate bot commented Sep 30, 2023

Release Notes

Highlights

Browser Versions

UI Mode Updates

New APIs

Deprecations

Breaking Changes: Playwright no longer downloads browsers automatically

Browser Versions

Highlights

Browser Versions

✨ New tool to merge reports

📚 Debian 12 Bookworm Support

🌈 UI Mode Updates

Browser Versions

v1.36.2: 1.36.2

Highlights

Browser Versions

Highlights

Browser Versions

Highlights

Browser Versions

Highlights

Browser Versions

Highlights

⚠️ Breaking changes

Browser Versions

Highlights

Browser Versions

Highlights

Browser Versions

Highlights

Browser Versions

Highlights

⚠️ Breaking changes

Browser Versions

Locators Update

New APIs

⚠️ Breaking change

Browser Versions

Highlights

Browser Versions

Highlights

Browser Versions

Highlights

Browser Versions

📣 Introducing UI Mode (preview)

New APIs

⚠️ Breaking change in component tests

Browser Versions

Highlights

Browser Versions

Highlights

Browser Versions

New APIs

Miscellaneous

⚠️ Breaking change in component tests

Browser Versions

🎉 Happy New Year 🎉

Browser Versions

Highlights

Browser Versions

Highlights

Browser Versions

New APIs

Miscellaneous

Browser Versions

Configuration

stackblitz bot commented Sep 30, 2023

changeset-bot bot commented Sep 30, 2023

⚠️ No Changeset found

`v1.36.2`: 1.36.2