An in-range update of rollup is breaking the build 🚨

[greenkeeper]

The devDependency rollup was updated from 1.12.1 to 1.12.2.

🚨 View failing branch.

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

• ❌ ci/gitlab/greenkeeper/rollup-1.12.2: Pipeline failed on GitLab (Details).

---

Release Notes for v1.12.2

2019-05-17

Bug Fixes

• Do not fail when using clearScreen:false in watchMode (#2858)
• Properly resolve star reexports when preserving modules (#2860)

Pull Requests

• #2858: Declare processConfigsErr before use (@humphd)
• #2860: Keep nested exports with preserveModules (@TomCaserta)
• #2864: Cache transitive reexport detection (@lukastaegert)

Commits

The new version differs by 7 commits.

• a4fbc53 1.12.2
• 968cb2a Update changelog
• 72f2e81 Cache transitive reexport detection (#2864)
• 020e87f Update changelog
• 7aaec61 Declare processConfigsErr before use (#2858)
• 6a79bc1 keep nested exports with preserveModules (#2854) (#2863)
• 7e3225f Fix date in changelog

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]

After pinning to 1.12.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.