Skip to content

Upcoming Release Changes#668

Open
theguild-bot wants to merge 1 commit intomasterfrom
changeset-release/master
Open

Upcoming Release Changes#668
theguild-bot wants to merge 1 commit intomasterfrom
changeset-release/master

Conversation

@theguild-bot
Copy link
Collaborator

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.

Releases

graphql-ws@6.0.8

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.

@github-actions
Copy link
Contributor

💻 Website Preview

The latest changes are available as preview in: https://pr-668.graphql-ws.pages.dev

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant