An in-range update of rollup is breaking the build π¨
Closed this issue Β· 2 comments
Version 0.51.4 of rollup was just published.
Branch | Build failing π¨ |
---|---|
Dependency | rollup |
Current Version | 0.51.3 |
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
- β coverage/coveralls First build on greenkeeper/rollup-0.51.4 at 95.763% Details
- β codecov/project 95.76% remains the same compared to de41617 Details
- β codecov/patch Coverage not affected when comparing de41617...2bec3a5 Details
Commits
The new version differs by 6 commits.
e2fb9f2
0.51.4
36ac0b8
Update changelog
e3f780f
Merge remote-tracking branch 'origin/master'
df0cc03
Merge pull request #1725 from rollup/fix-1710
9fadd5b
* resolve #1711
bc928fc
* Resolve #1710
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 π΄
Version 0.51.5 just got published.
Your tests are still failing with this version. Compare the changes π¨
After pinning to 0.51.3 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.