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

[Snyk] Upgrade socket.io-client from 2.2.0 to 2.3.0 #132

Merged
merged 1 commit into from
Mar 14, 2020

Conversation

snyk-bot
Copy link
Contributor

Snyk has created this PR to upgrade socket.io-client from 2.2.0 to 2.3.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
  • The recommended version is 1 version ahead of your current version.
  • The recommended version was released 6 months ago, on 2019-09-20.
Release notes
Package name: socket.io-client from socket.io-client GitHub release notes
Commit messages
Package name: socket.io-client
  • 661f1e7 [chore] Release 2.3.0
  • 71d7b79 [chore] Bump engine.io-client to version 3.4.0
  • 8b4a539 [docs] Add CDN link (#1318)
  • 40cf185 [ci] use Node.js 10 for compatibility with Gulp v3

Compare


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@coveralls
Copy link

coveralls commented Mar 14, 2020

Coverage Status

Coverage remained the same at 82.101% when pulling 403fa50 on snyk-upgrade-dde9f0564b910b5ec8280645e7fc4a88 into 1e12b5d on master.

@jupe jupe merged commit abd2689 into master Mar 14, 2020
@jupe jupe deleted the snyk-upgrade-dde9f0564b910b5ec8280645e7fc4a88 branch March 14, 2020 07:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants