Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
greenkeeper bot opened this issue Nov 4, 2018 · 1 comment
Open

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

greenkeeper bot opened this issue Nov 4, 2018 · 1 comment

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Nov 4, 2018

The dependency 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 direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ci/circleci: Your tests failed on CircleCI (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
Copy link
Contributor Author

greenkeeper bot commented Nov 4, 2018

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants