pvdlg / uprogress

:rainbow: μProgress - Lightweight and performant progress bar, with smooth GPU animation
https://pvdlg.github.io/uprogress/
MIT License
67 stars 4 forks source link

An in-range update of puppeteer is breaking the build 🚨 #202

Closed greenkeeper[bot] closed 5 years ago

greenkeeper[bot] commented 5 years ago

The devDependency puppeteer was updated from 1.9.0 to 1.10.0.

🚨 View failing branch.

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 - ✅ **bundlesize:** Total bundle size is 2.71KB/2.98KB (no change) ([Details](https://goo.gl/v1ALmp)). - ❌ **continuous-integration/travis-ci/push:** The Travis CI build could not complete due to an error ([Details](https://travis-ci.org/pvdlg/uprogress/builds/449665330?utm_source=github_status&utm_medium=notification)).

Release Notes for v1.10.0

Big Changes

API Changes

Added:

Bug Fixes

  • #921 - userDataDir + headless = lost authorization #921
  • #2033 - Feature request: Inspect screen reader output #2033
  • #3303 - docs: Add an example of chrome extension testing on CI
  • #3455 - No errors are thrown on asyncawait check. #3455

Raw Notes

cffcaad - chore: mark version v1.10.0
9ba3261 - feat(accessibility): snapshot the accessibility tree (#3470)
eca3c6b - test(cookies): cookies from headful now work in headless (#3481)
3596c5f - fix(page.evaluate): better function serialization (#3480)
e061007 - docs(api.md): update compatibility table
4110087 - docs(puppeteer-web): a note about running inside extension (#3477)
8e93eab - docs(api.md): add example to override request headers (#3475)
2a88690 - fix(launcher): add flags to improve reliability (#3474)
3dd5c28 - fix(pipe): dispatch "disconnected" event when browser is terminated (#3472)
9800b2c - docs(api.md): Fix missing await in extension example (#3447)
81edbbb - fix(clicking): handle negative area results in computeQuadArea (#3413)
fae441c - docs(troubleshooting): add workarounds for code transpilation (#3399)
cf8c62e - docs(api.md): Fix ElementHandle example (#3401)
d025d1f - fix(csscoverage): don't prematurely disable the CSS domain (#3418)
a4cebd8 - feat(chromium): roll Chromium to r599821 (#3414)
0fd3bfb - test(CSSCoverage): failing test when a stylesheet was recently added (#3400)
a04dedc - docs(troubleshooting.md): run non-headless on CI (#3353)
0bb462c - docs(readme): clarify SPA and SSR (#3363)
6ac66c3 - feat: browser.waitForTarget (#3356)
07febb6 - fix: add missing location property to some key descriptors (#3354)
90d1fe8 - docs(api): fixed grammatical error (it's -> its) #3352
af4209f - chore: bump version to v1.9.0-post (#3351)

Commits

The new version differs by 22 commits.

  • e9d89a2 chore: mark version v1.10.0 (#3482)
  • 9ba3261 feat(accessibility): snapshot the accessibility tree (#3470)
  • eca3c6b test(cookies): cookies from headful now work in headless (#3481)
  • 3596c5f fix(page.evaluate): better function serialization (#3480)
  • e061007 docs(api.md): update compatibility table
  • 4110087 docs(puppeteer-web): a note about running inside extension (#3477)
  • 8e93eab docs(api.md): add example to override request headers (#3475)
  • 2a88690 fix(launcher): add flags to improve reliability (#3474)
  • 3dd5c28 fix(pipe): dispatch "disconnected" event when browser is terminated (#3472)
  • 9800b2c docs(api.md): Fix missing await in extension example (#3447)
  • 81edbbb fix(clicking): handle negative area results in computeQuadArea (#3413)
  • fae441c docs(troubleshooting): add workarounds for code transpilation (#3399)
  • cf8c62e docs(api.md): Fix ElementHandle example (#3401)
  • d025d1f fix(csscoverage): don't prematurely disable the CSS domain (#3418)
  • a4cebd8 feat(chromium): roll Chromium to r599821 (#3414)

There are 22 commits in total.

See the full diff

FAQ and help There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 5 years ago

After pinning to 1.9.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.