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

[greenkeeper[bot]]

Version 2.8.4 of cors just got published.

Branch	Build failing 🚨
Dependency	cors
Current Version	2.8.3
Type	dependency

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

cors 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 :muscle:

Status Details

- ❌ **continuous-integration/travis-ci/push** The Travis CI build is in progress [Details](https://travis-ci.org/robototes/robototes-website/builds/253052372?utm_source=github_status&utm_medium=notification) - ❌ **semaphoreci** The build failed on Semaphore. [Details](https://semaphoreci.com/robototes/robototes-website/branches/greenkeeper-cors-2-8-4/builds/1)

---

Commits

The new version differs by 11 commits.

• c6ed038 2.8.4
• d3304ab Work-around Safari bug in default pre-flight response
• 386e82a build: Node.js@8.1
• 5c1ac31 build: Node.js@6.11
• 2f7743e build: support Node.js 8.x
• 6f28adb build: cache node_modules on CI
• 294c750 build: use Travis CI container infrastructure
• b4df28a build: pin Node.js versions to minor
• 70f0d40 build: mocha@3.4.2
• 127d67c build: supertest@3.0.0
• 0fd2ec2 build: should@11.2.1

See the full diff

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]]

After pinning to 2.8.3 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.