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 change-case is breaking the build 🚨 #26

Open
greenkeeper bot opened this issue Feb 25, 2018 · 1 comment
Open

An in-range update of change-case is breaking the build 🚨 #26

greenkeeper bot opened this issue Feb 25, 2018 · 1 comment

Comments

@greenkeeper
Copy link

greenkeeper bot commented Feb 25, 2018

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 3.0.2 of change-case was just published.

Branch Build failing 🚨
Dependency change-case
Current Version 3.0.1
Type dependency

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

change-case 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

Release Notes Min `no-case`

Fixed

  • Updated the min version of no-case required
Commits

The new version differs by 8 commits.

  • 12dbbc9 3.0.2
  • ea3ee2c chore(package): update mocha to version 5.0.0 (#42)
  • f91cea6 Fix lower case test name (#43)
  • c358398 Update no-case min version (#45)
  • c61014e chore(package): update mocha to version 4.0.0 (#39)
  • c0132ea Add Greenkeeper badge 🌴 (#38)
  • c3ec1c0 chore(package): update standard to version 10.0.0 (#36)
  • dbb9a1d chore(package): update standard to version 9.0.2 (#34)

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 Feb 25, 2018

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