-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An in-range update of codacy-coverage is breaking the build 🚨 #32
Comments
After pinning to 2.0.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Version 2.0.4 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 20 commits.
There are 20 commits in total. See the full diff |
Version 2.1.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release NotesRelease 2.1.0Improvements
|
Version 2.1.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 2.0.3 of codacy-coverage just got published.
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
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 🌴
The text was updated successfully, but these errors were encountered: