Skip to content
This repository has been archived by the owner on Apr 11, 2018. It is now read-only.

An in-range update of nyc is breaking the build 🚨 #76

Open
greenkeeper bot opened this issue May 5, 2017 · 0 comments
Open

An in-range update of nyc is breaking the build 🚨 #76

greenkeeper bot opened this issue May 5, 2017 · 0 comments

Comments

@greenkeeper
Copy link

greenkeeper bot commented May 5, 2017

Version 10.3.2 of nyc just got published.

Branch Build failing 🚨
Dependency nyc
Current Version 10.3.1
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
  • dependency-ci Dependencies checked Details,- ✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details,- ❌ continuous-integration/travis-ci/push The Travis CI build failed Details,- ✅ coverage/coveralls First build on greenkeeper/nyc-10.3.2 at 100.0% Details

Commits

The new version differs by 2 commits0.

  • e062a86 chore(release): 10.3.2
  • 213206f fix: we should not create a cache folder if cache is false (#567)

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 🌴

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

0 participants