Update dependency Microsoft.Playwright to 1.62.0

[thomhurst]

This PR contains the following updates:

Package	Change	Age	Confidence
Microsoft.Playwright	1.61.0 → 1.62.0

---

Release Notes

microsoft/playwright-dotnet (Microsoft.Playwright)

v1.62.0

🖼️ WebP screenshots

page.screenshot() and locator.screenshot() can now capture screenshots in the WebP format — Playwright infers the format from a .webp file extension, or you can set the type explicitly. Quality 100 (the default) is lossless, while lower values use lossy compression:

await Page.ScreenshotAsync(new() { Path = "homepage.webp", Quality = 50 });

New APIs

• New Scroll option (Auto | None) on actions to opt out of Playwright's automatic scroll-into-view.
• New Locator.WaitForFunctionAsync() waits until a function — called with the matching element — returns a truthy value.
• New APIResponse.TimingAsync() returns resource timing information for an API response.

Announcements

• 📋 The clipboard is now isolated from the operating system in headless mode, so tests that use navigator.clipboard no longer read or overwrite the clipboard of the machine running them.
• ⚠️ Debian 11 is not supported anymore.

Browser Versions

• Chromium 151.0.7922.34
• Mozilla Firefox 153.0
• WebKit 26.5

This version was also tested against the following stable channels:

• Google Chrome 151
• Microsoft Edge 151

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 CLI.

[coderabbitai]

Warning

Review limit reached

@thomhurst, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 5 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 110a8b1c-1aae-48cd-8ec4-8c69ea79be05

📥 Commits

Reviewing files that changed from the base of the PR and between cf36d10 and 091b023.

📒 Files selected for processing (1)

• Directory.Packages.props

---

_{Comment @coderabbitai help to get the list of available commands.}

[claude]

Code Review

This is an automated Renovate dependency bump: Microsoft.Playwright 1.61.0 → 1.62.0 in Directory.Packages.props. It's a single-line, single-file change with no application logic touched, no new code paths, and nothing that conflicts with CLAUDE.md build guidance (it's a manifest version bump, not a build-pipeline change).

No architectural, design, or correctness concerns here — LGTM. Only note is the usual due diligence for a Playwright bump: confirm CI's browser-install step still passes with the new version (Playwright sometimes requires a matching playwright install browser version bump), but that's CI's job to catch, not a reason to block this PR.