chore(deps): bump graphql-ws from 6.0.6 to 6.2.1

[dependabot]

Bumps graphql-ws from 6.0.6 to 6.2.1.

Release notes

Sourced from graphql-ws's releases.

v6.2.1

Patch Changes

• #660 61731f0 Thanks @​fkaempfer! - Fix typings for WebSocketServer

v6.2.0

Minor Changes

• #682 1e70c1a Thanks @​jwatzman! - Add parse option for custom GraphQL parsing

v6.1.1

Patch Changes

• #680 3fdd82f Thanks @​kkhys! - Disposing of a client event listener twice no longer removes an unrelated listener

  The unsubscribe function returned by client.on spliced at indexOf(listener) without checking for -1, so removing an already-removed listener would splice(-1, 1) and silently drop the most recently registered listener of the same event. This happens in practice without any double-dispose by the user: emits iterate over a copy of the listeners, so a one-shot internal listener that already unlistened itself during a nested emit (e.g. when client.terminate() is called from within a closed/error listener) is re-invoked from the copy and unlistens again, knocking out registered closed/error listeners.

v6.1.0

Minor Changes

• #672 afb7a8a Thanks @​andreisergiu98! - Add support for graphql@17

v6.0.8

Patch Changes

• #667 fc03004 Thanks @​endigma! - Fix the server sending a Complete message after an Error message for subscriptions.

  Previously, when a subscription's async iterable threw an error, the server would send:

  {"id":"1","type":"error","payload":[{"message":"..."}]}
  {"id":"1","type":"complete"}
  

  Per the protocol spec:

  Error: This message terminates the operation and no further messages will be sent.

  Complete (Server → Client): If the server dispatched the Error message relative to the original Subscribe message, no Complete message will be emitted.

  The server now correctly sends only the Error message:

  {"id":"1","type":"error","payload":[{"message":"..."}]}
  

  Clients that correctly follow the spec should be unaffected, as they are expected to ignore messages for operations they consider already completed.

v6.0.7

Patch Changes

• #665 5536292 Thanks @​enisdenjo! - Remove uWebSockets.js from peer dependencies in package.json

  It does not exist on NPM anymore and could lead to weird behavior when installing dependencies with npm. Nothing else changes, using graphql-ws with uWebSockets.js still works.

Changelog

Sourced from graphql-ws's changelog.

6.2.1

Patch Changes

• #660 61731f0 Thanks @​fkaempfer! - Fix typings for WebSocketServer

6.2.0

Minor Changes

• #682 1e70c1a Thanks @​jwatzman! - Add parse option for custom GraphQL parsing

6.1.1

Patch Changes

• #680 3fdd82f Thanks @​kkhys! - Disposing of a client event listener twice no longer removes an unrelated listener

  The unsubscribe function returned by client.on spliced at indexOf(listener) without checking for -1, so removing an already-removed listener would splice(-1, 1) and silently drop the most recently registered listener of the same event. This happens in practice without any double-dispose by the user: emits iterate over a copy of the listeners, so a one-shot internal listener that already unlistened itself during a nested emit (e.g. when client.terminate() is called from within a closed/error listener) is re-invoked from the copy and unlistens again, knocking out registered closed/error listeners.

6.1.0

Minor Changes

• #672 afb7a8a Thanks @​andreisergiu98! - Add support for graphql@17

6.0.8

Patch Changes

• #667 fc03004 Thanks @​endigma! - Fix the server sending a Complete message after an Error message for subscriptions.

  Previously, when a subscription's async iterable threw an error, the server would send:

  {"id":"1","type":"error","payload":[{"message":"..."}]}
  {"id":"1","type":"complete"}
  

  Per the protocol spec:

  Error: This message terminates the operation and no further messages will be sent.

  Complete (Server → Client): If the server dispatched the Error message relative to the original Subscribe message, no Complete message will be emitted.

  The server now correctly sends only the Error message:

  {"id":"1","type":"error","payload":[{"message":"..."}]}
  

... (truncated)

Commits

• 839ca7d Upcoming Release Changes (#684)
• 61731f0 Import type WebSocketServer directly from 'ws' (#660)
• af4f5c9 Upcoming Release Changes (#683)
• 1e70c1a feat(server): Add parse option for custom GraphQL parsing (#682)
• 716eb36 Upcoming Release Changes (#681)
• 3fdd82f fix(client): don't remove an unrelated listener when disposing of an already-...
• ea0d083 chore: no need for registry url
• 0b69b9b Upcoming Release Changes (#679)
• 8bbad60 chore: downgrade uws for node 20
• 3675e0d chore: bump uws
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for graphql-ws since your current version.

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)