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

Update feathers-socketio to the latest version 馃殌 #47

Merged
merged 1 commit into from May 10, 2017

Conversation

greenkeeper[bot]
Copy link
Contributor

@greenkeeper greenkeeper bot commented May 10, 2017

Version 2.0.0 of feathers-socketio just got published.

Dependency feathers-socketio
Current Version 1.6.0
Type devDependency

The version 2.0.0 is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of feathers-socketio.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.


Commits

The new version differs by 4 commits0.

  • 1f4cd07 2.0.0
  • 9b6172a Update socket.io-client to the latest version 馃殌 (#76)
  • b8a8b3b fix(package): update socket.io to version 2.0.0 (#75)
  • 661fe44 chore(package): update semistandard to version 11.0.0 (#72)

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 馃尨

@daffl daffl merged commit 8183c71 into master May 10, 2017
@daffl daffl deleted the greenkeeper/feathers-socketio-2.0.0 branch May 10, 2017 15:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant