Skip to content

An in-range update of codacy-coverage is breaking the build 🚨 #32

@greenkeeper

Description

@greenkeeper

Version 2.0.3 of codacy-coverage just got published.

Branch Build failing 🚨
Dependency codacy-coverage
Current Version 2.0.2
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As codacy-coverage 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 - Code No failing files. Details
  • bitHound - Dependencies No failing dependencies. Details
  • coverage/coveralls Coverage pending from Coveralls.io Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 6 commits.

  • e78ef3d Release version 2.0.3
  • 42dee02 Update package locks
  • 41a5e42 Merge pull request #45 from codacy/FixJSCoverageReporting
  • ab4d849 Remove buddy js
  • a3f841a Fixed wrong JS coverage reporting
  • ecc496e One more test for total coverage values

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