Open greenkeeper[bot] opened 7 years ago
Your tests are still failing with this version. Compare the changes 🚨
Your tests are still failing with this version. Compare the changes 🚨
The new version differs by 5 commits.
a3f033f
chore(release): 11.1.0
a076951
chore: upgrade to latest version of istanbul-lib-instrument
8768afe
feat: upgrade to version of spawn-wrap that supports .EXE (#626)
2d92501
chore: attempt to fix appveyor (#623)
bbadc1f
feat: add support for per file coverage checking (#591)
See the full diff
Version 11.0.2 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
- ✅ **coverage/coveralls** First build on greenkeeper/nyc-11.0.2 at 23.077% [Details](https://coveralls.io/builds/11812298) - ✅ **continuous-integration/travis-ci/push** The Travis CI build passed [Details](https://travis-ci.org/aureooms/js-polynomial/builds/238972790?utm_source=github_status&utm_medium=notification) - ❌ **codecov/project** No report found to compare against [Details](https://codecov.io/gh/aureooms/js-polynomial/commit/c4f20937d631fb554c19be7ab322d43bb091f681) - ✅ **codecov/patch** Coverage not affected. [Details](https://codecov.io/gh/aureooms/js-polynomial/commit/c4f20937d631fb554c19be7ab322d43bb091f681)Commits
The new version differs by 2 commits.
e4eff12
chore(release): 11.0.2
0c2ef43
chore: upgrade to newer version of spawn-wrap (#592)
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: