Skip to content

chore: roll patchright-core to 1.64.3 - #19

Merged
b1zya merged 1 commit into
mainfrom
roll_1.64.3
Nov 8, 2026
Merged

b1zya merged 1 commit into
mainfrom
roll_1.64.3

Conversation

@github-actions

@github-actions github-actions Bot commented Nov 5, 2026 •

Copy link
Copy Markdown

Roll patchright-core 1.64.1 -> 1.64.3

Verdict: safe (applied)

  • nothing our client is forked from changed; only the daemon and the patches moved

Published 2026-11-02T21:42:00.325Z (132 h ago).

Playwright sources: v1.64.1 (compiled client byte-identical; tried 1.64.1)

Forked files (three-way merge: src <- vendor -> upstream)

file result
src/program.ts unchanged
src/session.ts unchanged
src/registry.ts unchanged
src/output.ts unchanged
src/channelSessions.ts unchanged
src/cli.ts unchanged
src/args.ts unchanged
src/socketConnection.ts unchanged

Compiled files that changed

  • none

Command surface and daemon

  • unchanged

CI on this branch: success (run)

@github-actions

github-actions Bot commented Nov 5, 2026

Copy link
Copy Markdown
Author

CI result on this branch: failure. Not merged; see https://github.com/b1zya/patchright-cli/actions/runs/42034887367 for the failing job.

@github-actions

github-actions Bot commented Nov 6, 2026

Copy link
Copy Markdown
Author

CI result on this branch: failure. Not merged; see https://github.com/b1zya/patchright-cli/actions/runs/42222491837 for the failing job.

@github-actions

github-actions Bot commented Nov 7, 2026

Copy link
Copy Markdown
Author

The roll is safe and CI is green, but the workflow could not merge (the main ruleset or repository settings). Merge by hand.

b1zya added a commit that referenced this pull request Nov 8, 2026
… roll PRs (#20)

* devops(ci): warm up Chrome before the integration tests

A fresh runner reads the preinstalled Chrome from a cold disk; its first
launch took up to a minute and timed out whichever config tests ran
first, and starved the 10 s chrome --version probe. Seen on the roll
branches (runs 41455020026, 42034887367).

* devops(ci): close superseded roll PRs and say why a safe roll waits

A newer roll left the older roll_* PR open for good (#17 next to #19).
The merge-failure comment now names the real blocker: the pull_request
CI run held for approval on a push by the workflow token.
@github-actions

github-actions Bot commented Nov 8, 2026

Copy link
Copy Markdown
Author

The roll is safe and CI is green, but the workflow could not merge: the main ruleset counts only the pull request's own CI run, which GitHub holds for approval on a push by the workflow token. Approve that run (Actions, the CI run marked action required on this branch), wait for it to pass, then merge.

@b1zya
b1zya merged commit 73c1965 into main Nov 8, 2026
10 checks passed
@b1zya
b1zya deleted the roll_1.64.3 branch November 8, 2026 09:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant