An in-range update of rollup is breaking the build 🚨
Closed this issue · 1 comments
greenkeeper commented
The devDependency rollup was updated from 1.19.4 to 1.20.0.
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
- ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
Release Notes for v1.20.0
2019-08-21
Features
- Add augmentChunkHash plugin hook to be able to reflect changes in renderChunk in the chunk hash (#2921)
Bug Fixes
- Do not mutate the acorn options object (#3051)
- Make sure the order of emitted chunks always reflects the order in which they were emitted (#3055)
- Do not hang when there are strings containing comment-like syntax in some scenarios (#3069)
Pull Requests
- #2921: Add augmentChunkHash plugin hook (@isidrok)
- #2995: Add info on installing locally to docs (@mesqueeb)
- #3037: Refresh pull request labels (@shellscape)
- #3048: Document ROLLUP_WATCH environment variable (@shellscape)
- #3051: Avoid changes to the original options (.acorn) object (@LongTengDao)
- #3052: Minor refactoring: Remove one try-catch (@KSXGitHub)
- #3053: Refactor to use async-await in more places (@KSXGitHub)
- #3055: Provide consistent chunking via a consistent order of entry modules when emitting chunks (@lukastaegert)
- #3058: Remove acorn-bigint and acorn-dynamic-import from bundle (@LongTengDao)
- #3061: Update to acorn@7 (@lukastaegert)
- #3063: Auto-generate license file (@lukastaegert)
- #3069: Prevent infinite loop when scanning for line-breaks and there are comment-like strings (@lukastaegert)
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 1.19.4 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.