This repository has been archived by the owner on Jan 23, 2024. It is now read-only.
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:
4.0.0
->4.0.1
4.1.0
->4.1.3
2.3.2
->2.7.0
3.0.0
->3.1.0
Release Notes
apollographql/apollo-server (@apollo/server-plugin-landing-page-graphql-playground)
v4.0.1
Compare Source
Patch Changes
f4c3cd9b6
Thanks @trevor-scheer! - Officially deprecate Playground plugin via README updateapollographql/apollo-server (@apollo/server-plugin-response-cache)
v4.1.3
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.
v4.1.2
Compare Source
Patch Changes
f6e3ae021
Thanks @trevor-scheer! - Start building packages with TS 5.x, which should have no effect for usersv4.1.1
Compare Source
Patch Changes
4668f4594
Thanks @Igloczek! - Export types from response cache pluginapollographql/federation (@apollo/subgraph)
v2.7.0
Compare Source
Minor Changes
Implement progressive
@override
functionality (#2911)The progressive
@override
feature brings a new argument to the@override
directive:label: String
. When a label is added to an@override
application, the override becomes conditional, depending on parameters provided to the query planner (a set of which labels should be overridden). Note that this feature will be supported in router for enterprise users only.Out-of-the-box, the router will support a percentage-based use case for progressive
@override
. For example:The above example will override the root
hello
field from the "original" subgraph 5% of the time.More complex use cases will be supported by the router via the use of coprocessors/rhai to resolve arbitrary labels to true/false values (i.e. via a feature flag service).
Patch Changes
6ae42942b13dccd246ccc994faa2cb36cd62cb3c
,66833fb8d04c9376f6ed476fed6b1ca237f477b7
,931f87c6766c7439936df706727cbdc0cd6bcfd8
]:v2.6.3
Compare Source
Patch Changes
v2.6.2
Compare Source
Patch Changes
7b5b836d15247c997712a47847f603aa5887312e
,74ca7dd617927a20d79b824851f7651ef3c40a4e
]:v2.6.1
Compare Source
Patch Changes
0d5ab01a
]:v2.6.0
Compare Source
Patch Changes
b18841be
,e325b499
]:v2.5.7
Compare Source
Patch Changes
v2.5.6
Compare Source
Patch Changes
c719214a
]:v2.5.5
Compare Source
Patch Changes
Fix specific case for requesting __typename on interface entity type (#2775)
In certain cases, when resolving a __typename on an interface entity (due to it actual being requested in the operation), that fetch group could previously be trimmed / treated as useless. At a glance, it appears to be a redundant step, i.e.:
It's actually necessary to preserve this in the case that we're coming from an interface object to an (entity) interface so that we can resolve the concrete __typename correctly.
Updated dependencies []:
v2.5.4
Compare Source
Patch Changes
v2.5.3
Compare Source
Patch Changes
4b9a512b
,c6e0e76d
,1add932c
]:v2.5.2
Compare Source
Patch Changes
35179f08
]:v2.5.1
Compare Source
Patch Changes
b9052fdd
]:v2.5.0
Compare Source
Minor Changes
Introduce the new
@authenticated
directive for composition (#2644)Users may now compose
@authenticated
applications from their subgraphs into a supergraph. This addition will support a future version of Apollo Router that enables authenticated access to specific types and fields via directive applications.The directive is defined as follows:
In order to compose your
@authenticated
usages, you must update your subgraph's federation spec version to v2.5 and add the@authenticated
import to your existing imports like so:@​link(url: "https://specs.apollo.dev/federation/v2.5", import: [..., "@​authenticated"])
Patch Changes
fe1e3d7b
,6b18af50
,9396c0d6
,2b5796a9
,4f3c3b9e
]:v2.4.13
Compare Source
Patch Changes
v2.4.12
Compare Source
Patch Changes
693c2433
]:v2.4.11
Compare Source
Patch Changes
a740e071
]:v2.4.10
Compare Source
Patch Changes
b6be9f96
]:v2.4.9
Compare Source
Patch Changes
7ac83456
,d60349b3
,1bb7c512
,02eab3ac
,fd4545c2
]:v2.4.8
Compare Source
Patch Changes
62e0d254
,7f1ef73e
]:v2.4.7
Compare Source
Patch Changes
2d44f346
]:v2.4.6
Compare Source
Patch Changes
5cd17e69
,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
v2.4.3
Compare Source
Patch Changes
Resolve
Promise
references before calling__resolveType
on interface (#2556)Since the introduction of entity interfaces, users could not return
a
Promise
from__resolveReference
while implementing a synchronous,custom
__resolveType
function. This change fixes/permits this use case.Additional background / implementation details:
Returning a
Promise
from__resolveReference
has historically neverbeen an issue. However, with the introduction of entity interfaces, the
calling of an interface's
__resolveType
function became a new concern.__resolveType
functions expect a reference (and shouldn't be concernedwith whether those references are wrapped in a
Promise
). In order toaddress this, we can
await
the reference before calling the__resolveType
(this handles both the non-Promise
andPromise
case).Updated dependencies [
f6a8c1ce
]:v2.4.2
Compare Source
Patch Changes
2c370508
,179b4602
]:v2.4.1
Compare Source
Patch Changes
b6be9f96
]:v2.4.0
Compare Source
Patch Changes
Optimises query plan generation for parts of queries that can statically be known to not cross across subgraphs (#2449)
Updated dependencies [
260c357c
,7bc0f8e8
,1a555d98
,cab383b2
]:v2.3.6
Compare Source
Patch Changes
98844fd5
,11f2d7c0
,2894a1ea
]:v2.3.5
Compare Source
Patch Changes
v2.3.4
Compare Source
Patch Changes
6e2d24b5
]:v2.3.3
Compare Source
Patch Changes
Correctly attach provided subscription resolvers to the schema object (#2388)
Updated dependencies []:
apollographql/apollo-utils (@apollo/utils.keyvadapter)
v3.1.0
Compare Source
Minor Changes
e02f708
Thanks @HishamAli81! - Updated the KeyValueCache.KeyValueCacheSetOptions type to be configurable, to be able to support custom key value caches that require additional cache set options.Patch Changes
e02f708
]: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.