-
Notifications
You must be signed in to change notification settings - Fork 24
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 🚨 #540
Comments
After pinning to 11.2.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
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.7.1 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.7.2 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 6 commits.
See the full diff |
Version 11.7.3 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 11.8.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 11.3.0 of nyc was just published.
This version is covered by your current version range and after updating it in your project the build failed.
nyc is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
Status Details
Commits
The new version differs by 12 commits.
d85118c
chore(release): 11.3.0
7792733
chore: explicitly update istanbul dependencies (#698)
222a3d0
chore: slight difference in pinning logic, based on @ljharb's advice
f04b7a9
feat: add option to hook vm.runInContext (#680)
cdfdff3
feat: add --exclude-after-remap option for users who pre-instrument their codebase (#697)
a413f6a
chore: upgrade to yargs 10 (#694)
10125aa
docs: fix reporters link
f5089ca
docs: added examples of coverage reports (#656)
af281e7
chore: update spawn-wrap to 1.4.0 (#692)
a685f7c
docs: missing options prefix -- in front of check-coverage (#695)
f31d7a6
feat: allow instrument-only to produce sourcemaps (#674)
425c0fd
chore: ignore package-lock.json (#683)
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
The text was updated successfully, but these errors were encountered: