Bump engine.io and socket.io

dependabot[bot] commented 1 year ago

Bumps engine.io and socket.io. These dependencies needed to be updated together. Updates engine.io from 3.3.2 to 3.6.0

Release notes

Sourced from engine.io's releases.

3.6.0

Bug Fixes

add extension in the package.json main entry (#608) (3ad0567)

do not reset the ping timer after upgrade (1f5d469)

Features

decrease the default value of maxHttpBufferSize (58e274c)

This change reduces the default value from 100 mb to a more sane 1 mb.

This helps protect the server against denial of service attacks by malicious clients sending huge amounts of data.

See also: https://github.com/advisories/GHSA-j4f2-536g-r55m

increase the default value of pingTimeout (f55a79a)

Links

Diff: https://github.com/socketio/engine.io/compare/3.5.0...3.6.0

Client release: -

ws version: ~7.4.2

3.5.0

Features

add support for all cookie options (19cc582)

disable perMessageDeflate by default (5ad2736)

Links

Diff: https://github.com/socketio/engine.io/compare/3.4.2...3.5.0

Client release: 3.5.0

ws version: ~7.4.2

3.4.2

Bug Fixes

remove explicit require of uws (85e544a)

Links

Diff: 3.4.1...3.4.2

Client release: -

... (truncated)

Changelog

Sourced from engine.io's changelog.

3.6.0 (2022-06-06)

Bug Fixes

add extension in the package.json main entry (#608) (3ad0567)

do not reset the ping timer after upgrade (1f5d469), closes socketio/socket.io-client-swift#1309

Features

decrease the default value of maxHttpBufferSize (58e274c)

This change reduces the default value from 100 mb to a more sane 1 mb.

This helps protect the server against denial of service attacks by malicious clients sending huge amounts of data.

See also: https://github.com/advisories/GHSA-j4f2-536g-r55m

increase the default value of pingTimeout (f55a79a)

6.2.0 (2022-04-17)

Features

add the "maxPayload" field in the handshake details (088dcb4)

So that clients in HTTP long-polling can decide how many packets they have to send to stay under the maxHttpBufferSize value.

This is a backward compatible change which should not mandate a new major revision of the protocol (we stay in v4), as we only add a field in the JSON-encoded handshake data:
0{"sid":"lv_VI97HAXpY6yYWAAAC","upgrades":["websocket"],"pingInterval":25000,"pingTimeout":5000,"maxPayload":1000000}
6.1.3 (2022-02-23)

Bug Fixes

typings: allow CorsOptionsDelegate as cors options (#641) (a463d26)

uws: properly handle chunked content (#642) (3367440)

... (truncated)

Commits

f62f265 chore(release): 3.6.0
f55a79a feat: increase the default value of pingTimeout
1f5d469 fix: do not reset the ping timer after upgrade
3ad0567 fix: add extension in the package.json main entry (#608)
58e274c feat: decrease the default value of maxHttpBufferSize
b9dee7b chore(release): 3.5.0
19cc582 feat: add support for all cookie options
5ad2736 feat: disable perMessageDeflate by default
f632269 chore: bump ws version
ddb80a2 ci: migrate to GitHub Actions
Additional commits viewable in compare view

Updates socket.io from 2.2.0 to 2.5.0

Release notes

Sourced from socket.io's releases.

2.5.0

:warning: WARNING :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: https://github.com/advisories/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:

Diff: https://github.com/socketio/socket.io/compare/2.4.1...2.5.0

Client release: 2.5.0

engine.io version: ~3.6.0 (diff)

ws version: ~7.4.2

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):
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)

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

security: do not allow all origins by default (f78a575)

properly overwrite the query sent in the handshake (d33a619)

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

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](https://github.com/planetarium/libplanet-explorer-frontend/network/alerts).

cloudflare-pages[bot] commented 1 year ago

Deploying with Cloudflare Pages

Latest commit:	`0df4c69`
Status:	✅ Deploy successful!
Preview URL:	https://53150f8f.libplanet-explorer.pages.dev
Branch Preview URL:	https://dependabot-npm-and-yarn-engi.libplanet-explorer.pages.dev

View logs

pull-request-quantifier-deprecated[bot] commented 1 year ago

This PR has 0 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

Quantification details

``` Label : No Changes Size : +0 -0 Percentile : 0% Total files changed: 1 Change summary by file extension: .json : +0 -0 ``` > Change counts above are quantified counts, based on the [PullRequestQuantifier customizations](https://github.com/microsoft/PullRequestQuantifier/blob/main/docs/prquantifier-yaml.md).

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a balance between between PR complexity and PR review overhead. PRs within the optimal size (typical small, or medium sized PRs) mean: - Fast and predictable releases to production: - Optimal size changes are more likely to be reviewed faster with fewer iterations. - Similarity in low PR complexity drives similar review times. - Review quality is likely higher as complexity is lower: - Bugs are more likely to be detected. - Code inconsistencies are more likely to be detected. - Knowledge sharing is improved within the participants: - Small portions can be assimilated better. - Better engineering practices are exercised: - Solving big problems by dividing them in well contained, smaller problems. - Exercising separation of concerns within the code changes. #### What can I do to optimize my changes - Use the PullRequestQuantifier to quantify your PR accurately - Create a context profile for your repo using the [context generator](https://github.com/microsoft/PullRequestQuantifier/releases) - Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the `Excluded` section from your `prquantifier.yaml` context profile. - Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your `prquantifier.yaml` context profile. - Only use the labels that matter to you, [see context specification](./docs/prquantifier-yaml.md) to customize your `prquantifier.yaml` context profile. - Change your engineering behaviors - For PRs that fall outside of the desired spectrum, review the details and check if: - Your PR could be split in smaller, self-contained PRs instead - Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR). #### How to interpret the change counts in git diff output - One line was added: `+1 -0` - One line was deleted: `+0 -1` - One line was modified: `+1 -1` (git diff doesn't know about modified, it will interpret that line like one addition plus one deletion) - Change percentiles: Change characteristics (addition, deletion, modification) of this PR in relation to all other PRs within the repository.

Was this comment helpful? :thumbsup: :ok_hand: :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.

CLAassistant commented 1 year ago

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

dependabot[bot] commented 1 year ago

OK, I won't notify you again about this release, but will get in touch when a new version is available.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

planetarium / libplanet-explorer-frontend

Bump engine.io and socket.io #166

3.6.0

Bug Fixes

Features

Links

3.5.0

Features

Links

3.4.2

Bug Fixes

Links

3.6.0 (2022-06-06)

Bug Fixes

Features

6.2.0 (2022-04-17)

Features

6.1.3 (2022-02-23)

Bug Fixes

2.5.0

Bug Fixes

Links:

2.4.1

Reverts

Links:

2.5.0 (2022-06-26)

Bug Fixes

2.4.1 (2021-01-07)

Reverts

2.4.0 (2021-01-04)

Bug Fixes

Deploying with Cloudflare Pages