chore(deps)(deps): bump graphql-ws from 5.16.2 to 6.0.8 in /backend

[dependabot]

Bumps graphql-ws from 5.16.2 to 6.0.8.

Release notes

Sourced from graphql-ws's releases.

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.

v6.0.6

Patch Changes

• #648 1f53bb4 Thanks @​enisdenjo! - Fix building issues causing CJS type definitions referencing ESM modules

v6.0.5

Patch Changes

• #630 fce94fa Thanks @​m1212e! - crossws adapter for compatibility with all supported environments

v6.0.4

Patch Changes

• #625 b4a656d Thanks @​HermanBilous! - Use Math.pow for retry delay calculation

v6.0.3

Patch Changes

• 747c01c Thanks @​enisdenjo! - Drop ExecutionPatchResult and FormattedExecutionPatchResult types

  Neither of the types are officially supported (yet) and the future versions of graphql-js adding support for stream/defer will a different signature for the incremental execution result.

... (truncated)

Changelog

Sourced from graphql-ws's changelog.

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":"..."}]}
  

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

6.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.

6.0.6

Patch Changes

• #648 1f53bb4 Thanks @​enisdenjo! - Fix building issues causing CJS type definitions referencing ESM modules

6.0.5

Patch Changes

• #630 fce94fa Thanks @​m1212e! - crossws adapter for compatibility with all supported environments

6.0.4

Patch Changes

... (truncated)

Commits

• 2cbe0ed Upcoming Release Changes (#668)
• fc03004 fix: do not send Complete after Error for subscriptions (#667)
• 6a31f46 Upcoming Release Changes (#666)
• 5536292 Remove uWebSockets.js from peer dependencies in package.json (#665)
• 0c0eb49 Upcoming Release Changes (#649)
• 1f53bb4 Update pkgroll and patch (#648)
• f54873c docs: access socket from ctx.extra
• 85985ee Upcoming Release Changes (#641)
• bc5dafd ci: permissions on jobs
• 0ed458f ci: delete algolia and use release permissions
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by theguild-bot, 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)

[dependabot]

Assignees

The following users could not be added as assignees: Just-Bamford. Either the username does not exist or it does not have the correct permissions to be added as an assignee.

Labels

The following labels could not be found: dependencies, security. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.