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 socket.io is breaking the build 🚨 #299

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

An in-range update of socket.io is breaking the build 🚨 #299

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

Comments

@greenkeeper
Copy link

greenkeeper bot commented Nov 28, 2018

The dependency socket.io was updated from 2.1.1 to 2.2.0.

🚨 View failing branch.

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

socket.io 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
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 10 commits.

  • df05b73 [chore] Release 2.2.0
  • b00ae50 [feat] Add cache-control header when serving the client source (#2907)
  • d3c653d [docs] Add Touch Support to the whiteboard example (#3104)
  • a7fbd1a [fix] Throw an error when trying to access the clients of a dynamic namespace (#3355)
  • 190d22b [chore] Bump dependencies
  • 7b8fba7 [test] Update Travis configuration
  • e5f0cea [docs] Use new JavaScript syntax inside the README (#3360)
  • 7e35f90 [docs] fix this scope in the chat example
  • 2dbec77 [chore] Update issue template
  • d97d873 [docs] update README.md (#3309)

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
Author

greenkeeper bot commented Nov 28, 2018

After pinning to 2.1.1 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