Connectors improvements: Router 2.3.0 supports Connect spec v0.2, including batch requests, error customization, and direct access to HTTP headers. To use these features: upgrade your Router to 2.3, update your version of Federation to 2.11, and update the @link directives in your subgraphs to https://specs.apollo.dev/connect/v0.2.
See the Connectors changelog for more details.
When logging unknown operations encountered during safe-listing, include information about whether enforcement was skipped. This will help distinguish between truly problematic external operations (where enforcement_skipped is false) and internal operations that are intentionally allowed to bypass safelisting (where enforcement_skipped is true).
By @DaleSeo in https://github.com/apollographql/router/pull/7509
The Router now supports a response_body selector which provides access to the response body in telemetry configurations. This enables more detailed monitoring and logging of response data in the Router.
Example configuration:
telemetry:
instrumentation:
spans:
router:
attributes:
"my_attribute":
response_body: trueBy @Velfi in https://github.com/apollographql/router/pull/7363
Connectors now inspect the content-type header of responses to determine how they should treat the response. This allows more flexibility as prior to this change, all responses were treated as JSON which would lead to errors on non-json responses.
The behavior is as follows:
content-type ends with /json (like application/json) OR +json (like application/vnd.foo+json): content is parsed as JSON.content-type is text/plain: content will be treated as a UTF-8 string. Content can be accessed in selection mapping via $ variable.content-type is any other value: content will be treated as a JSON null.content-type header is provided: content is assumed to be JSON and therefore parsed as JSON.If deserialization fails, an error message of Response deserialization failed with a error code of CONNECTOR_DESERIALIZE will be returned:
"errors": [
{
"message": "Response deserialization failed",
"extensions": {
"code": "CONNECTOR_DESERIALIZE"
}
}
]By @andrewmcgivery in https://github.com/apollographql/router/pull/7380
For errors pertaining to connectors and demand control features, Apollo telemetry will now include the original error message and path as part of the traces sent to GraphOS.
By @timbotnik in https://github.com/apollographql/router/pull/7378
The Router now supports ignoring specific headers when deduplicating requests to subgraphs which provide subscription events. Previously, any differing headers which didn't actually affect the subscription response (e.g., user-agent) would prevent or limit the potential of deduplication.
The introduction of the ignored_headers option allows you to specify headers to ignore during deduplication, enabling you to benefit from subscription deduplication even when requests include headers with unique or varying values that don't affect the subscription's event data.
Configuration example:
subscription:
enabled: true
deduplication:
enabled: true # optional, default: true
ignored_headers: # (optional) List of ignored headers when deduplicating subscriptions
- x-transaction-id
- custom-header-nameBy @bnjjj in https://github.com/apollographql/router/pull/7070
During the development of Router 2.0, the health check endpoint support was converted to be a plugin. Unfortunately, the support for disabling the health check endpoint was lost during the conversion.
This is now fixed and a new unit test ensures that disabling the health check does not result in the creation of a health check endpoint.
By @garypen in https://github.com/apollographql/router/pull/7519
The Router accepts modifications to the client name and version (apollo::telemetry::client_name and apollo::telemetry::client_version), but those modifications were not propagated through the telemetry layers to update spans and traces.
After this change, the modifications from plugins on the router service are propagated through the telemetry layers.
By @carodewig in https://github.com/apollographql/router/pull/7369
The connectors plugin will no longer error when using a variable in a nested input argument. The following example would error prior to this change:
query Query ($query: String){
complexInputType(filters: { inSpace: true, search: $query })
}
By @andrewmcgivery in https://github.com/apollographql/router/pull/7472
http.route (PR #7390)Per the OpenTelemetry spec, the http.route should only include "the matched route, that is, the path template used in the format used by the respective server framework."
Prior to this change, the Router sends the full URI in http.route, which can be high cardinality (ie /graphql?operation=one_of_many_values). The Router will now only include the path (/graphql).
By @carodewig in https://github.com/apollographql/router/pull/7390
A recent change increased the log level of JWT authentication failures from info to error. This reverts that change.
By @carodewig in https://github.com/apollographql/router/pull/7396
When configuring the same header name in both @connect(http: { headers: }) (or @source(http: { headers: })) in SDL and propagate in Router YAML configuration, the request had both headers, even if the value is the same. After this change, Router YAML configuration always wins.
By @andrewmcgivery in https://github.com/apollographql/router/pull/7499
The legacy JavaScript query planner forbids any usage of unknown @link specs in supergraph schemas with either EXECUTION or SECURITY value set for the for argument (aka, the spec's "purpose"). This behavior had not been ported to the native query planner previously. This PR implements the expected behavior in the native query planner.
By @duckki in https://github.com/apollographql/router/pull/7587
@defer fetchThe query planner could add an inline spread conditioned on the Query type in deferred subgraph fetch queries. Such a query would be invalid in the subgraph when the subgraph schema renamed the root query type. This fix removes the root type condition from all subgraph queries, so that they stay valid even when root types were renamed.
By @duckki in https://github.com/apollographql/router/pull/7580
The Router's internal Redis configuration has been improved to increase client resiliency under various failure modes (TCP failures and timeouts, unresponsive sockets, Redis server failures, etc.). It also adds heartbeats (a PING every 10 seconds) to the Redis clients.
By @aembke, @carodewig in https://github.com/apollographql/router/pull/7526
The documentation for standard metric instruments for coprocessors has been updated:
apollo.router.operations.coprocessor.total to apollo.router.operations.coprocessorcoprocessor.succeeded attribute applies to apollo.router.operations.coprocessor only.By @shorgi in https://github.com/apollographql/router/pull/7359
A new section has been added to the demand control documentation to demonstrate how to use Rhai scripts to expose cost estimation data in response headers. This allows clients to see the estimated cost, actual cost, and other demand control metrics directly in HTTP responses, which is useful for debugging and client-side optimization.
By @abernix in https://github.com/apollographql/router/pull/7564
Fetched April 11, 2026