fix(ci): bump Playwright for Node 24 browser install#29946
Open
kbingol wants to merge 1 commit into
Open
Conversation
github-actions
Bot
added
needs:compliance
Contributor
|
Thanks for updating your PR! It now meets our contributing guidelines. 👍 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue for this PR
Closes #29944
Type of change
What does this PR do?
Bumps Playwright from 1.59.1 to 1.60.0.
This should avoid a cold-cache Windows CI hang where
bunx playwright install chromiumreaches 100% and then never exits before e2e tests start. Playwright 1.60.0 includes the upstream archive extraction fix from microsoft/playwright#40747, which is linked from the related install-hang reports.How did you verify your code works?
bun.lockwithbun install --ignore-scripts.@playwright/test,playwright, andplaywright-coreto 1.60.0.I could not fully run the Windows e2e job locally, so CI should verify the actual runner behavior.
Screenshots / recordings
Not a UI change.
Checklist