Skip to content

Make the id field on ServerMessage::Error optional - as it can be ret… (copy #8181)#8189

Merged
abernix merged 3 commits intodevfrom
mergify/copy/dev/pr-8181
Sep 3, 2025
Merged

Make the id field on ServerMessage::Error optional - as it can be ret… (copy #8181)#8189
abernix merged 3 commits intodevfrom
mergify/copy/dev/pr-8181

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Sep 3, 2025

This PR FIXES #6138. It brings @jeffutter's #8181 into a context where CI will run and lets me (@abernix) finish the changeset for it.

The websocket-transport-ws spec does not require an id on a CONNECTION_ERROR. This makes that field optional

Todo

  • Changeset
  • Backport and ship as 2.6.1
  • CLA check (@abernix signed off)

Checklist

Complete the checklist (and note appropriate exceptions) before the PR is marked ready-for-review.

  • PR description explains the motivation for the change and relevant context for reviewing
  • PR description links appropriate GitHub/Jira tickets (creating when necessary)
  • Changes are compatible[^1]
  • Performance impact assessed and acceptable
  • Tests added and passing[^4]
    • Unit tests
    • Integration tests
    • Manual tests, as necessary

This is an automatic copy of pull request #8181 done by [Mergify](https://mergify.com).

…urned on INIT which doesn't have an id, and the spec for graphql-transport-ws specifies it as optional.

(cherry picked from commit f564e68)
@apollo-cla
Copy link

@mergify[bot]: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Apollo Contributor License Agreement here: https://contribute.apollographql.com/

@apollo-librarian
Copy link

apollo-librarian bot commented Sep 3, 2025

✅ Docs preview has no changes

The preview was not built because there were no changes.

Build ID: 1219167322286d328210672a
Build Logs: View logs

@github-actions

This comment has been minimized.

@abernix
Copy link
Member

abernix commented Sep 3, 2025

@Mergifyio backport 2.6.1

@mergify
Copy link
Contributor Author

mergify bot commented Sep 3, 2025

backport 2.6.1

❌ No backport have been created

Details
  • Backport to branch 2.6.1 failed

Unable to backport: Mergify can't impersonate a bot from another GitHub App: mergify[bot].

@abernix abernix requested a review from a team as a code owner September 3, 2025 12:09
Co-authored-by: Renée <renee.kooi@apollographql.com>
@abernix abernix enabled auto-merge (squash) September 3, 2025 12:23
@abernix abernix merged commit 6da9cdb into dev Sep 3, 2025
15 checks passed
@abernix abernix deleted the mergify/copy/dev/pr-8181 branch September 3, 2025 15:48
@abernix
Copy link
Member

abernix commented Sep 4, 2025

@Mergifyio backport 2.6.1

@mergify
Copy link
Contributor Author

mergify bot commented Sep 4, 2025

backport 2.6.1

✅ Backports have been created

Details

mergify bot added a commit that referenced this pull request Sep 4, 2025
Copies: #8181
Fixes: #6138
Co-authored-by: Jeffery Utter <jeffery.utter@thescore.com>
Co-authored-by: Jesse Rosenberger <git@jro.cc>
Co-authored-by: Renée <renee.kooi@apollographql.com>
(cherry picked from commit 6da9cdb)
abernix added a commit that referenced this pull request Sep 4, 2025
@abernix abernix mentioned this pull request Sep 8, 2025
@abernix abernix mentioned this pull request Sep 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

WebSocket parsing issue for connection_error (graphql_transport_ws message)

6 participants