unboundsoftware/schemas-app
6
0
Fork 0
Code Issues 1 Pull Requests 3 Actions Packages Projects Releases Activity

fix(deps): update dependency graphql-ws to v6.1.1 #300

Merged
renovate merged 1 commits from renovate/graphql-ws-6.x into main 2026-07-25 17:13:49 +00:00
Conversation 0 Commits 1 Files Changed 2
+5 -5
renovate commented 2026-07-25 17:10:31 +00:00
Owner
Copy Link
Copy Source

This PR contains the following updates:

Package Change Age Confidence
graphql-ws (source) 6.1.0 → 6.1.1 age confidence

Release Notes

enisdenjo/graphql-ws (graphql-ws)

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.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • 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 has been generated by Mend Renovate.

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [graphql-ws](https://the-guild.dev/graphql/ws) ([source](https://github.com/enisdenjo/graphql-ws)) | [`6.1.0` → `6.1.1`](https://renovatebot.com/diffs/npm/graphql-ws/6.1.0/6.1.1) | ![age](https://developer.mend.io/api/mc/badges/age/npm/graphql-ws/6.1.1?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/graphql-ws/6.1.0/6.1.1?slim=true) | --- ### Release Notes <details> <summary>enisdenjo/graphql-ws (graphql-ws)</summary> ### [`v6.1.1`](https://github.com/enisdenjo/graphql-ws/blob/HEAD/CHANGELOG.md#611) [Compare Source](https://github.com/enisdenjo/graphql-ws/compare/v6.1.0...v6.1.1) ##### Patch Changes - [#&#8203;680](https://github.com/enisdenjo/graphql-ws/pull/680) [`3fdd82f`](https://github.com/enisdenjo/graphql-ws/commit/3fdd82fbe064e94ff87eabd3ef8c56ff4901d2f1) Thanks [@&#8203;kkhys](https://github.com/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. </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yNTcuMiIsInVwZGF0ZWRJblZlciI6IjQzLjI1Ny4yIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
renovate added 1 commit 2026-07-25 17:10:33 +00:00
fix(deps): update dependency graphql-ws to v6.1.1
renovate/stability-days Updates have met minimum release age requirement
Details
schemas-app / build (push) Skipped
schemas-app / build (pull_request) Successful in 2m32s
Details
schemas-app / deploy-prod (pull_request) Skipped
Details
48c99eed7d
renovate scheduled this pull request to auto merge when all checks succeed 2026-07-25 17:10:34 +00:00
renovate merged commit 6cd9482fac into main 2026-07-25 17:13:49 +00:00
renovate deleted branch renovate/graphql-ws-6.x 2026-07-25 17:13:51 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
acctest (Shiny Acctest) argoyle (Joakim Olsson) buildtools (Buildtools) kubernetes (Kubernetes) releaser (Unbound Releaser) renovate (Renovate Bot)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: unboundsoftware/schemas-app#300