search

chrisguttandin / fast-unique-numbers

A module to create a set of unique numbers as fast as possible.
MIT License
2 stars 0 forks source link

An in-range update of karma is breaking the build 🚨 #449

Closed greenkeeper[bot] closed 4 years ago

greenkeeper[bot] commented 4 years ago

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

The devDependency karma was updated from 5.0.2 to 5.0.3.

🚨 View failing branch.

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

karma is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details - ❌ **continuous-integration/travis-ci/push:** The Travis CI build could not complete due to an error ([Details](https://travis-ci.org/github/chrisguttandin/fast-unique-numbers/builds/681283101?utm_source=github_status&utm_medium=notification)).
Release Notes for v5.0.3

5.0.3 (2020-04-29)

Bug Fixes

Commits

The new version differs by 9 commits.

  • dee09d8 chore(release): 5.0.3 [skip ci]
  • e44ca94 fix(client): flush resultsBuffer on engine upgrade (#3212)
  • f9ef33a chore(test): update Cucumber to the latest version (#3480)
  • 3b854ad chore(ci): fix BrowserStack timeouts (#3484)
  • 518d001 chore(ci): cleanup Travis config (#3481)
  • fc9ea9a chore(ci): use recommended timeouts for browserstack (#3475)
  • fd8c3a6 chore(test): remove @not-jenkins tag for Cucumber tests (#3479)
  • b52333d docs: simplify repository setup steps (#3478)
  • 652e24e chore(build): run cucumber tests using NPM scripts instead of Grunt (#3476)

See the full diff

FAQ and help There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 4 years ago

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