chore(deps): upgrade Playwright to 1.60.0 to fix hanging CI#2787
Conversation
Closes #2783 See microsoft/playwright#39692, microsoft/playwright#40724, and microsoft/playwright#40747. Co-Authored-By: @mootari
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
📝 WalkthroughWalkthroughPlaywright development dependency upgraded from v1.58.2 to v1.60.0 across devDependencies and CI browser job container image. ViewTransition plugin updated with explicit rejection handlers for multiple promise phases and helper functions to distinguish expected abort-style rejections from unexpected transition failures. ChangesPlaywright 1.60.0 upgrade with ViewTransition error handling
Suggested reviewers
🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
All alerts resolved. Learn more about Socket for GitHub. This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. Ignoring alerts on:
|
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
📊 Dependency Size ChangesWarning This PR adds 4.4 MB of new dependencies, which exceeds the threshold of 200 kB.
Total size change: 4.4 MB |
Playwright 1.58.2 used Chromium 145.0.7632.6. Playwright 1.60.0 uses Chromium 148.0.7778.96. For some reason, this latent issue with not handling these promise rejections is now causing test failures. We should have been handling these anyway.
|
@SocketSecurity ignore npm/node-fetch-native@1.6.7 seems to just be because that package commits its built code (alongside source) for some reason |
🔗 Linked issue
Closes #2783
🧭 Context
See microsoft/playwright#39692, microsoft/playwright#40724, and microsoft/playwright#40747.
📚 Description
Update Playwright and its Action to 1.60.0
... which then caused component tests to start failing with:
Playwright 1.58.2 used Chromium 145.0.7632.6. Playwright 1.60.0 uses Chromium 148.0.7778.96. For some reason or another, the latent issue with not handling View Transition rejections started surfacing after this update. We should have been handling these anyway.
Co-Authored-By: @mootari