[email protected] breaks build 🚨

[greenkeeperio-bot]

Hello lovely humans,

rollup just published its new version 0.36.4.

State	Failing tests 🚨
Dependency	rollup
New version	0.36.4
Type	devDependency

This version is covered by your current version range and after updating it in your project the build went from success to failure.

As rollup is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project ✨

You rock!

🌴

---

The new version differs by 9 commits .

• fca14db -> v0.36.4
• 3da03c6 Merge pull request #1106 from rollup/fix-977
• 3a89cf7 Merge pull request #1076 from zackschuster/patch-1
• 59f815b Update tests after #1037
• ab3b38f Bundle execution is only dependent on program level call expressions
• e8b44a7 Merge branch 'called-but-unused-import' of github.com:mbostock/rollup into fix-977
• da4fb22 destructure options in Scope constructor
• 82f2149 Add another failing test case.
• b65657f Add failing test case for #977.

See the full diff.

---

This pull request was created by greenkeeper.io.

_{Tired of seeing this sponsor message? ⚡ greenkeeper upgrade}