Repository navigation
chore: roll patchright-core to 1.64.2 - #17
github-actions[bot] wants to merge 1 commit into
Conversation
|
The roll is safe and CI is green, but the workflow could not merge (the |
ae50ffa to
48f747d
Compare
|
The roll is safe and CI is green, but the workflow could not merge (the |
48f747d to
d12d5a7
Compare
|
The roll is safe and CI is green, but the workflow could not merge (the |
d12d5a7 to
a737d2e
Compare
|
The roll is safe and CI is green, but the workflow could not merge (the |
a737d2e to
b46f317
Compare
|
The roll is safe and CI is green, but the workflow could not merge (the |
b46f317 to
041a786
Compare
|
CI result on this branch: failure. Not merged; see https://github.com/b1zya/patchright-cli/actions/runs/41455020026 for the failing job. |
… 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.
|
Superseded by #19 (patchright-core 1.64.3). |
Roll patchright-core 1.64.1 -> 1.64.2
Verdict: safe (applied)
Published 2026-10-25T12:41:21.812Z (193 h ago).
Playwright sources: v1.64.1 (compiled client byte-identical; tried 1.64.1)
Forked files (three-way merge: src <- vendor -> upstream)
Compiled files that changed
Command surface and daemon
CI on this branch: failure (run)