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 fast-csv is breaking the build 🚨 #51

Open
greenkeeper bot opened this issue Apr 24, 2019 · 1 comment
Open

An in-range update of fast-csv is breaking the build 🚨 #51

greenkeeper bot opened this issue Apr 24, 2019 · 1 comment

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Apr 24, 2019

The dependency fast-csv was updated from 2.4.1 to 2.5.0.

🚨 View failing branch.

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

fast-csv 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 is in progress (Details).
  • continuous-integration/appveyor/branch: AppVeyor build failed (Details).

Commits

The new version differs by 10 commits.

  • d4e33a2 updating history file and version number
  • 5101f20 Merge pull request #254 from C2FO/v2-safe-buffer-initilization
  • 0e93232 Test against more node versions
  • f56b0e5 Fix grunt errors in node > 6
  • a9542cc Use safer-buffer in place of Buffer
  • 7cddebd Install safer-buffer
  • c1d50f8 adding more current node versions to ci
  • 0d0546d Merge pull request #245 from montera82/patch-1
  • 5aeb9e6 Fix grammar to make doc more professional
  • a6a190b Updated description of Writing Data block (#199)

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 24, 2019

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

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

0 participants