fix(deps): update apollo graphql packages #11811
Merged
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.2.3
->2.4.8
4.7.4
->4.7.5
Release Notes
apollographql/federation (@apollo/gateway)
v2.4.8
Compare Source
Patch Changes
62e0d254
,1293034c
,7f1ef73e
,2a97f372
]:v2.4.7
Compare Source
Patch Changes
planning performance), to fix a possibly raised assertion error (with a message of form like
Cannot add selection of field X to selection set of parent type Y
), and to fix a rare issue where an interface or union field was not beingqueried for all the types it should be.
2d44f346
]:v2.4.6
Compare Source
Patch Changes
5cd17e69
,8ca107ac
,e136ad87
]:v2.4.5
Compare Source
Patch Changes
Supersedes v2.4.4 due to a publishing error with no dist/ folder (#2583)
Updated dependencies [
c96e24c4
]:v2.4.4
Compare Source
Patch Changes
assert
function in theDataRewrite.ts
. The incorrect method was imported (due to a bad (#2581)import auto-completion) and went unnoticed, leading to potential build issue.
cb7f414d
]:v2.4.3
Compare Source
Patch Changes
f6a8c1ce
]:v2.4.2
Compare Source
Patch Changes
@interfaceObject
type has a@requires
. When an@interfaceObject
type has a field with a (#2524)@requires
and the query requests that field only for some specific implementations of the corresponding interface,then the generated query plan was sometimes invalid and could result in an invalid query to a subgraph (against a
subgraph that rely on
@apollo/subgraph
, this lead the subgraph to produce an error message looking like"The _entities resolver tried to load an entity for type X, but no object or interface type of that name was found in the schema"
).2c370508
,179b4602
]:v2.4.1
Compare Source
Patch Changes
Fix issues (incorrectly rejected composition and/or subgraph errors) with
@interfaceObject
. Those issues may occur (#2494)either due to some use of
@requires
in an@interfaceObject
type, or when some subgraphS
defines a type that is animplementation of an interface
I
in the supergraph, and there is an@interfaceObject
forI
in another subgraph,but
S
does not itself definesI
.Fix handling of aliases and variables in introspection queries. (#2506)
Start building packages with TS 5.x, which should have no effect on consumers (#2480)
Improves reuse of named fragments in subgraph fetches. When a question has named fragments, the code tries to reuse (#2497)
those fragment in subgraph fetches is those can apply (so when the fragment is fully queried in a single subgraph fetch).
However, the existing was only able to reuse those fragment in a small subset of cases. This change makes it much more
likely that if a fragment can be reused, it will be.
Updated dependencies [
450b9578
,afde3158
,eafebc3c
,01fe3f83
]:v2.4.0
Compare Source
Minor Changes
This change introduces a configurable query plan cache. This option allows (#2385)
developers to provide their own query plan cache like so:
The current default implementation is effectively as follows:
TypeScript users should implement the
QueryPlanCache
type which is nowexported by
@apollo/query-planner
:Adds debug/testing query planner options (
debug.bypassPlannerForSingleSubgraph
) to bypass the query planning (#2441)process for federated supergraph having only a single subgraph. The option is disabled by default, is not recommended
for production, and is not supported (it may be removed later). It is meant for debugging/testing purposes.
Patch Changes
Refactor the internal implementation of selection sets used by the query planner to decrease the code complexity and (#2387)
improve query plan generation performance in many cases.
Optimises query plan generation for parts of queries that can statically be known to not cross across subgraphs (#2449)
Updated dependencies [
260c357c
,7bc0f8e8
,d4426ff9
,a9385bdb
,1a555d98
,ade7ceb8
,09382e74
,cab383b2
]:v2.3.6
Compare Source
Patch Changes
Handle defaulted variables correctly during post-processing. (
98844fd5
)Users who tried to use built-in conditional directives (skip/include) with defaulted variables and no variable provided would encounter an error thrown by operation post-processing saying that the variables weren't provided. The defaulted values went unaccounted for, so the operation would validate but then fail an assertion while resolving the conditional.
With this change, defaulted variable values are now collected and provided to post-processing (with defaults being overwritten by variables that are actually provided).
Fix issues (incorrectly rejected composition and/or subgraph errors) with
@interfaceObject
. Those issues may occur (11f2d7c0
)either due to some use of
@requires
in an@interfaceObject
type, or when some subgraphS
defines a type that is animplementation of an interface
I
in the supergraph, and there is an@interfaceObject
forI
in another subgraph,but
S
does not itself definesI
.Fix handling of aliases and variables in introspection queries. (
ef5c8170
)Fix potential bug when an
@interfaceObject
type has a@requires
. When an@interfaceObject
type has a field with a (2894a1ea
)@requires
and the query requests that field only for some specific implementations of the corresponding interface,then the generated query plan was sometimes invalid and could result in an invalid query to a subgraph (against a
subgraph that rely on
@apollo/subgraph
, this lead the subgraph to produce an error message looking like"The _entities resolver tried to load an entity for type X, but no object or interface type of that name was found in the schema"
).Updated dependencies [
98844fd5
,11f2d7c0
,c0412fd9
,2894a1ea
,ce0459a6
]:v2.3.5
Compare Source
Patch Changes
09382e74
]:v2.3.4
Compare Source
Patch Changes
Handle defaulted variables correctly during post-processing. (#2443)
Users who tried to use built-in conditional directives (skip/include) with defaulted variables and no variable provided would encounter an error thrown by operation post-processing saying that the variables weren't provided. The defaulted values went unaccounted for, so the operation would validate but then fail an assertion while resolving the conditional.
With this change, defaulted variable values are now collected and provided to post-processing (with defaults being overwritten by variables that are actually provided).
Updated dependencies [
6e2d24b5
]:v2.3.3
Compare Source
Patch Changes
Update @apollo/utils.logger typings dependency (#2269)
Exposes, for each subgraph request, the path in the overall gateway operation at which that subgraph request gets inserted. This path is now available as the pathInIncomingRequest field in the arguments of RemoteGraphQLDataSource.willSendRequest and RemoteGraphQLDataSource.didReceiveResponse. (#2384)
Previously the
queryPlanStoreKey
was a hash of the query concatenated with an unhashedoperationName
if it was present. This resulted in variable length cache keys that could become unnecessarily long, occupying additional space in the query plan cache. (#2310)This change incorporates the
operationName
into the hash itself (ifoperationName
is present).Update @apollo/utils.createhash package, which drops support for node 12 (#2266)
Update @apollo/utils.isnodelike package, which dropped support for node 12 (#2268)
Update @apollo/utils.fetcher package, which drops support for node 12 (#2267)
Updated dependencies [
71a07f30
]:v2.3.2
Compare Source
Patch Changes
Move gateway post-processing errors from
errors
intoextensions.valueCompletion
of the response (#2380)[https://github.com/apollographql/federation/pull/2335](https://togithub.com/apollographql/federation/pull/2335)5]\(PR #2335) introduced a breaking change that broke existing usages with respect to nullability and gateway error handling. In response to [https://github.com/apollographql/federation/issues/2374](https://togithub.com/apollographql/federation/issues/2374)4]\(Issue #2374), we are reverting the breaking portion of this change by continuing to swallow post processing errors as the gateway did prior to v2.3.0. Instead, those errors will now be included on the
extensions.valueCompletion
object in the response object.Gateway v2.3.0 and v2.3.1 are both affected by this change in behavior.
Updated dependencies []:
v2.3.1
Compare Source
Patch Changes
Capture non-ftv1 error information in metrics data. This (#2242)
error information allows the inline trace plugin to correctly
aggregate stats about errors (where no federated trace data
is available) and stop reporting incomplete traces which
are missing unavailable error information.
This PR is a precursor to apollographql/apollo-server#7136
Fix issue where the query planner was incorrectly not querying
__typename
in a subgraph fetch when@interfaceObject
is involved (#2366)Updated dependencies [
7e2ca46f
,eb5a8bc0
]:This CHANGELOG pertains only to Apollo Federation packages in the 2.x range. The Federation v0.x equivalent for this package can be found here on the
version-0.x
branch of this repo.v2.3.0
Compare Source
@shareable
field when@external
is on a type in a fed1 schema (one without@link
) PR #2343.@interfaceObject
queries due to missing "input rewrites" PR #2346.apollographql/apollo-server (@apollo/server)
v4.7.5
Compare Source
Patch Changes
#7614
4fadf3ddc
Thanks @Cellule! - Publish TypeScript typings for CommonJS modules output.This allows TypeScript projects that use CommonJS modules with
moduleResolution: "node16"
ormoduleResolution: "nodeNext"
to correctly resolves the typings of apollo's packages as CommonJS instead of ESM.
Updated dependencies [
4fadf3ddc
]:Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, 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 has been generated by Mend Renovate. View repository job log here.