Open greenkeeper[bot] opened 7 years ago
After pinning to 10.0.0 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 🚨
Your tests are still failing with this version. Compare the changes 🚨
The new version differs by 6 commits .
455619f
chore(release): 10.2.0
95cc09a
feat: upgrade to version of yargs with extend support (#541)
43535f9
chore: explicit update of istanbuljs dependencies (#535)
98ebdff
feat: allow babel cache to be enabled (#517)
50adde4
feat: exclude the coverage/ folder by default 🚀 (#502)
6a59834
chore(package): update tap to version 10.0.0 (#507)
See the full diff.
Your tests are still failing with this version. Compare the changes 🚨
The new version differs by 8 commits0.
55e826d
chore(release): 10.3.0
89dc7a6
chore: explicit update of istanbul dependnecies (#562)
1887d1c
feat: add support for --no-clean, to disable deleting raw coverage output (#558)
ff73b18
fix: source-maps were not being cached in the parent process when --all was being used (#556)
2ff8f3b
chore: test node 6 on travis (#553)
3c0d81f
docs(readme): move advanced features to docs site (#551)
fdf3e97
docs: switch to conventional commits badge
9f2d45f
docs(readme): link to available reporters (#546)
false
See the full diff
Your tests are still failing with this version. Compare the changes 🚨
The new version differs by 4 commits0.
e062a86
chore(release): 10.3.2
213206f
fix: we should not create a cache folder if cache is false (#567)
75713d8
chore(release): 10.3.1
1bf74fd
fix: introduced a bug that resulted in source-maps not being loaded approriately on second test run (#566)
false
See the full diff
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 is in progress [Details](https://travis-ci.org/langri-sha/screeps-modules/builds/192900392) - ❌ **bitHound - Dependencies** 1 failing dependency. [Details](https://www.bithound.io/github/langri-sha/screeps-modules/2e9c2e5a9c95bed93e498453961375503d23cdc1/dependencies/npm#filter-failing-dep) - ✅ **bitHound - Code** No failing files. [Details](https://www.bithound.io/github/langri-sha/screeps-modules/2e9c2e5a9c95bed93e498453961375503d23cdc1/files?status=passing)Commits
The new version differs by 14 commits .
8f7af3a
chore(release): 10.1.0
8c58d68
fix: address edge-cases related to --all when instrumentation is disabled (#482)
8b58c05
feat: allow eager instantiation of instrumenter (#490)
d8d2de0
feat: upgrade to istanbul-lib-instrument with support for 'const foo = function () {}' name preservation. upgrade to istanbul-lib-hook with fix for ts-node. (#494)
7708235
chore: add test and docs for high and low watermarks (#493)
0a1d72a
feat: reporting watermarks can now be set in nyc config stanza (#469)
1022b16
fix: pass configuration options to --check-coverage (#483)
7b4c090
chore(package): update tap to version 9.0.3 (#488)
093963b
chore(release): 10.0.2
e01ec8c
fix: upgrade to newer istanbul-lib-instrument, with fixes for inferred function names (#479)
2e39e00
chore(release): 10.0.1
e0ef1d5
fix: upgrade spawn-wrap and istanbul-lib-instrument (#477)
8603aa9
chore(package): update is-windows to version 1.0.0 (#466)
64ae4f3
chore(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: