This version is covered by your current version range and after updating it in your project the build failed.
As nyc 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 passed [Details](https://travis-ci.org/node-minibase/minibase/builds/192899778)
- ✅ **coverage/coveralls** First build on greenkeeper/nyc-10.1.0 at 100.0% [Details](https://coveralls.io/builds/9717869)
- ❌ **continuous-integration/appveyor/branch** AppVeyor build failed [Details](https://ci.appveyor.com/project/tunnckoCore/minibase/build/1.0.61)
Commits
8c58d68fix: address edge-cases related to --all when instrumentation is disabled (#482)
8b58c05feat: allow eager instantiation of instrumenter (#490)
d8d2de0feat: upgrade to istanbul-lib-instrument with support for 'const foo = function () {}' name preservation. upgrade to istanbul-lib-hook with fix for ts-node. (#494)
7708235chore: add test and docs for high and low watermarks (#493)
0a1d72afeat: reporting watermarks can now be set in nyc config stanza (#469)
1022b16fix: pass configuration options to --check-coverage (#483)
7b4c090chore(package): update tap to version 9.0.3 (#488)
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).
Version 10.1.0 of nyc just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As nyc 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 passed [Details](https://travis-ci.org/node-minibase/minibase/builds/192899778) - ✅ **coverage/coveralls** First build on greenkeeper/nyc-10.1.0 at 100.0% [Details](https://coveralls.io/builds/9717869) - ❌ **continuous-integration/appveyor/branch** AppVeyor build failed [Details](https://ci.appveyor.com/project/tunnckoCore/minibase/build/1.0.61)Commits
The new version differs by 14 commits .
8f7af3achore(release): 10.1.08c58d68fix: address edge-cases related to --all when instrumentation is disabled (#482)8b58c05feat: allow eager instantiation of instrumenter (#490)d8d2de0feat: upgrade to istanbul-lib-instrument with support for 'const foo = function () {}' name preservation. upgrade to istanbul-lib-hook with fix for ts-node. (#494)7708235chore: add test and docs for high and low watermarks (#493)0a1d72afeat: reporting watermarks can now be set in nyc config stanza (#469)1022b16fix: pass configuration options to --check-coverage (#483)7b4c090chore(package): update tap to version 9.0.3 (#488)093963bchore(release): 10.0.2e01ec8cfix: upgrade to newer istanbul-lib-instrument, with fixes for inferred function names (#479)2e39e00chore(release): 10.0.1e0ef1d5fix: upgrade spawn-wrap and istanbul-lib-instrument (#477)8603aa9chore(package): update is-windows to version 1.0.0 (#466)64ae4f3chore(package): update standard-version to version 4.0.0 (#461)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: