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

[greenkeeper]

The devDependency cors was updated from 2.8.4 to 2.8.5.

🚨 View failing branch.

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

cors is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ ci/inspecode/push: Your job is running. (Details).
• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Commits

The new version differs by 52 commits.

• 9158a86 2.8.5
• 01477dc Fix setting "maxAge" option to 0
• cb91054 build: supertest@3.3.0
• c023f4f build: nyc@13.1.0
• 9daa37d build: mocha@5.2.0
• 697ea95 build: restructure Travis CI build steps
• 228b4ca build: Node.js@10.11
• db046b2 build: Node.js@8.12
• f45d533 tests: remove mocha.opts file
• 00d6eec build: use yaml eslint configuration
• 0168ac2 build: Node.js@10.7
• 3af6d30 build: express@4.16.3
• b5bbc28 build: support Node.js 10.x
• 2685e66 docs: add note for rest tools / servers in dynamic origin example
• b42b8b3 docs: improve readability on if-else statement

There are 52 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

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