fix(deps): update dependency graphql-ws to v6.2.0

[svc-secops]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
graphql-ws (source)	6.0.6 → 6.2.0

---

Release Notes

enisdenjo/graphql-ws (graphql-ws)

v6.2.0

Compare Source

Minor Changes

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

v6.1.1

Compare Source

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

Compare Source

Minor Changes

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

v6.0.8

Compare Source

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

Compare Source

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.

---

Configuration

📅 Schedule: (in timezone Etc/UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • "after 8am and before 4pm on tuesday"

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

This PR has been generated by Renovate Bot.