An in-range update of nyc is breaking the build π¨
greenkeeper opened this issue Β· 2 comments
Version 10.2.0 of nyc just got published.
Branch | Build failing π¨ |
---|---|
Dependency | nyc |
Current Version | 10.1.2 |
Type | devDependency |
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 πͺ
Status Details
Commits
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.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
Version 10.3.0 just got published.
Your tests are still failing with this version. Compare the changes π¨
Commits
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
Version 10.3.2 just got published.
Your tests are still failing with this version. Compare the changes π¨
Commits
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