An in-range update of rollup is breaking the build π¨
Closed this issue Β· 1 comments
greenkeeper commented
Version 0.51.8 of rollup was just published.
Branch | Build failing π¨ |
---|---|
Dependency | rollup |
Current Version | 0.51.7 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
rollup 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
- β bitHound - Dependencies No failing dependencies. Details
- β bitHound - Code 1 failing file. Details
- β continuous-integration/travis-ci/push The Travis CI build passed Details
- β security/snyk No new issues Details
- β continuous-integration/travis-ci/pr The Travis CI build passed Details
- β coverage/coveralls Coverage remained the same at 93.162% Details
- β codecov/project 93.16% remains the same compared to dcec023 Details
- β codecov/patch Coverage not affected when comparing dcec023...2bddd23 Details
Commits
The new version differs by 8 commits.
ab8d67f
0.51.8
e7fbec6
Update changelog
d6e95ce
Merge pull request #1742 from rollup/update-dependencies
ba85f9c
Update dependencies
1042217
Merge pull request #1740 from rollup/refactor-assignment-handling
945bb9d
Fix typo
5c37051
* Raise maximum path depth again
690510f
Simplify assignment -> reassignment tracking
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 π΄
greenkeeper commented
After pinning to 0.51.7 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.