vstirbu/fsm-as-promised

An in-range update of uuid is breaking the build 🚨

greenkeeper opened this issue · 1 comments

greenkeeper commented

Version 3.3.0 of uuid was just published.

Branch Build failing 🚨
Dependency [uuid](https://github.com/kelektiv/node-uuid)
Current Version 3.2.1
Type dependency

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

uuid 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
  • ✅ coverage/coveralls First build on greenkeeper/uuid-3.3.0 at 98.02% Details
Commits

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

  • 1cb9826 chore(release): 3.3.0
  • f3e48ff fix: fix #229
  • 854df05 chore: update dev dependencies (to fix security alerts)
  • 02161b2 Merge branch 'master' of github.com:kelektiv/node-uuid
  • beffff8 fix: assignment to readonly property to allow running in strict mode (#270)
  • 931c70d Merge branch 'master' of github.com:kelektiv/node-uuid
  • 0705cd5 feat: enforce Conventional Commit style commit messages (#282)
  • 2e33970 chore: Add Active LTS and Active versions of Node.js (#279)
  • 205e0ed fix: Get correct version of IE11 crypto (#274)
  • d062fdc fix: assignment to readonly property to allow running in strict mode (#270)
  • c47702c fix: mem issue when generating uuid (#267)
  • cc9a182 feat: enforce Conventional Commit style commit messages (#282)
  • 44c7f9f Add Active LTS and Active versions of Node.js (#279)
  • 153d331 fix: Get correct version of IE11 crypto (#274)
  • df40e54 fix assignment to readonly property to allow running in strict mode (#270)

There are 17 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 commented

After pinning to 3.2.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.