Apollo Router Changelogs


This page contains the changelog for the latest release of Apollo Router.

Go to GitHub to view changelogs for all router releases.

v2.6.1

πŸ› Fixes

_entities Apollo Error Metrics Missing Service Attribute (PR #8153)

The error counting feature introduced in v2.5.0 (PR #7712) caused a bug where _entities errors from subgraph fetches no longer included a service (subgraph or connector) attribute. This incorrectly categorized these errors as originating from the router instead of their actual service in the Apollo Studio UI.

This fix restores the missing service attribute.

By @rregitsky in https://github.com/apollographql/router/pull/8153

Deduplication and WebSocket stream termination (PR #8104)

Fixed a regression introduced in v2.5.0, where WebSocket connections to subgraphs would remain open after all client subscriptions were closed. This could lead to unnecessary resource usage and connections not being properly cleaned up until a new event was received.

Previously, when clients disconnected from subscription streams, the router would correctly close client connections but would leave the underlying WebSocket connection to the subgraph open indefinitely in some cases.

By @bnjjj in https://github.com/apollographql/router/pull/8104

Make the id field optional for WebSocket subscription connection_error messages (Issue #6138)

Fixed a Subscriptions over WebSocket issue where connection_error messages from subgraphs would be swallowed by the router because they incorrectly required an id field. According to the graphql-transport-ws specification (one of two transport specifications we provide support for), connection_error messages only require a payload field, not an id field. The id field in is now optional which will allow the underlying error message to propagate to clients when underlying connection failures occur.

By @jeffutter in https://github.com/apollographql/router/pull/8189

Enable annotations on deployments via Helm Chart (PR #8164)

The Helm chart previously did not allow customization of annotations on the deployment itself (as opposed to the pods within it, which is done with podAnnotations); this can now be done with the deploymentAnnotations value.

By @glasser in https://github.com/apollographql/router/pull/8164

Feedback

Edit on GitHub

Ask Community