An in-range update of rollup is breaking the build 🚨
greenkeeper opened this issue · comments
The devDependency rollup was updated from 1.4.1 to 1.4.2.
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.4.2
2019-03-07
Bug Fixes
- Respect variable identity of exports when hashing (#2741)
- Resolve a situations where a variable was imported twice with the same name (#2737)
Pull Requests
- #2741: Fix hashing when different variable are exported using the same name (@lukastaegert)
- #2737: Fix duplicate imports with conflicting names (@lukastaegert)
Commits
The new version differs by 6 commits.
adaa23e1.4.22d03a67Update changelog858fea4Resolve a situation where different default exports referencing the same (#2737)6903425Update changelogaf41561Fix an issue where the same hash was generated when different variables (#2741)d27c0f6Docs: Fix return type (#2738)
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 1.4.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
- The
devDependencyrollup was updated from1.4.2to1.5.0.
Your tests are still failing with this version. Compare changes
Release Notes for v1.5.0
2019-03-07
Features
- Allow resolving to a different id while marking it as external at the same time (#2734)
Pull Requests
- #2734: Allow resolveId to return an object (@lukastaegert)
Tests now passing