search

tunnckoCore / assert-kindof

Check native type of the given value and throw TypeError if not okey. Expressive, elegant, behavior-driven API, good descriptive default error messages, simple and clean syntax.
http://j.mp/19crqvf
MIT License
4 stars 0 forks source link

An in-range update of pre-commit is breaking the build 🚨 #13

Closed greenkeeper[bot] closed 7 years ago

greenkeeper[bot] commented 7 years ago

Version 1.2.0 of pre-commit just got published.

Branch Build failing 🚨
Dependency pre-commit
Current Version 1.1.3
Type devDependency

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

As pre-commit is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:

Status Details - ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/tunnckoCore/assert-kindof/builds/182566909) - ✅ **coverage/coveralls** First build on greenkeeper/pre-commit-1.2.0 at 100.0% [Details](https://coveralls.io/builds/9205394)
Commits

The new version differs by 8 commits .

  • 1689e3e [dist] 1.2.0 - Better windows support
  • a9c9732 solves the windows issue (with symlinks) (#84)
  • 4167676 chore(package): update mocha to version 3.2.0 (#86)
  • 3cf4cf7 chore(package): update dependencies (#85)
  • 7154dee Update dep to remove warn about cross-spaw (#76)
  • ead9484 cross-spawn@4 (#77)
  • fec48cb [ci] Remove NPM hack and old npm
  • 18da668 [deps] Fix npmgate

See the full diff.

Not sure how things should work exactly? There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 7 years ago

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