[Refaerds]

Summary

Prerelease versions for the two upstream upgrades now on main:

Package	From	To	Why
@cloudflare/playwright	1.3.7-next	1.4.0-next	#249: Playwright v1.62.1, Chrome 152. Minor, as recommended in the PR.
@cloudflare/puppeteer	1.5.0-rc.0	2.0.0-next	#248: Puppeteer v25.10.0, Chrome 152. Upstream removed Browser.isConnected(), MouseOptions.clickCount and the sameParty cookie attribute, so this is a major, as recommended in the PR.

@cloudflare/playwright-mcp is unchanged.

The Cloudflare API of @cloudflare/playwright does not change. Upstream Playwright v1.60 removed four already-deprecated APIs, which the release notes should list: Locator.ariaRef(), the handle option of exposeBinding(), the logger option of connect()/connectOverCDP(), and the videosPath/videoSize context options.

How

The "Prepare" steps from RELEASING.md:

npm version 1.4.0-next --workspace @cloudflare/playwright --no-git-tag-version
npm version 2.0.0-next --workspace @cloudflare/puppeteer --no-git-tag-version
npm install --package-lock-only --prefix packages/playwright-cloudflare/tests
npm install --package-lock-only --prefix packages/puppeteer-cloudflare/tests

A root npm install --package-lock-only afterwards is a no-op, so the root lockfile is consistent.

One incidental lockfile change: in packages/playwright-cloudflare/tests/package-lock.json npm normalised the stale "../..": { dev, optional, peer } link entry to "../..": {}. The documented command produced it; it is not a hand edit.

After merge

Once the full suites on main pass, publish per RELEASING.md with GitHub releases marked pre-release, tagged cloudflare-playwright-v1.4.0-next and cloudflare-puppeteer-v2.0.0-next. Both publish to the npm next dist-tag; latest stays at 1.3.6 / 1.4.0 until a stable bump.

[clanky-the-clanker]

✅ Approved — I found no issues: the package versions and all affected lockfiles agree.

_{The decision is advisory: this review is a comment and never approves, blocks or requests changes on the pull request.}

---

✅ All checks passed

📋 Code Quality: ✅ LGTM

The version fields and lockfile entries match each other for both packages.

---

📝 Documentation: ✅ LGTM

RELEASING.md uses example versions (1.5.0-rc.0, 1.0.0-rc.0) together with a VERSION variable to show the procedure. They are not meant to track the current release, so they don't need updating here.

---

_{Reviewed commit: f9607945}

[github-actions]

@cloudflare/playwright preview for commit f960794

npm i https://pkg.pr.new/cloudflare/browser-run/@cloudflare/playwright@f9607945bf054153a625b775536199be3d1d372c

Published by this workflow run. New pushes and reruns update this comment.

[github-actions]

@cloudflare/playwright-mcp preview for commit f960794

npm i https://pkg.pr.new/cloudflare/browser-run/@cloudflare/playwright-mcp@f9607945bf054153a625b775536199be3d1d372c

Published by this workflow run. New pushes and reruns update this comment.

[github-actions]

@cloudflare/puppeteer preview for commit f960794

npm i https://pkg.pr.new/cloudflare/browser-run/@cloudflare/puppeteer@f9607945bf054153a625b775536199be3d1d372c

Published by this workflow run. New pushes and reruns update this comment.