Skip to content

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

Description

@greenkeeper

Version 1.0.9 of chance just got published.

Branch Build failing 🚨
Dependency chance
Current Version 1.0.8
Type dependency

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

chance 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
  • ci/circleci CircleCI is running your tests Details
  • bitHound - Code 2 failing files. Details
  • bitHound - Dependencies No failing dependencies. Details

Commits

The new version differs by 40 commits.

  • 6c78cd5 Bump version to 1.0.9 to include #298
  • 730880b Remove no longer used file
  • bcaca21 Merge pull request #298 from pcmill/Add-dutch-names
  • fc8b400 More test coverage
  • 4584c13 Try this again with the correct script steps
  • 5b164ce Try moving coveralls to own step
  • ac8aa9d Update lint rules, remove unused files
  • 04e7a02 Run nyc with ava before trying to upload to coveralls
  • ac85d70 Remove Grunt, move dependencies back to dev dependencies, install nyc for coverage
  • d8fcb63 Merge #315
  • 800b526 Move test back to proper place, remove dupe test
  • 60a1e00 More stringent lint rules
  • 7a612c9 Fix lint issues
  • 83ae155 Wrap up test fixing
  • ce6cd22 Move regional and text to new testing framework

There are 40 commits in total.

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 🌴

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions