-
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 nyc is breaking the build 🚨 #26
Comments
After pinning to 11.0.3 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Version 11.2.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 7 commits.
See the full diff |
Version 11.2.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 11.3.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 12 commits.
See the full diff |
Version 11.4.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 13 commits.
See the full diff |
Version 11.6.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 12 commits.
See the full diff |
Version 11.1.0 of nyc just got published.
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
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 🌴
The text was updated successfully, but these errors were encountered: