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 grunt-plato is breaking the build 🚨 #4

Open
greenkeeper bot opened this issue Nov 6, 2017 · 1 comment
Open

An in-range update of grunt-plato is breaking the build 🚨 #4

greenkeeper bot opened this issue Nov 6, 2017 · 1 comment

Comments

@greenkeeper
Copy link

greenkeeper bot commented Nov 6, 2017

Version 1.4.0 of grunt-plato was just published.

Branch Build failing 🚨
Dependency grunt-plato
Current Version 1.3.0
Type dependency

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

grunt-plato 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 could not complete due to an error Details

Commits

The new version differs by 12 commits ahead by 12, behind by 1.

  • 465cc07 1.4.0
  • d11113d 1.3.0
  • aab6fb9 Merge branch 'Olpays-master'
  • 433888e update dependencies
  • 8504ecd add eslint option
  • 45cc2ca Update plato dependency
  • 9b2a8f3 Updated package.json - Using https instead of ssh
  • 8fe8d7b Using olpays plato fork
  • 41767e0 Change plato to ES6 compatible version
  • 40b5a69 1.2.1
  • 780c6d3 Merge pull request #25 from yorch/master
  • 8990029 Fixes issue #23, ensures that blank lines on excludeFromFile does not add unnecessary chars to options.exclude

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 6, 2017

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