-
-
Notifications
You must be signed in to change notification settings - Fork 0
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 dotest is breaking the build 🚨 #18
Comments
After pinning to 2.5.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Your tests are still failing with this version. Compare changes CommitsThe new version differs by 9 commits.
See the full diff |
Your tests are still failing with this version. Compare changes CommitsThe new version differs by 9 commits.
See the full diff |
Your tests are still failing with this version. Compare changes |
The devDependency dotest was updated from
2.5.0
to2.6.0
.🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
dotest 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.
e8d3095
2.6.0
85f85d9
Docs(changelog): Update changelog
330083e
Refactor: Replaced istanbul with nyc
0bcf073
Chore(package): Update dependencies
f138e11
Chore(package): Update minimum node version
d48e381
Docs: Minor clean up
2892933
Test: Improve coverage for error() and fail()
786d1ca
Feat: Add log() dontCount argument
0fb58f7
Test(config): Update Travis node versions
57bfb71
Test(config): Update ESLint ES version to 2017
9a4401d
chore(package): update eslint to version 5.15.2 (#30)
667f55d
Fix(runner): Incorrect Codacy env check
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: