ember-data-model-fragments
ember-data-model-fragments copied to clipboard
Bump socket.io from 2.3.0 to 2.4.1
Bumps socket.io from 2.3.0 to 2.4.1.
Release notes
Sourced from socket.io's releases.
2.4.1
This release reverts the breaking change introduced in
2.4.0
(https://github.com/socketio/socket.io/commit/f78a575f66ab693c3ea96ea88429ddb1a44c86c7).If you are using Socket.IO v2, you should explicitly allow/disallow cross-origin requests:
- without CORS (server and client are served from the same domain):
io.origins((req, callback) => { callback(null, req.headers.origin === undefined); // cross-origin requests will not be allowed });
- with CORS (server and client are served from distinct domains):
io.origins(["http://localhost:3000"]); // for local development io.origins(["https://example.com"]);
In any case, please consider upgrading to Socket.IO v3, where this security issue is now fixed (CORS is disabled by default).
Reverts
- fix(security): do not allow all origins by default (a169050)
Links:
- Diff: https://github.com/socketio/socket.io/compare/2.4.0...2.4.1
- Client release: -
- engine.io version:
~3.5.0
- ws version:
~7.4.2
2.4.0
Related blog post: https://socket.io/blog/socket-io-2-4-0/
Features (from Engine.IO)
Bug Fixes
- security: do not allow all origins by default (f78a575)
- properly overwrite the query sent in the handshake (d33a619)
:warning: BREAKING CHANGE :warning:
Previously, CORS was enabled by default, which meant that a Socket.IO server sent the necessary CORS headers (
Access-Control-Allow-xxx
) to any domain. This will not be the case anymore, and you now have to explicitly enable it.
... (truncated)
Changelog
Sourced from socket.io's changelog.
2.4.1 (2021-01-07)
Reverts
- fix(security): do not allow all origins by default (a169050)
2.4.0 (2021-01-04)
Bug Fixes
Commits
e6b8697
chore(release): 2.4.1a169050
revert: fix(security): do not allow all origins by default873fdc5
chore(release): 2.4.0f78a575
fix(security): do not allow all origins by defaultd33a619
fix: properly overwrite the query sent in the handshake3951a79
chore: bump engine.io version6fa026f
ci: migrate to GitHub Actions- See full diff in compare view
You can trigger a rebase of this PR by commenting @dependabot rebase
.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebase
will rebase this PR -
@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it -
@dependabot merge
will merge this PR after your CI passes on it -
@dependabot squash and merge
will squash and merge this PR after your CI passes on it -
@dependabot cancel merge
will cancel a previously requested merge and block automerging -
@dependabot reopen
will reopen this PR if it is closed -
@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -
@dependabot use these labels
will set the current labels as the default for future PRs for this repo and language -
@dependabot use these reviewers
will set the current reviewers as the default for future PRs for this repo and language -
@dependabot use these assignees
will set the current assignees as the default for future PRs for this repo and language -
@dependabot use this milestone
will set the current milestone as the default for future PRs for this repo and language
You can disable automated security fix PRs for this repo from the Security Alerts page.