You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix fleet-awareness telemetry exporting metrics to the bare usage-reporting endpoint instead of the OTLP /v1/metrics route (#3465)
The opt-out anonymous telemetry pipeline introduced in #3289 configured the OTLP metric exporter with a bare https://usage-reporting.api.apollographql.com URL. Because the URL is supplied programmatically (rather than via OTEL_EXPORTER_OTLP_ENDPOINT), the @opentelemetry/exporter-metrics-otlp-http package does not append the /v1/metrics signal path automatically, so every export POSTed to / instead of /v1/metrics. The exporter now targets the full OTLP metrics route.
Filter cloud resource detection to only the anonymous data we process (#3450)
The opt-out telemetry introduced in #3289 ran OpenTelemetry cloud resource detectors (AWS, GCP, Azure, Alibaba Cloud) whose attributes could include infrastructure-identifying values such as account IDs, instance IDs, ARNs, hostnames, function names, and log group/stream names. These attributes are now stripped before export, retaining only the non-identifying cloud.provider and cloud.platform attributes that Apollo processes on the ingestion side.
#17de906c3 Thanks @marklai1998! - Restore Node.js 22 support. engines.node was set to >=24.0.0 during the graphql-js rewrite without a documented Node 24 runtime requirement, which silently dropped the current Node 22 LTS. CI now tests Node 22 alongside 24 and latest.
This release is a generic reimplementation of @apollo/subgraph
that can be used with any graphql-js compatible subgraphs. Unless
otherwise noted, behavior is intended to stay compatible with the
previous implementation.
Changed
Use graphql-js functionality over custom logic. All logic is now
re-implemented using graphql-js functionality. @apollo/federation-internals is no
longer a dependency.
printSubgraphSchema now prints the complete schema, federation
directives, types, and root fields included. NOTE: It is just a thin wrapper around @graphql-tools/utils's printSchemaWithDirectives.
Removed
LegacySchemaModule input shape.buildSubgraphSchema no longer accepts
Apollo Server's old { typeDefs, resolvers } object shape. Pass an array of { typeDefs, resolvers } modules (or a bare DocumentNode) instead:
#215915cf592 Thanks @ingvaldlorentzen! - Fixed already-published version detection with npm 12, which always wraps successful npm info --json output in an array. The unwrapped output made changeset publish treat every package as unpublished and fail attempting to republish existing versions.
#83672262087 Thanks @ardatan! - Preserve multiple applications of the same directive when extending a type even if the repeatable directive definition is not present in the merge inputs.
#83945523c4b Thanks @bengry! - Write the synthesized default operation types back onto the schema definition node, so merging a schema extension that has no operation block (federation SDL, for example) still produces a query root on graphql@17.
#8349 7fe0319
Thanks @aarne! - Pass the collected directive definitions to mergeSchemaDefs so repeatable directives on schema definitions and extend schema extensions
(e.g. a repeatable @link) are kept as separate instances instead of being collapsed and having
their arguments merged.
#8346 2273c21
Thanks @ardatan! - This release adds GraphQL v17 support and aligns
the existing executor implementation with the latest GraphQL v17 API changes. The following
changes are included:
getAsyncHelpers is now available on GraphQLResolveInfo. Its track method is used whenever waitUntil is available, as in Yoga's Explicit Resource Management
getAbortSignal is now available on GraphQLResolveInfo, matching behavior that was already
available in this executor implementation, as in Yoga's Execution Cancellation
GraphQLResolveInfo automatically aligns variableValues according to the GraphQL version for
better compatibility. In GraphQL v17 and above, variableValues follows the wrapped shape
({ coerced, sources }) expected by GraphQL APIs. In GraphQL v16 and below, variableValues
remains a flat map as in previous versions.
If your custom scalar resolvers define __serialize and __parseValue, they are automatically
mapped to coerceOutputValue and coerceInputValue in GraphQL v17.
BREAKING: @graphql-tools/executor's getVariableValues now returns { variableValues }
on success, where variableValues is a VariableValues object ({ coerced, sources }). On
failure, it returns { errors }.
BREAKING: collectFields, shouldIncludeNode, getDeferValues, and collectSubFields now
need a VariableValues object instead of Record<string, any> for the variableValues
argument.
visitResult now internally normalizes ExecutionRequest.variables into a VariableValues-compatible shape ({ coerced, sources }) before traversing selections.
Preserves GraphQL 16 compatibility while upgrading to @graphql-tools/utils v12, @graphql-tools/executor v2, and the compatible @graphql-tools/schema and @graphql-tools/merge releases. Consumers now receive consistent resolver and execution request types without conflicts between different GraphQL Tools versions.
Stitched and delegated operations handle the new executor variable result shape correctly, including variables used by directives. Resolver execution also supports the executor's cancellation and asynchronous work helpers while remaining compatible with the GraphQL 16 GraphQLResolveInfo API.
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.14.0→2.14.42.14.3→2.15.17.29.6→7.29.77.29.0→7.29.77.29.5→7.29.72.31.0→2.31.13.2.0→3.2.19.2.2→9.2.47.0.35→7.0.3710.0.38→10.1.111.1.21→11.2.03.2.2→3.3.024.0.4→24.0.522.19.18→22.20.47.7.1→7.8.07.2.0→7.2.18.59.2→8.70.18.71.08.59.2→8.70.18.71.0v1.8.0→v1.9.09.2.1→9.2.4v4.0.1→v4.0.34.4.4→4.4.529.15.2→29.16.616.14.0→16.14.216.14.0→16.14.29.1.0→9.2.2^0.10.0→^0.11.02.12.6→2.12.730.4.1→30.5.26.12.1→6.38.03.2.0→3.2.1v3.0.4→v3.0.52.8.4→2.15.06.0.1→6.2.011.19.0→11.20.03.8.3→3.9.9v1.72.0→v1.77.0v1.34.0→v1.36.0v3.0.3→v3.0.57.2.2→7.3.029.4.9→29.4.149.5.7→9.6.25.106.2→5.111.18.21.0→8.21.38.22.04.14.1→4.18.1Release Notes
apollographql/federation (@apollo/gateway)
v2.14.4Compare Source
Patch Changes
Fix fleet-awareness telemetry exporting metrics to the bare usage-reporting endpoint instead of the OTLP
/v1/metricsroute (#3465)The opt-out anonymous telemetry pipeline introduced in #3289 configured the OTLP metric exporter with a bare
https://usage-reporting.api.apollographql.comURL. Because the URL is supplied programmatically (rather than viaOTEL_EXPORTER_OTLP_ENDPOINT), the@opentelemetry/exporter-metrics-otlp-httppackage does not append the/v1/metricssignal path automatically, so every export POSTed to/instead of/v1/metrics. The exporter now targets the full OTLP metrics route.Updated dependencies []:
v2.14.3Compare Source
Patch Changes
7c0a8ba4cf061cf0e2a6537803ed828c36234bed]:v2.14.2Compare Source
Patch Changes
Filter cloud resource detection to only the anonymous data we process (#3450)
The opt-out telemetry introduced in #3289 ran OpenTelemetry cloud resource detectors (AWS, GCP, Azure, Alibaba Cloud) whose attributes could include infrastructure-identifying values such as account IDs, instance IDs, ARNs, hostnames, function names, and log group/stream names. These attributes are now stripped before export, retaining only the non-identifying
cloud.providerandcloud.platformattributes that Apollo processes on the ingestion side.Updated dependencies []:
v2.14.1Compare Source
Patch Changes
Pass instrumentation scope version as a separate argument when creating the OpenTelemetry meter for telemetry. Fixes #3436. (#3439)
Updated dependencies [
278eb0fc2bc0ef13ba371407df04cfe50fa2887d,8bb88f9c7b90addd5ef29f9e4a3f9c027e6cf690,621568719382df6592749168893e0e533a648ba5]:apollographql/subgraph-js (@apollo/subgraph)
v2.15.1Compare Source
Patch Changes
de906c3Thanks @marklai1998! - Restore Node.js 22 support.engines.nodewas set to>=24.0.0during the graphql-js rewrite without a documented Node 24 runtime requirement, which silently dropped the current Node 22 LTS. CI now tests Node 22 alongside 24 and latest.v2.15.0Compare Source
This release is a generic reimplementation of
@apollo/subgraphthat can be used with any
graphql-jscompatible subgraphs. Unlessotherwise noted, behavior is intended to stay compatible with the
previous implementation.
Changed
graphql-jsfunctionality over custom logic. All logic is nowre-implemented using
graphql-jsfunctionality.@apollo/federation-internalsis nolonger a dependency.
printSubgraphSchemanow prints the complete schema, federationdirectives, types, and root fields included. NOTE: It is just a thin wrapper around
@graphql-tools/utils'sprintSchemaWithDirectives.Removed
LegacySchemaModuleinput shape.buildSubgraphSchemano longer acceptsApollo Server's old
{ typeDefs, resolvers }object shape. Pass an array of{ typeDefs, resolvers }modules (or a bareDocumentNode) instead:v2.14.4Compare Source
babel/babel (@babel/core)
v7.29.7Compare Source
v7.29.7 (2026-05-25)
Re-release all packages with npm provenance attestations
changesets/changesets (@changesets/cli)
v2.31.1Compare Source
Patch Changes
15cf592Thanks @ingvaldlorentzen! - Fixed already-published version detection with npm 12, which always wraps successfulnpm info --jsonoutput in an array. The unwrapped output madechangeset publishtreat every package as unpublished and fail attempting to republish existing versions.eslint-community/eslint-plugin-eslint-comments (@eslint-community/eslint-plugin-eslint-comments)
v3.2.1Compare Source
Bug Fixes
ardatan/graphql-tools (@graphql-tools/merge)
v9.2.4Compare Source
Patch Changes
#8367
2262087Thanks @ardatan! - Preserve multiple applications of the same directive when extending a type even if the repeatable directive definition is not present in the merge inputs.#8394
5523c4bThanks @bengry! - Write the synthesized default operation types back onto the schema definition node, so merging aschemaextension that has no operation block (federation SDL, for example) still produces a query root ongraphql@17.Updated dependencies [
60db079,57e316d,1c1c5a0,1c1c5a0,0b9529f]:v9.2.3Compare Source
Patch Changes
#8349
7fe0319Thanks @aarne! - Pass the collected directive definitions to
mergeSchemaDefsso repeatable directives onschemadefinitions andextend schemaextensions(e.g. a repeatable
@link) are kept as separate instances instead of being collapsed and havingtheir arguments merged.
Updated dependencies
[
2273c21]:ardatan/graphql-tools (@graphql-tools/resolvers-composition)
v7.0.37Compare Source
Patch Changes
60db079,57e316d,1c1c5a0,1c1c5a0,0b9529f]:v7.0.36Compare Source
Patch Changes
[
2273c21]:ardatan/graphql-tools (@graphql-tools/schema)
v10.1.1Compare Source
Patch Changes
2262087,5523c4b,60db079,57e316d,1c1c5a0,1c1c5a0,0b9529f]:v10.1.0Compare Source
Minor Changes
#8346
2273c21Thanks @ardatan! - This release adds GraphQL v17 support and aligns
the existing executor implementation with the latest GraphQL v17 API changes. The following
changes are included:
getAsyncHelpersis now available onGraphQLResolveInfo. Itstrackmethod is used wheneverwaitUntilis available, as in Yoga'sExplicit Resource Management
getAbortSignalis now available onGraphQLResolveInfo, matching behavior that was alreadyavailable in this executor implementation, as in Yoga's
Execution Cancellation
GraphQLResolveInfoautomatically alignsvariableValuesaccording to the GraphQL version forbetter compatibility. In GraphQL v17 and above,
variableValuesfollows the wrapped shape(
{ coerced, sources }) expected by GraphQL APIs. In GraphQL v16 and below,variableValuesremains a flat map as in previous versions.
__serializeand__parseValue, they are automaticallymapped to
coerceOutputValueandcoerceInputValuein GraphQL v17.@graphql-tools/executor'sgetVariableValuesnow returns{ variableValues }on success, where
variableValuesis aVariableValuesobject ({ coerced, sources }). Onfailure, it returns
{ errors }.collectFields,shouldIncludeNode,getDeferValues, andcollectSubFieldsnowneed a
VariableValuesobject instead ofRecord<string, any>for thevariableValuesargument.
visitResultnow internally normalizesExecutionRequest.variablesinto aVariableValues-compatible shape ({ coerced, sources }) before traversing selections.Patch Changes
[
2273c21,7fe0319]:graphql-hive/gateway (@graphql-tools/wrap)
v11.2.0Compare Source
Minor Changes
#2604
ee4cc07Thanks @enisdenjo! - Support GraphQL 16 with @graphql-tools/utils v12Preserves GraphQL 16 compatibility while upgrading to
@graphql-tools/utilsv12,@graphql-tools/executorv2, and the compatible@graphql-tools/schemaand@graphql-tools/mergereleases. Consumers now receive consistent resolver and execution request types without conflicts between different GraphQL Tools versions.Stitched and delegated operations handle the new executor variable result shape correctly, including variables used by directives. Resolver execution also supports the executor's cancellation and asynchronous work helpers while remaining compatible with the GraphQL 16
GraphQLResolveInfoAPI.Patch Changes
#2604
ee4cc07Thanks @enisdenjo! - dependencies updates:@graphql-tools/schema@^10.1.1↗︎ (from^10.0.29, independencies)@graphql-tools/utils@^12.0.1↗︎ (from^11.0.0, independencies)Updated dependencies [
ee4cc07,ee4cc07]:v11.1.24Compare Source
v11.1.23Compare Source
Patch Changes
eb6569b]:v11.1.22Compare Source
Patch Changes
af2cccb]:neo4j/cypher-builder (@neo4j/cypher-builder)
v3.3.0Compare Source
Minor Changes
#865
4c1051dThanks @angrykoala! - Add support forNEXTclause using the methodnext()tsconfig/bases (@tsconfig/node24)
v24.0.5Compare Source
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v8.70.1Compare Source
🩹 Fixes
await(#12716)❤️ Thank You
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.70.0Compare Source
🚀 Features
🩹 Fixes
❤️ Thank You
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.69.0Compare Source
🚀 Features
🩹 Fixes
❤️ Thank You
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.68.0Compare Source
🚀 Features
🩹 Fixes
ignoreVoid: falseresults in false negative in ArrowFunctionExpression (#12646)❤️ Thank You
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.67.0Compare Source
This was a version bump only for eslint-plugin to align it with other projects, there were no code changes.
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.66.0Compare Source
🩹 Fixes
❤️ Thank You
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.65.0Compare Source
🚀 Features
🩹 Fixes
❤️ Thank You
See GitHub Releases for more information.
You can read about our versioning strategy and releases on our website.
v8.64.0Compare Source
🚀 Features
using/await usingdeclarations and deprecate the rule (#12500)🩹 Fixes
❤️ Thank You
See GitHub Releases for more information.
You can read about our [versioning strategy](https://typescript-eslint.io/users/
Configuration
📅 Schedule: (in timezone Europe/London)
* 0-4 1,15 * *)🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.