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

fix(deps): update dependency graphql-ws to v6.0.8 #159

Merged
renovate merged 1 commits from renovate/graphql-ws-6.x into main 2026-03-26 20:12:29 +00:00
Conversation 0 Commits 1 Files Changed 2
+5 -5
renovate commented 2026-03-26 20:06:44 +00:00
Owner
Copy Link
Copy Source

This PR contains the following updates:

Package Change Age Confidence
graphql-ws (source) 6.0.7 → 6.0.8 age confidence

Release Notes

enisdenjo/graphql-ws (graphql-ws)

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.

Configuration

📅 Schedule: 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 Renovate Bot.

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.0.7` → `6.0.8`](https://renovatebot.com/diffs/npm/graphql-ws/6.0.7/6.0.8) | ![age](https://developer.mend.io/api/mc/badges/age/npm/graphql-ws/6.0.8?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/graphql-ws/6.0.7/6.0.8?slim=true) | --- ### Release Notes <details> <summary>enisdenjo/graphql-ws (graphql-ws)</summary> ### [`v6.0.8`](https://github.com/enisdenjo/graphql-ws/blob/HEAD/CHANGELOG.md#608) [Compare Source](https://github.com/enisdenjo/graphql-ws/compare/v6.0.7...v6.0.8) ##### Patch Changes - [#&#8203;667](https://github.com/enisdenjo/graphql-ws/pull/667) [`fc03004`](https://github.com/enisdenjo/graphql-ws/commit/fc0300468644ea117142bc94adbda5d79181828b) Thanks [@&#8203;endigma](https://github.com/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. </details> --- ### Configuration 📅 **Schedule**: 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 [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My44Ni4wIiwidXBkYXRlZEluVmVyIjoiNDMuODYuMCIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOltdfQ==-->
renovate added 1 commit 2026-03-26 20:06:46 +00:00
fix(deps): update dependency graphql-ws to v6.0.8
schemas-app / build (pull_request) Successful in 3m12s
Details
schemas-app / deploy-prod (pull_request) Has been skipped
Details
1cef67e36a
renovate scheduled this pull request to auto merge when all checks succeed 2026-03-26 20:06:48 +00:00
renovate merged commit bba485dacc into main 2026-03-26 20:12:29 +00:00
renovate deleted branch renovate/graphql-ws-6.x 2026-03-26 20:12:30 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
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#159
Delete Branch "renovate/graphql-ws-6.x"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?