[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
graphql-ws (source)	6.1.1 → 6.4.1

---

Release Notes

enisdenjo/graphql-ws (graphql-ws)

v6.4.1

Compare Source

Patch Changes

• #​703 707c38c Thanks @​lprnmns! - Use the jsonMessageReplacer when automatically responding to a ping with a pong, on both the client and the server

v6.4.0

Compare Source

Minor Changes

• #​696 83be052 Thanks @​niukanen1! - Add an isProd option to the ws, uWebSockets.js and @fastify/websocket use-server helpers, matching the existing crossws option. It controls whether internal error messages are masked with Internal server error before reaching the client, defaulting to the NODE_ENV === 'production' check as before. This lets apps running in production keep reporting onConnect error messages to the client by opting out, or mask eagerly in non-production environments.

Patch Changes

• #​700 d8aeda6 Thanks @​kratam! - Fix the client closing an in-use socket when many subscriptions complete at once and a new one subscribes within the lazyCloseTimeout

  Every completing subscription scheduled its own lazy close timeout, but only the last one got cleared on the next connect. The client now keeps a single lazy close timeout and checks for active subscriptions before closing.

• #​702 1e05c8c Thanks @​Meemaw! - Avoid an unhandled rejection when a subscription is disposed before the connection is acknowledged and the socket closes before the subscription releases its connection lock (for example, when the client is disposed while connecting and the WebSocket implementation delivers the close event on a microtask).

v6.3.0

Compare Source

Minor Changes

• #​691 b5f53cd Thanks @​niukanen1! - Add onPing and onPong server callbacks to ServerOptions, similar to onConnect and onDisconnect. The callbacks receive the connection Context as the first argument and the ping/pong payload as the second, allowing apps to log or react to subprotocol-level pings with access to connection state. The automatic pong reply is preserved when using the server-level onPing callback; the low-level websocket onPing listener still disables the automatic reply for full manual control.

Patch Changes

• #​693 c41433e Thanks @​smnbbrv! - fix the client leaking memory per operation on long-living connections

• #​695 93c8ebf Thanks @​zerolxy612! - Allow operation IDs that match properties inherited from Object.prototype.

v6.2.2

Compare Source

Patch Changes

• #​690 1029314 Thanks @​Haasini-kudala! - Support crossws 0.4 by selecting the GraphQL WebSocket subprotocol during the upgrade handshake. Preserve automatic protocol negotiation in the legacy crossws 0.3 Node and uWebSockets adapters.

• #​686 536960e Thanks @​cpruijsen! - Fix the CrossWS adapter ignoring socket closes issued from server.opened

  makeHooks only registered the peer in the clients map after server.opened returned, while send/close no-op'd unless the peer was already in that map. A protocol-mismatch close (and any other close from inside opened) was therefore dropped, the WebSocket stayed open, and no ConnectionAck was ever sent because the message handler was never installed.

v6.2.1

Compare Source

Patch Changes

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

v6.2.0

Compare Source

Minor Changes

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

---

Configuration

📅 Schedule: (in timezone Asia/Shanghai)

• Branch creation
  • "after 2am and before 8am on friday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

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

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: eesast-web@2024.0.0
npm error Found: graphql@17.0.2
npm error node_modules/graphql
npm error   graphql@"17.0.2" from the root project
npm error
npm error Could not resolve dependency:
npm error peer graphql@"^15.0.0 || ^16.0.0" from @apollo/client@3.14.1
npm error node_modules/@apollo/client
npm error   @apollo/client@"3.14.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-10-26T23_08_09_838Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-10-26T23_08_09_838Z-debug-0.log

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request