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 js-file-download is breaking the build 🚨 #30

Open
greenkeeper bot opened this issue Mar 21, 2019 · 1 comment
Open

An in-range update of js-file-download is breaking the build 🚨 #30

greenkeeper bot opened this issue Mar 21, 2019 · 1 comment

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Mar 21, 2019

The dependency js-file-download was updated from 0.4.4 to 0.4.5.

🚨 View failing branch.

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

js-file-download 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 failed (Details).

Commits

The new version differs by 10 commits.

  • 431da63 bump version to 0.4.5
  • ad1a0dc Merge pull request #45 from wkillerud/infra/linting
  • 7002707 Merge pull request #44 from wkillerud/fix/typings
  • 7a45656 Have Travis use the latest LTS of Node when running CI
  • 582bb40 Add eslint as a mimimal form of testing for CI
  • bc191c9 Add valid inputs to new Blob() to typings
  • b4b5798 Merge pull request #42 from Jono20201/patch-2
  • 8e1e7b7 Update README.md
  • a39fb77 Merge pull request #41 from Jono20201/patch-1
  • 0c65881 Update package.json

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 Mar 21, 2019

After pinning to 0.4.4 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