search

Alorel / ngforage

localForage bindings for Angular
https://alorel.github.io/ngforage/
MIT License
111 stars 18 forks source link

build(deps): bump engine.io and socket.io #531

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps engine.io and socket.io. These dependencies needed to be updated together. Updates engine.io from 6.2.1 to 6.5.1

Release notes

Sourced from engine.io's releases.

6.5.1

Bug Fixes

  • prevent crash when accessing TextDecoder (#684) (6dd2bc4)

Credits

Huge thanks to @​iowaguy for helping!

Links

6.5.0

Bug Fixes

  • uws: discard any write to an aborted uWS response (#682) (3144d27)

Features

Support for WebTransport

The Engine.IO server can now use WebTransport as the underlying transport.

WebTransport is a web API that uses the HTTP/3 protocol as a bidirectional transport. It's intended for two-way communications between a web client and an HTTP/3 server.

References:

Until WebTransport support lands in Node.js, you can use the @fails-components/webtransport package:

import { readFileSync } from "fs";
import { createServer } from "https";
import { Server } from "engine.io";
import { Http3Server } from "@fails-components/webtransport";

// WARNING: the total length of the validity period MUST NOT exceed two weeks (https://w3c.github.io/webtransport/#custom-certificate-requirements)
const cert = readFileSync("/path/to/my/cert.pem");
const key = readFileSync("/path/to/my/key.pem");


const httpsServer = createServer({
</tr></table>

... (truncated)

Changelog

Sourced from engine.io's changelog.

6.5.1 (2023-06-27)

Bug Fixes

  • prevent crash when accessing TextDecoder (#684) (6dd2bc4)

Credits

Huge thanks to @​iowaguy for helping!

Dependencies

6.5.0 (2023-06-16)

Bug Fixes

  • uws: discard any write to an aborted uWS response (#682) (3144d27)

Features

Support for WebTransport

The Engine.IO server can now use WebTransport as the underlying transport.

WebTransport is a web API that uses the HTTP/3 protocol as a bidirectional transport. It's intended for two-way communications between a web client and an HTTP/3 server.

References:

Until WebTransport support lands in Node.js, you can use the @fails-components/webtransport package:

import { readFileSync } from "fs";
import { createServer } from "https";
import { Server } from "engine.io";
import { Http3Server } from "@fails-components/webtransport";

// WARNING: the total length of the validity period MUST NOT exceed two weeks (https://w3c.github.io/webtransport/#custom-certificate-requirements)
</tr></table>

... (truncated)

Commits
  • 98915d0 chore(release): 6.5.1
  • 6dd2bc4 fix: prevent crash when accessing TextDecoder (#684)
  • 9608781 chore(deps): bump engine.io from 6.2.1 to 6.4.2 in /examples/latency (#678)
  • 1f640a2 chore(release): 6.5.0
  • 1bfa9cd refactor: adapt to latest uWebSockets.js changes
  • 123b68c feat: add support for WebTransport
  • 3144d27 fix(uws): discard any write to an aborted uWS response (#682)
  • 7bd7775 docs: update the list of CVE
  • 95e2153 chore(release): 6.4.2
  • fc480b4 fix: prevent crash when provided with an invalid query param
  • Additional commits viewable in compare view


Updates socket.io from 4.5.3 to 4.7.1

Release notes

Sourced from socket.io's releases.

4.7.1

The client bundle contains a few fixes regarding the WebTransport support.

Links

4.7.0

Bug Fixes

  • remove the Partial modifier from the socket.data type (#4740) (e5c62ca)

Features

Support for WebTransport

The Socket.IO server can now use WebTransport as the underlying transport.

WebTransport is a web API that uses the HTTP/3 protocol as a bidirectional transport. It's intended for two-way communications between a web client and an HTTP/3 server.

References:

Until WebTransport support lands in Node.js, you can use the @fails-components/webtransport package:

import { readFileSync } from "fs";
import { createServer } from "https";
import { Server } from "socket.io";
import { Http3Server } from "@fails-components/webtransport";

// WARNING: the total length of the validity period MUST NOT exceed two weeks (https://w3c.github.io/webtransport/#custom-certificate-requirements)
const cert = readFileSync("/path/to/my/cert.pem");
const key = readFileSync("/path/to/my/key.pem");


const httpsServer = createServer({
key,
cert
});


httpsServer.listen(3000);


const io = new Server(httpsServer, {
</tr></table>

... (truncated)

Changelog

Sourced from socket.io's changelog.

4.7.1 (2023-06-28)

The client bundle contains a few fixes regarding the WebTransport support.

Dependencies

4.7.0 (2023-06-22)

Bug Fixes

  • remove the Partial modifier from the socket.data type (#4740) (e5c62ca)

Features

Support for WebTransport

The Socket.IO server can now use WebTransport as the underlying transport.

WebTransport is a web API that uses the HTTP/3 protocol as a bidirectional transport. It's intended for two-way communications between a web client and an HTTP/3 server.

References:

Until WebTransport support lands in Node.js, you can use the @fails-components/webtransport package:

import { readFileSync } from "fs";
import { createServer } from "https";
import { Server } from "socket.io";
import { Http3Server } from "@fails-components/webtransport";

// WARNING: the total length of the validity period MUST NOT exceed two weeks (https://w3c.github.io/webtransport/#custom-certificate-requirements)
const cert = readFileSync("/path/to/my/cert.pem");
const key = readFileSync("/path/to/my/key.pem");


const httpsServer = createServer({
key,
cert
});


</tr></table>

... (truncated)

Commits
  • 2f6cc2f chore(release): 4.7.1
  • 00d8ee5 chore(release): 4.7.0
  • 2dd5fa9 ci: add Node.js 20 in the test matrix
  • a5dff0a docs(examples): increase httpd ProxyTimeout value (2)
  • 3035c25 docs(examples): increase httpd ProxyTimeout value
  • 63f181c feat: serve client bundles with CORS headers
  • a250e28 chore: bump engine.io to version 6.5.0
  • e5c62ca fix: remove the Partial modifier from the socket.data type (#4740)
  • 01d3762 docs(changelog): update the version range of the engine.io dependency
  • faf914c chore(release): 4.6.2
  • 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) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/Alorel/ngforage/network/alerts).
coveralls commented 1 year ago

Coverage Status

coverage: 95.05%. remained the same when pulling 27093f411c7a5dbb1f938e76ffc8ada0670058f9 on dependabot/npm_and_yarn/engine.io-and-socket.io-6.5.1 into 2344622abba5b1e0997d4c5291331b214e5ebe35 on master.

Alorel commented 10 months ago

:tada: This PR is included in version 10.1.0 :tada:

The release is available on:

Your semantic-release bot :package::rocket: