fnogatz/CHR.js

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

Closed this issue Β· 1 comments

Version 3.2.0 of uuid was just published.

Branch Build failing 🚨
Dependency uuid
Current Version 3.1.0
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 could not complete due to an error Details

Commits

The new version differs by 14 commits.

  • c0d44fd Publish v3.2.0 (#240)
  • eaa9f4e Use standard-version for release (#246)
  • 67d697c Fix #248 (#251)
  • 1fef18b fix: use msCrypto if available. Fixes #241 (#247)
  • 815daa3 eslint (#224)
  • bba9402 eslint (#219)
  • 0ea33e6 use typeof to check for crypto rather than global. Fixes #185 (#221)
  • c1f720d Defer random initialization of node and clockseq. Fixes #189 (#220)
  • dc02a76 UUID v3 Support (#217)
  • 72fbabb Corrected version from v4->v5 in README_js.md (#215)
  • 962c80a Use runmd to build README (#204)
  • e2389b3 Fix parentheses typo in README.md (#203)
  • 880d24e Update README.md (#208)
  • 8e23981 Fix buffer not being modified (uuid v5) (#201)

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 🌴

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