once@1.4.0 breaks build 🚨

[greenkeeperio-bot]

Hello lovely humans,

once just published its new version 1.4.0.

State	Failing tests 🚨
Dependency	once
New version	1.4.0
Type	dependency

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

As once is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very 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 3 commits .

• 0e614d9 v1.4.0
• 733b990 once.strict added
• 9e68062 update tap

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 85.047% when pulling e3950d5 on greenkeeper-once-1.4.0 into 2d861e0 on master.

[tunnckoCore]

Damn... that strategy to add standard to travis.yml was totally hell wrong. Must update all repos ASAP!