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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

An in-range update of socket.io-client is breaking the build 馃毃 #588

Closed
greenkeeper bot opened this Issue Oct 22, 2017 · 2 comments

Comments

Projects
None yet
1 participant
@greenkeeper
Copy link
Contributor

greenkeeper bot commented Oct 22, 2017

Version 2.0.4 of socket.io-client was just published.

Branch Build failing 馃毃
Dependency socket.io-client
Current Version 2.0.3
Type devDependency

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

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

Commits

The new version differs by 4 commits.

  • ebb0596 [chore] Release 2.0.4
  • 57cee21 [test] Remove IE6 and IE7 tests (#1164)
  • c58ecfc [docs] Add code examples for registered events (#1139)
  • e9ebe36 [docs] Add an example with ES6 import in the README (#1138)

See the full diff

FAQ and help

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


Your Greenkeeper Bot 馃尨

@greenkeeper greenkeeper bot added the greenkeeper label Oct 22, 2017

@greenkeeper

This comment has been minimized.

Copy link
Contributor Author

greenkeeper bot commented Oct 22, 2017

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

@daffl

This comment has been minimized.

Copy link
Member

daffl commented Oct 24, 2017

Looks like this is fixed now.

@daffl daffl closed this Oct 24, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can鈥檛 perform that action at this time.