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 pluralize is breaking the build 🚨 #23

Open
greenkeeper bot opened this issue Jul 18, 2017 · 1 comment
Open

An in-range update of pluralize is breaking the build 🚨 #23

greenkeeper bot opened this issue Jul 18, 2017 · 1 comment

Comments

@greenkeeper
Copy link

greenkeeper bot commented Jul 18, 2017

Version 5.1.0 of pluralize just got published.

Branch Build failing 🚨
Dependency pluralize
Current Version 5.0.0
Type dependency

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

pluralize is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build is in progress Details
  • bitHound - Dependencies 1 failing dependency. Details
  • bitHound - Code No failing files. Details

Commits

The new version differs by 7 commits.

  • 05801dd 5.1.0
  • f3bba6b Filesize badge (#64)
  • b9f114e Add methods for isSingular and isPlural (#67)
  • fffaf87 Fix bower.json (#66)
  • 5a4a0aa Make anime/manga uncountable (#63)
  • 782732d Add "ous" words to uncountables, sort uncountables (#61)
  • 3da4a24 chore(package): update chai to version 4.0.0 (#58)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

@greenkeeper
Copy link
Author

greenkeeper bot commented Jul 18, 2017

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