-
Notifications
You must be signed in to change notification settings - Fork 0
An in-range update of type-coverage is breaking the build 🚨 #3
Comments
After pinning to 2.0.4 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 12 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 passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 10 commits.
See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 19 commits.
There are 19 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 37 commits.
There are 37 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 66 commits.
There are 66 commits in total. See the full diff |
The devDependency type-coverage was updated from
2.0.4
to2.1.0
.🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
type-coverage 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 15 commits.
51790ee
v2.1.0
92dbffc
chore: use yarn workspaces
0576777
fix: ci failure
ba61be7
feat: extract ts-lib-utils package
94385d4
fix: lint error
864a21c
chore: update dependencies
f124bef
fix: ci failure
53db314
refactor: remove standard
815132a
feat: add eslint rules
5ad7db0
refactor: use eslint instead of tslint
d8e79bf
chore: update dependencies
4bd0f8d
docs: add info about type-coverage-watcher to the readme
b227529
chore: update no-unused-export
00e6c14
chore: update no-unused-export
fbab1cf
chore: update no-unused-export
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: