Skip to content

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

@greenkeeper

Description

@greenkeeper

Version 11.1.0 of nyc just got published.

Branch Build failing 🚨
Dependency nyc
Current Version 11.0.3
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
  • bitHound - Dependencies 1 failing dependency. Details
  • bitHound - Code No failing files. Details
  • continuous-integration/travis-ci/push The Travis CI build passed Details
  • coverage/coveralls First build on greenkeeper/nyc-11.1.0 at 100.0% Details

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 and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions