-
Notifications
You must be signed in to change notification settings - Fork 51
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 🚨 #87
Comments
After pinning to 2.2.0 your tests are passing again. Downgrade this dependency 📌. |
Your tests are still failing with this version. Compare changes Release Notes for v2.3.0See CHANGELOG. CommitsThe new version differs by 4 commits ahead by 4, behind by 6.
See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v2.4.0See CHANGELOG. CommitsThe new version differs by 13 commits.
See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v2.4.1See CHANGELOG. |
Your tests are still failing with this version. Compare changes Release Notes for v2.5.0See CHANGELOG. CommitsThe new version differs by 5 commits.
See the full diff |
Your tests are still failing with this version. Compare changes |
The dependency node-fetch was updated from
2.2.0
to2.2.1
.🚨 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
Release Notes for v2.2.1
See CHANGELOG.
Commits
The new version differs by 8 commits.
ac07bf7
2.2.1
9a32fd3
ready for release
4bc21da
doc update
5494e19
compress flag should not overwrite accept encoding header
91e1c0b
avoid named export for compatibility below node 10
d935121
fix import rule for stream PassThrough
8cc909f
update readme to add credits and call for collaborators (#540)
745a27c
README update (#504)
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: