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

Bump socket.io-parser, socket.io and socket.io-client #29

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Nov 10, 2022

Bumps socket.io-parser to 3.4.2 and updates ancestor dependencies socket.io-parser, socket.io and socket.io-client. These dependencies need to be updated together.

Updates socket.io-parser from 3.1.2 to 3.4.2

Release notes

Sourced from socket.io-parser's releases.

3.4.1

Bug Fixes

  • prevent DoS (OOM) via massive packets (#95) (dcb942d)

Links

3.4.0

This release mostly contains a bump of the debug package.

Links

3.3.2

Bug Fixes

  • prevent DoS (OOM) via massive packets (#95) (89197a0)

Links

3.3.1

Links

3.3.0

Bug Fixes

  • remove any reference to the global variable (b47efb2)

Links

3.2.0

Bug fixes

  • properly detect typed arrays (#85)
  • properly handle JSON.stringify errors (#84)

Note

... (truncated)

Changelog

Sourced from socket.io-parser's changelog.

3.4.2 (2022-11-09)

Bug Fixes

  • check the format of the index of each attachment (04d23ce)

4.2.1 (2022-06-27)

Bug Fixes

  • check the format of the index of each attachment (b5d0cb7)

4.0.5 (2022-06-27)

Bug Fixes

  • check the format of the index of each attachment (b559f05)

4.2.0 (2022-04-17)

Features

  • allow the usage of custom replacer and reviver (#112) (b08bc1a)

4.1.2 (2022-02-17)

Bug Fixes

  • allow objects with a null prototype in binary packets (#114) (7f6b262)

4.1.1 (2021-10-14)

4.1.0 (2021-10-11)

... (truncated)

Commits
  • 4b3c191 chore(release): 3.4.2
  • 04d23ce fix: check the format of the index of each attachment
  • 6a59237 test: add Node.js 12 and 14 in the build matrix
  • a8130ce chore: release 3.4.1
  • dcb942d fix: prevent DoS (OOM) via massive packets (#95)
  • a5d0435 test: transpile to es5 with babelify
  • 652402a [chore] Release 3.4.0
  • 9b3572e [chore] Bump debug to version 4.1.0 (#92)
  • de1fd36 [docs] Fix incorrect socket.io-protocol version in Readme (#89)
  • 0de72b9 [chore] Release 3.3.0
  • Additional commits viewable in compare view

Updates socket.io from 2.0.4 to 2.5.0

Release notes

Sourced from socket.io's releases.

2.5.0

⚠️ WARNING ⚠️

The default value of the maxHttpBufferSize option has been decreased from 100 MB to 1 MB, in order to prevent attacks by denial of service.

Security advisory: GHSA-j4f2-536g-r55m

Bug Fixes

  • fix race condition in dynamic namespaces (05e1278)
  • ignore packet received after disconnection (22d4bdf)
  • only set 'connected' to true after middleware execution (226cc16)
  • prevent the socket from joining a room after disconnection (f223178)

Links:

2.4.1

This release reverts the breaking change introduced in 2.4.0 (socketio/socket.io@f78a575).

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):
const io = require("socket.io")(httpServer, {
  allowRequest: (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:

... (truncated)

Changelog

Sourced from socket.io's changelog.

2.5.0 (2022-06-26)

Bug Fixes

  • fix race condition in dynamic namespaces (05e1278)
  • ignore packet received after disconnection (22d4bdf)
  • only set 'connected' to true after middleware execution (226cc16)
  • prevent the socket from joining a room after disconnection (f223178)

4.5.1 (2022-05-17)

Bug Fixes

  • forward the local flag to the adapter when using fetchSockets() (30430f0)
  • typings: add HTTPS server to accepted types (#4351) (9b43c91)

4.5.0 (2022-04-23)

Bug Fixes

  • typings: ensure compatibility with TypeScript 3.x (#4259) (02c87a8)

Features

  • add support for catch-all listeners for outgoing packets (531104d)

This is similar to onAny(), but for outgoing packets.

Syntax:

socket.onAnyOutgoing((event, ...args) => {
  console.log(event);
});
  • broadcast and expect multiple acks (8b20457)

Syntax:

io.timeout(1000).emit("some-event", (err, responses) => {
</tr></table> 

... (truncated)

Commits
  • baa6804 chore(release): 2.5.0
  • f223178 fix: prevent the socket from joining a room after disconnection
  • 226cc16 fix: only set 'connected' to true after middleware execution
  • 05e1278 fix: fix race condition in dynamic namespaces
  • 22d4bdf fix: ignore packet received after disconnection
  • dfded53 chore: update engine.io version to 3.6.0
  • e6b8697 chore(release): 2.4.1
  • a169050 revert: fix(security): do not allow all origins by default
  • 873fdc5 chore(release): 2.4.0
  • f78a575 fix(security): do not allow all origins by default
  • Additional commits viewable in compare view

Updates socket.io-client from 2.0.4 to 2.5.0

Release notes

Sourced from socket.io-client's releases.

2.5.0

Bug Fixes

  • ensure buffered events are sent in order (991eb0b)

Links:

2.4.0

The minor bump is matching the bump of the server, but there is no new feature in this release.

Links:

2.3.1

The debug dependency has been reverted to ~3.1.0, as the newer versions contains ES6 syntax which breaks in IE browsers.

Please note that this only applied to users that bundle the Socket.IO client in their application, with webpack for example, as the "official" bundles (in the dist/ folder) were already transpiled with babel.

For webpack users, you can also take a look at the webpack-remove-debug plugin.

Bug Fixes

  • fix reconnection after opening socket asynchronously (#1253) (050108b)

Links:

  • Milestone: 2.3.1
  • Diff: socketio/socket.io-client@2.3.0...2.3.1
  • Server release: -
  • engine.io-client version: ~3.4.0
  • ws version: ~6.1.0
  • Build size
    • socket.io.js:
      • min: 61.3 KB (- 5.7 KB)
      • min+gzip: 19.7 KB (- 0.8 KB)
    • socket.io.slim.js:
      • min: 52.6 KB (+ 0.4 KB)

... (truncated)

Changelog

Sourced from socket.io-client's changelog.

2.5.0 (2022-06-26)

Bug Fixes

  • ensure buffered events are sent in order (991eb0b)

4.5.1 (2022-05-17)

There were some minor bug fixes on the server side, which mandate a client bump.

4.5.0 (2022-04-23)

Features

  • add details to the disconnect event (b862924)

The "disconnect" event will now include additional details to help debugging if anything has gone wrong.

Example when a payload is over the maxHttpBufferSize value in HTTP long-polling mode:

socket.on("disconnect", (reason, details) => {
  console.log(reason); // "transport error"
// in that case, details is an error object
console.log(details.message); "xhr post error"
console.log(details.description); // 413 (the HTTP status of the response)
// details.context refers to the XMLHttpRequest object
console.log(details.context.status); // 413
console.log(details.context.responseText); // ""
});

  • add support for catch-all listeners for outgoing packets (74e3e60)

This is similar to onAny(), but for outgoing packets.

Syntax:

socket.onAnyOutgoing((event, ...args) => {
  console.log(event);
});
</tr></table> 

... (truncated)

Commits
  • 2b8e318 chore(release): 2.5.0
  • 991eb0b fix: ensure buffered events are sent in order
  • b1d7eef ci: remove Node.js 8 from the test matrix
  • de2ccff chore(release): 2.4.0
  • e9dd12a chore: bump engine.io-client version
  • 7248c1e ci: migrate to GitHub Actions
  • 4631ed6 chore(release): 2.3.1
  • 7f73a28 test: fix tests in IE
  • 67c54b8 chore: bump engine.io-parser and socket.io-parser
  • 15a52ab test: remove arrow function (for now)
  • Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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.

Bumps [socket.io-parser](https://github.com/socketio/socket.io-parser) to 3.4.2 and updates ancestor dependencies [socket.io-parser](https://github.com/socketio/socket.io-parser), [socket.io](https://github.com/socketio/socket.io) and [socket.io-client](https://github.com/socketio/socket.io-client). These dependencies need to be updated together.


Updates `socket.io-parser` from 3.1.2 to 3.4.2
- [Release notes](https://github.com/socketio/socket.io-parser/releases)
- [Changelog](https://github.com/socketio/socket.io-parser/blob/main/CHANGELOG.md)
- [Commits](socketio/socket.io-parser@3.1.2...3.4.2)

Updates `socket.io` from 2.0.4 to 2.5.0
- [Release notes](https://github.com/socketio/socket.io/releases)
- [Changelog](https://github.com/socketio/socket.io/blob/main/CHANGELOG.md)
- [Commits](socketio/socket.io@2.0.4...2.5.0)

Updates `socket.io-client` from 2.0.4 to 2.5.0
- [Release notes](https://github.com/socketio/socket.io-client/releases)
- [Changelog](https://github.com/socketio/socket.io-client/blob/main/CHANGELOG.md)
- [Commits](socketio/socket.io-client@2.0.4...2.5.0)

---
updated-dependencies:
- dependency-name: socket.io-parser
  dependency-type: indirect
- dependency-name: socket.io
  dependency-type: direct:production
- dependency-name: socket.io-client
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Nov 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants