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 gulp-coffee is breaking the build 🚨 #3

Open
greenkeeper bot opened this issue Nov 1, 2018 · 1 comment
Open

An in-range update of gulp-coffee is breaking the build 🚨 #3

greenkeeper bot opened this issue Nov 1, 2018 · 1 comment

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Nov 1, 2018

The devDependency gulp-coffee was updated from 3.0.2 to 3.0.3.

🚨 View failing branch.

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

gulp-coffee 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
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 10 commits.

  • 39df753 3.0.3
  • 8c9ec9a Merge pull request #89 from TheDancingCode/no-coercion
  • 9db3c01 Merge pull request #90 from TheDancingCode/remove-require
  • 64b0784 Remove unneeded Mocha require statement
  • 8cd8339 Avoid implicit type coercion
  • f668318 Remove unused variables
  • 428393b Replace deprecated new Buffer()
  • 841228b Update repo location
  • 95c3621 Replace unneeded merge
  • a752a2a Fix node version in README

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 Nov 1, 2018

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