-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Misleading release notice? #1112
Comments
I think you are referring to
|
I was confused, I think because the new release note hadn't made it. Can you speak to whether the 1.7x -> 2.x bump is breaking? Do I need to synchronously update the client and server? I couldn't find it in the docs but the semver bump is a bit scary. |
I think it bumped for the double-encoding of unicode change, correct? |
I'll update the release note as soon as possible, but yes, the change @nuclearace is referring to is a breaking one (socketio/engine.io-parser#81). |
The release that went out 10 minutes ago says that it updates the engine-io client to 1.8.4, but the version that was actually released seems to peg to 3.1.0:
"engine.io-client": "~3.1.0"
socket.io-client/package.json
Line 23 in d30914d
Was this intentional?
The text was updated successfully, but these errors were encountered: