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-nodemon is breaking the build 🚨 #295

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

An in-range update of gulp-nodemon is breaking the build 🚨 #295

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

Comments

@greenkeeper
Copy link

greenkeeper bot commented Nov 3, 2018

The devDependency gulp-nodemon was updated from 2.2.1 to 2.4.1.

🚨 View failing branch.

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

gulp-nodemon 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 could not complete due to an error (Details).

Commits

The new version differs by 16 commits.

  • b4234a3 Version bump
  • 033c27b Merge pull request #159 from bennyn/patch-1
  • 7ce2da0 Support Ctrl + C on Windows
  • 1a31fa2 Update nodemon. Remove (erroneously named) "test" folder.
  • 628b239 Update README.md
  • ff92bba Update README.md
  • 9927ad5 Version 2.4.0, ignore package-lock.json in .gitignore
  • d087b15 Merge pull request #151 from cnshenj/master
  • c1ef02d Update gulp to 4.x.x
  • c49b947 Version bump
  • 59be245 Merge pull request #135 from dmm/master
  • f431571 Use locally installed gulp to run tasks.
  • b271168 Merge pull request #133 from Dvbnhbq/patch-1
  • de73518 Add some original nodemon colour
  • 979bb1e Merge pull request #132 from XescuGC/update_readmee

There are 16 commits in total.

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
Author

greenkeeper bot commented Nov 3, 2018

After pinning to 2.2.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