An in-range update of nyc is breaking the build π¨
Closed this issue Β· 0 comments
greenkeeper commented
Version 10.3.0 of nyc just got published.
Branch | Build failing π¨ |
---|---|
Dependency | nyc |
Current Version | 10.2.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
- β **continuous-integration/appveyor/branch** AppVeyor build failed [Details](https://ci.appveyor.com/project/jescalan/spike-core/build/1.0.10),- β **coverage/coveralls** First build on greenkeeper/nyc-10.3.0 at 98.311% [Details](https://coveralls.io/builds/11301169),- β **continuous-integration/travis-ci/push** The Travis CI build passed [Details](https://travis-ci.org/static-dev/spike-core/builds/227079893?utm_source=github_status&utm_medium=notification)Commits
The new version differs by 4 commits ahead by 4, behind by 2.
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)
false
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 π΄