An in-range update of isparta is breaking the build π¨
greenkeeper opened this issue Β· 2 comments
Version 4.1.0 of isparta was just published.
Branch | Build failing π¨ |
---|---|
Dependency | isparta |
Current Version | 4.0.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
isparta 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 8 commits.
1142f35
chore(release): version 4.1.0
fdcbf45
test: update expected cover to unexpected locations
3763c5f
test: update compiled test files
7d6a4a3
chore(test): rename index spec
840a066
chore(pkg): remove hide-stack-frames-from
912fbee
fix(pkg): force use of istanbul@0.4.4
638ac1e
feat(pkg): update to latest esprima for enabling instrumentation of async/await (#132)
7e89d4e
docs(README): add unmaintained badge
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 π΄
After pinning to 4.0.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Network error. Retried successfully