redrun@4.1.0 breaks build 🚨

[greenkeeperio-bot]

Hello lovely humans,

redrun just published its new version 4.1.0.

State	Failing tests 🚨
Dependency	redrun
New version	4.1.0
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 redrun 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!

🌴

---

GitHub Release

feature

• (redrun) rm deprecation message
• (redrun) add ability to run scripts with redrun from any directory
• (package) eslint v3.0.0
• (package) add tap-min
• (redrun) add -q, --quiet

---

The new version differs by 7 commits (ahead by 7, behind by 3).

• c067f42 chore(package) v4.1.0
• 3e4087c feature(redrun) rm deprecation message
• 7640170 feature(redrun) add ability to run scripts with redrun from any directory
• a068a1f feature(package) eslint v3.0.0
• 59a3984 chore(package) v4.0.0
• 70f3ab5 feature(package) add tap-min
• c522579 feature(redrun) add -q, --quiet

See the full diff.

---

This pull request was created by greenkeeper.io.

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

[coveralls]

Coverage remained the same at 100.0% when pulling 8c4c00f on greenkeeper-redrun-4.1.0 into 20aec15 on master.