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 cuid is breaking the build 🚨 #83

Open
greenkeeper bot opened this issue Dec 16, 2019 · 1 comment
Open

An in-range update of cuid is breaking the build 🚨 #83

greenkeeper bot opened this issue Dec 16, 2019 · 1 comment

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Dec 16, 2019

The dependency cuid was updated from 2.1.6 to 2.1.8.

🚨 View failing branch.

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

cuid 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 62 commits.

  • c0a96db 2.1.8
  • b96071e 2.1.7
  • df4b670 Merge pull request #133 from k2s/patch-1
  • cf90e3b Merge pull request #1 from glnc/patch-1
  • 3ba4397 Implemented tests running within a worker
  • b077e6e Let testcafe start and kill http-server
  • 7d19475 Indent using spaces (instead of tabs)
  • d238065 Added boilerplate for executing cuid() within a worker
  • a23a73f Merge branch 'master' into patch-1
  • 3a5e7db Update dependency uglify-js to v3.7.2
  • e1d0dbe Update dependency uglify-js to v3.7.1
  • 053dbf8 Update dependency uglify-js to v3.7.0
  • 753a47a Update dependency uglify-js to v3.6.9
  • dfa68a3 Update dependency uglify-js to v3.6.8
  • dc0b468 Update dependency riteway to v6.1.1

There are 62 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
Copy link
Contributor Author

greenkeeper bot commented Dec 16, 2019

After pinning to 2.1.6 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