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 tsconfig-holy-grail is breaking the build 🚨 #455

Closed greenkeeper[bot] closed 4 years ago

greenkeeper[bot] commented 4 years ago

🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚

Find out how to migrate to Snyk at greenkeeper.io

The devDependency tsconfig-holy-grail was updated from 11.0.9 to 11.0.10.

🚨 View failing branch.

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

tsconfig-holy-grail 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/684700450?utm_source=github_status&utm_medium=notification)).
Release Notes for v11.0.10

all commits

Commits

The new version differs by 8 commits.

  • 4c02df5 11.0.10
  • 5b406b3 fix(package): update cz-conventional-changelog to version 3.2.0
  • f9bed16 fix(package): update commitizen to version 4.1.2
  • 401703a fix(package): update @types/node to version 12.12.38
  • 51a8d62 fix(package): update commitizen to version 4.0.5
  • c2cf8a9 fix(package): update mocha to version 7.1.2
  • 4dfdfb5 fix(package): update eslint-config-holy-grail to version 46.0.16
  • afd632e fix(package): update eslint-config-holy-grail to version 46.0.15

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 11.0.9 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.