An in-range update of rollup is breaking the build 🚨
greenkeeper opened this issue · comments
The dependency rollup was updated from 1.25.1 to 1.25.2.
This version is covered by your current version range and after updating it in your project the build failed.
rollup is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
Status Details
- ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
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 1.25.1 your tests are passing again. Downgrade this dependency 📌.
- The
dependencyrollup was updated from1.25.2to1.26.0.
Your tests are still failing with this version. Compare changes
Release Notes for v1.26.0
2019-10-27
Features
- Only warn when no output is provided for an IIFE bundle but still produce valid code (#3181)
- Support reexporting namespaces as a binding (#3193)
- Switch from hash.js to crypto for hashing in the Node build for better performance and support for very large assets (#3194)
Bug Fixes
- Correctly handle chunks reexporting the same namespace as two different bindings (#3193)
Pull Requests
- #3181: Remove the need to provide an output name for IIFE bundles (@bterrier)
- #3193: Add support for "export * as name from …" (@lukastaegert)
- #3194: Add support for large assets (> 100 MB) (@SebastianNiemann)
Commits
The new version differs by 5 commits.
53fb6fe1.26.01fad958Update changelog1e1a111Add support for "export * as name from …" (#3193)2f7e064Remove the need to provide an output name for IIFE bundles (#3181)b4c8b43[feat] Adds support for large assets (> 100 MB) (#3194)
See the full diff