This version is covered by your current version range and after updating it in your project the build failed.
As mocha 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
- β **bitHound - Code** 1 failing file. [Details](https://www.bithound.io/github/arlac77/registry-mixin/e16c0295ef2e53f3480b2a36066b652ec509a8be/files#filter-failing-file)
- β **bitHound - Dependencies** No failing dependencies. [Details](https://www.bithound.io/github/arlac77/registry-mixin/e16c0295ef2e53f3480b2a36066b652ec509a8be/dependencies/npm?status=passing)
- β **continuous-integration/travis-ci/push** The Travis CI build passed [Details](https://travis-ci.org/arlac77/registry-mixin/builds/259569436?utm_source=github_status&utm_medium=notification)
- β **coverage/coveralls** First build on greenkeeper/mocha-3.5.0 at 91.525% [Details](https://coveralls.io/builds/12631203)
- β **codecov/patch** Coverage not affected when comparing 942ac9d...e16c029 [Details](https://codecov.io/gh/arlac77/registry-mixin/commit/e16c0295ef2e53f3480b2a36066b652ec509a8be)
- β **codecov/project** 91.52% remains the same compared to 942ac9d [Details](https://codecov.io/gh/arlac77/registry-mixin/commit/e16c0295ef2e53f3480b2a36066b652ec509a8be)
Release Notesfree-as-in-freezing
Old issues and PRs are now being marked "stale" by Probot's "Stale" plugin. If an issue is marked as such, and you would like to see it remain open, simply add a new comment to the ticket or PR.
WARNING: Support for non-ES5-compliant environments will be dropped starting with version 4.0.0 of Mocha!
2408d90Make dependencies use older version of readable-stream to work around incompatibilities introduced by 2.3.0 on June 19th
68a1466Try not clearing the env for debug in the integration test and see if that fixes Node 0.10 on AppVeyor; if need be, some other fix/workaround can be applied to handle whatever was up with debug without causing this issue
958fbb4Update new tests to work in browser per test hierarchy reorganization
1df7c94Merge pull request #2704 from seppevs/increase_test_coverage_of_mocha_js
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).
After pinning to 3.4.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Version 3.5.0 of mocha just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As mocha 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
- β **bitHound - Code** 1 failing file. [Details](https://www.bithound.io/github/arlac77/registry-mixin/e16c0295ef2e53f3480b2a36066b652ec509a8be/files#filter-failing-file) - β **bitHound - Dependencies** No failing dependencies. [Details](https://www.bithound.io/github/arlac77/registry-mixin/e16c0295ef2e53f3480b2a36066b652ec509a8be/dependencies/npm?status=passing) - β **continuous-integration/travis-ci/push** The Travis CI build passed [Details](https://travis-ci.org/arlac77/registry-mixin/builds/259569436?utm_source=github_status&utm_medium=notification) - β **coverage/coveralls** First build on greenkeeper/mocha-3.5.0 at 91.525% [Details](https://coveralls.io/builds/12631203) - β **codecov/patch** Coverage not affected when comparing 942ac9d...e16c029 [Details](https://codecov.io/gh/arlac77/registry-mixin/commit/e16c0295ef2e53f3480b2a36066b652ec509a8be) - β **codecov/project** 91.52% remains the same compared to 942ac9d [Details](https://codecov.io/gh/arlac77/registry-mixin/commit/e16c0295ef2e53f3480b2a36066b652ec509a8be)Release Notes
free-as-in-freezing3.5.0 / 2017-07-31
--forbid-only
and--forbid-pending
flags. Use these in CI or hooks to ensure tests aren't accidentally being skipped! (@charlierudolph)--napi-modules
flag (@jupp0r)Commits
The new version differs by 34 commits.
82d879f
Release v3.5.0
bf687ce
update mocha.js for v3.5.0
ec73c9a
update date for release of v3.5.0 in CHANGELOG [ci skip]
1ba2cfc
update CHANGELOG.md for v3.5.0 [ci skip]
065e14e
remove custom install script from travis (no longer needed)
4e87046
update karma-sauce-launcher URL for npm@5
6886ccc
increase timeout for slow-grepping test
2408d90
Make dependencies use older version of readable-stream to work around incompatibilities introduced by 2.3.0 on June 19th
68a1466
Try not clearing the env for debug in the integration test and see if that fixes Node 0.10 on AppVeyor; if need be, some other fix/workaround can be applied to handle whatever was up with debug without causing this issue
958fbb4
Update new tests to work in browser per test hierarchy reorganization
1df7c94
Merge pull request #2704 from seppevs/increase_test_coverage_of_mocha_js
1f270cd
Stop timing out (#2889)
27c7496
upgrade to debug@2.6.8; closes #2859 (#2860)
50fc47d
fix CI; closes #2867 (#2868)
1b1377c
Add test for ignoreLeaks and fix descriptions
There are 34 commits in total.
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: