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:
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) |  |  |
---
### 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
- [#​667](https://github.com/enisdenjo/graphql-ws/pull/667) [`fc03004`](https://github.com/enisdenjo/graphql-ws/commit/fc0300468644ea117142bc94adbda5d79181828b) Thanks [@​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==-->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This PR contains the following updates:
6.0.7→6.0.8Release Notes
enisdenjo/graphql-ws (graphql-ws)
v6.0.8Compare Source
Patch Changes
#667
fc03004Thanks @endigma! - Fix the server sending aCompletemessage after anErrormessage for subscriptions.Previously, when a subscription's async iterable threw an error, the server would send:
Per the protocol spec:
The server now correctly sends only the
Errormessage: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.
This PR has been generated by Renovate Bot.