An in-range update of puppeteer is breaking the build π¨
greenkeeper opened this issue Β· 2 comments
Version 1.6.1 of puppeteer was just published.
Branch | Build failing π¨ |
---|---|
Dependency | puppeteer |
Current Version | 1.6.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
puppeteer is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
- β continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
Release Notes
v1.6.1Big Changes
- Chromium 69.0.3494.0 (r575458)
API changes
No API changes.
Bug Fixes
- #2927 - Bad font rendering on Linux
Raw notes
0a4f24a - chore: mark version v1.6.1
45e140a - fix(launcher): always add about:blank
to default arguments.
66289bd - fix: bump Chromium version to fix font rendering on Linux
Commits
The new version differs by 3 commits.
0a4f24a
chore: mark version v1.6.1
45e140a
fix(launcher): always add
about:blank
to default arguments.66289bd
fix: bump Chromium version to fix font rendering on Linux
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 π΄
After pinning to 1.6.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
False positive