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

[greenkeeper]

The devDependency rollup was updated from 1.7.0 to 1.7.1.

🚨 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

• ✅ coverage/coveralls: First build on greenkeeper/all/rollup-1.7.1 at 87.413% (Details).
• ❌ build_and_test: * build_and_test - Failed

---

Release Notes for v1.7.1

2019-03-24

Bug Fixes

• Prevent invalid code when exporting several hundred identifiers from a chunk (#2768)
• Do not wrongly deconflict labels (#2776)

Pull Requests

• #2768: Sanitize shortened internal export names (@lukastaegert)
• #2769: Update dependencies and fix security issue (@lukastaegert)
• #2776: Do not treat break labels as identifiers (@lukastaegert)

Commits

The new version differs by 7 commits.

• 7c4ceca 1.7.1
• 034034f Update changelog
• 75b41e2 Do not treat break labels as identifiers (#2776)
• 61dcba8 Update changelog
• 9cbb73e Sanitize shortened internal export names (#2768)
• dec4d83 Update changelog
• 429942e Update dependencies and fix security issues (#2769)

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.7.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

[greenkeeper]

• The devDependency rollup was updated from 1.7.1 to 1.7.2.

Your tests are still failing with this version. Compare changes