Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

An in-range update of node-fetch is breaking the build 🚨 #26

Closed
greenkeeper bot opened this issue Apr 26, 2019 · 4 comments
Closed

An in-range update of node-fetch is breaking the build 🚨 #26

greenkeeper bot opened this issue Apr 26, 2019 · 4 comments

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Apr 26, 2019

The dependency node-fetch was updated from 2.3.0 to 2.4.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

node-fetch 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
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for v2.4.0

See CHANGELOG.

Commits

The new version differs by 13 commits.

  • c9805a2 2.4.0 release (#616)
  • 49d7760 Pass custom timeout to subsequent requests on redirect (#615)
  • cfc8e5b Swap packagephobia badge for flat style (#592)
  • 2a2d438 Adding Brotli Support (#598)
  • 05f5ac1 Node 12 compatibility (#614)
  • 432c9b0 support reading blob with stream (#608)
  • 0ad136d Added new reading method to blob
  • bee2ad8 ignore buffers recalculation
  • e996bda Quick readme update
  • 1c2f07f Headers should not accept empty field name (#562)
  • 7d32932 Unify internal body as buffer (#552)
  • 35a4abe Fix spelling mistake (#551)
  • 2d0fc68 Clone URLSearchParams to avoid mutation (#547)

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 🌴

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Apr 26, 2019

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

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Apr 27, 2019

  • The dependency node-fetch was updated from 2.4.0 to 2.4.1.

Your tests are still failing with this version. Compare changes

Release Notes for v2.4.1

See CHANGELOG.

Commits

The new version differs by 2 commits.

  • b3ecba5 2.4.1 release (#619)
  • 1a88481 Fix Blob for older node versions and webpack. (#618)

See the full diff

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented May 1, 2019

  • The dependency node-fetch was updated from 2.4.1 to 2.5.0.

Your tests are still failing with this version. Compare changes

Release Notes for v2.5.0

See CHANGELOG.

Commits

The new version differs by 5 commits.

  • 0c2294e 2.5.0 release (#630)
  • 0fc414c Allow third party blob implementation (#629)
  • d8f5ba0 build: disable generation of package-lock since it is not used (#623)
  • 1fe1358 test: enable --throw-deprecation for tests (#625)
  • a35dcd1 chore(deps): address deprecated url-search-params package (#622)

See the full diff

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented May 16, 2019

  • The dependency node-fetch was updated from 2.5.0 to 2.6.0.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 2 commits.

  • 95286f5 v2.6.0 (#638)
  • bf8b4e8 Allow agent option to be a function (#632)

See the full diff

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant