An in-range update of puppeteer-core is breaking the build 🚨 #7
Comments
|
After pinning to 1.18.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Your tests are still failing with this version. Compare changes Release Notes for v1.20.0Big changes
API changesAddedBug fixese0c8d46 - fix: abort Raw notesa5f03ce - chore: mark version v1.20.0 (#4928) CommitsThe new version differs by 54 commits.
There are 54 commits in total. See the full diff |
The dependency puppeteer-core was updated from
1.18.1to1.19.0.🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
puppeteer-core is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
Status Details
Release Notes for v1.19.0
Big Changes
API changes
Added
class: FileChooser(ea28ccc)page.waitForFileChooser()(ea28ccc)Bug Fixes
#2946 - Handling File Input Dialogs
#4300 -
backgroundpage.on('console')not working#4374 - puppeteer.launch({ pipe: true }) may crash due to unhandled stream errors
Raw notes
b6172e8 - chore: mark version v1.19.0
ea28ccc - feat(page): introduce file chooser interception (#4653)
2abaac1 - fix(launcher): make dumpio and pipe options work together (#4727)
3982a60 - chore(testrunner): bump TestRunner version to v0.7.0 (#4719)
852c46c - feat(testrunner): async suite descriptions (#4721)
835e884 - feat(testrunner): add new testrunner options (#4718)
934d73e - fix(testreporter): Test Reporter should not terminate node.js process (#4716)
eea55bd - fix(testrunner): properly handle testrunner terminations (#4717)
ad18021 - fix(launcher): disable component extensions (#4704)
f8616ed - fix(pipe): handle 'error' events on pipes to avoid crashing (#4705)
c9977c8 - fix(page): properly create isolated worlds (#4707)
a39d553 - fix(tests): Get TLS version from Node instead of hardcoding it (#4700)
bafda9f - fix(launcher): ensure PUPPETEER_EXECUTABLE_PATH is used if set (#4677)
a582c11 - chore(ci): add Node10 and Node12 to Cirrus (#4699)
715aad2 - fix: proper parse Error message on Node 12 (#4698)
49b2795 - feat(keyboard): feature phone buttons (#4694)
a17c727 - chore: release next testrunner (#4697)
8e0c2fa - feat(chromium): roll Chromium to r674921 (#4678)
9ef4153 - feat(chromium): roll Chromium to r673587 (#4646)
492132f - docs(api.md): Slightly enhanced wording (#4631)
a069a12 - docs(puppeteer-chromium): docker alpine freetype-dev dependency (#4643)
2d99d85 - fix(firefox): error message typo (#4623)
4ccd52c - chore: bump version to v1.18.1-post (#4630)
Commits
The new version differs by 23 commits.
af0d229chore: mark version v1.19.0 (#4744)ea28cccfeat(page): introduce file chooser interception (#4653)2abaac1fix(launcher): make dumpio and pipe options work together (#4727)3982a60chore(testrunner): bump TestRunner version to v0.7.0 (#4719)852c46cfeat(testrunner): async suite descriptions (#4721)835e884feat(testrunner): add new testrunner options (#4718)934d73efix(testreporter): Test Reporter should not terminate node.js process (#4716)eea55bdfix(testrunner): properly handle testrunner terminations (#4717)ad18021fix(launcher): disable component extensions (#4704)f8616edfix(pipe): handle 'error' events on pipes to avoid crashing (#4705)c9977c8fix(page): properly create isolated worlds (#4707)a39d553fix(tests): Get TLS version from Node instead of hardcoding it (#4700)bafda9ffix(launcher): ensure PUPPETEER_EXECUTABLE_PATH is used if set (#4677)a582c11chore(ci): add Node10 and Node12 to Cirrus (#4699)715aad2fix: proper parse Error message on Node 12 (#4698)There are 23 commits in total.
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
The text was updated successfully, but these errors were encountered: