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

[greenkeeper[bot]]

Version 6.0.3 of now just got published.

Branch	Build failing 🚨
Dependency	now
Current Version	6.0.2
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As now 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 :muscle:

Status Details

- ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/bracketclub/api/builds/234932045?utm_source=github_status&utm_medium=notification)

---

Release Notes

6.0.3

Patches

• Added now CLI proxy: #569
• Explain why we're shipping the bundled CLI: c9dabd9
• Build inside a single directory: f92e556
• Sweetened a heading: 9654b36
• Always download the specified version: 672a161
• Prepared for the npm release: bfb83d7

Not sure how things should work exactly?

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your Greenkeeper Bot :palm_tree:

[greenkeeper[bot]]

Version 6.0.4 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Release Notes

6.0.4

Patches

• Only include the files that are needed: 5536960
• Read package.json on runtime when downloading: fe0c4a3

Commits

The new version differs by 4 commits.

• 3c8f8a0 Upload binaries to slack after deploying
• 15bed6b 6.0.4
• fe0c4a3 Read package.json on runtime when downloading
• 5536960 Only include the files that are needed

See the full diff