build(deps): bump playwright from 1.41.1 to 1.45.1

[dependabot]

Bumps playwright from 1.41.1 to 1.45.1.

Release notes

Sourced from playwright's releases.

v1.45.1

Highlights

microsoft/playwright#31473 - [REGRESSION]: Playwright raises an error ENOENT: no such file or directory, open 'test-results/.playwright-artifacts-0/hash.zip' with Electron microsoft/playwright#31442 - [REGRESSION]: Locators of elements changing from/to hidden have operations hanging when using --disable-web-security microsoft/playwright#31431 - [REGRESSION]: NewTab doesn't work properly with Chrome with --disable-web-security microsoft/playwright#31425 - [REGRESSION]: beforeEach hooks are not skipped when describe condition depends on fixtures microsoft/playwright#31491 - [REGRESSION]: @playwright/experimental-ct-react doesn't work with VSCode extension and PNPM

Browser Versions

• Chromium 127.0.6533.5
• Mozilla Firefox 127.0
• WebKit 17.4

This version was also tested against the following stable channels:

• Google Chrome 126
• Microsoft Edge 126

v1.45.0

Clock

Utilizing the new Clock API allows to manipulate and control time within tests to verify time-related behavior. This API covers many common scenarios, including:

• testing with predefined time;
• keeping consistent time and timers;
• monitoring inactivity;
• ticking through time manually.

// Initialize clock and let the page load naturally.
await page.clock.install({ time: new Date('2024-02-02T08:00:00') });
await page.goto('http://localhost:3333');
// Pretend that the user closed the laptop lid and opened it again at 10am,
// Pause the time once reached that point.
await page.clock.pauseAt(new Date('2024-02-02T10:00:00'));
// Assert the page state.
await expect(page.getByTestId('current-time')).toHaveText('2/2/2024, 10:00:00 AM');
// Close the laptop lid again and open it at 10:30am.
await page.clock.fastForward('30:00');
await expect(page.getByTestId('current-time')).toHaveText('2/2/2024, 10:30:00 AM');

See the clock guide for more details.

Test runner

• New CLI option --fail-on-flaky-tests that sets exit code to 1 upon any flaky tests. Note that by default, the test runner exits with code 0 when all failed tests recovered upon a retry. With this option, the test run will fail in such case.

... (truncated)

Commits

• e8989f8 chore: mark v1.45.1 (#31516)
• 1d94caa cherry-pick(#31496): docs(release-notes): fix .NET snippets
• 5be5168 cherry-pick(#31504): fix(ct): export package.json
• 0fe7a10 cherry-pick(#31437): fix(electron): tracing with @​playwright/test
• 4ec4ccf cherry-pick(#31401): chore: .NET generator fixes
• 3b4d32e cherry-pick(#31458): fix(utility): create utility world when web security is ...
• 4ccaef6 cherry-pick(#31426): fix(runner): do not run beforeEach hooks upon skip modifier
• 4f3f6ee cherry-pick(#31421): docs: release notes for 1.45
• d557b7b cherry-pick(#31420): docs(java): correctly parse time (#31422)
• 1368bca cherry-pick(#31419): docs: deprecate handle option in exposeBinding
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	environment, eval, filesystem, network, shell, unsafe	0	7.23 MB	yurys
npm/[email protected]	None	0	3.05 MB	yurys

🚮 Removed packages: npm/[email protected], npm/[email protected]

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Environment variable access	npm/[email protected]	Env Vars: PW_FREEZE_TIME Location: Package overview	package.json	🚫
Debug access	npm/[email protected]	Module: async_hooks Location: Package overview	package.json	🚫
Minified code	npm/[email protected]	Confidence: 1.00 Location: Package overview	package.json	🚫

View full report↗︎

Next steps

What is environment variable access?

Package accesses environment variables, which may be a sign of credential stuffing or data theft.

Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to.

What is debug access?

Uses debug, reflection and dynamic code execution features.

Removing the use of debug will reduce the risk of any reflection and dynamic code execution.

What's wrong with minified code?

This package contains minified code. This may be harmless in some cases where minified code is included in packaged libraries, however packages on npm should not minify code.

In many cases minified code is harmless, however minified code can be used to hide a supply chain attack. Consider not shipping minified code on npm.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]