Closed greenkeeper[bot] closed 7 years ago
After pinning to 11.0.3 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Your tests are still failing with this version. Compare the changes 🚨
The new version differs by 7 commits.
b2ff72d
chore(release): 11.2.0
97b962e
chore: explicit update of istanbul-lib-instrument (#662)
0dcceda
feat: allow cwd to be configured see #620
0fc6d8f
chore: add support for --cwd (#542) (#620)
658dba4
fix: remove excluded files from coverage before writing (#649)
dd40dc5
feat: add possibility to filter coverage-maps (#637)
fb3ab92
docs: add link to community slack (#639)
See the full diff
Your tests are still failing with this version. Compare the changes 🚨
Version 11.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 could not complete due to an error [Details](https://travis-ci.org/unional/jspm-config/builds/258950944?utm_source=github_status&utm_medium=notification)Commits
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
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: