This repository has been archived by the owner on Mar 28, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 11
chore(deps): update apollo graphql packages to v2 (major) #17
Closed
Conversation
This file contains 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
renovate
bot
force-pushed
the
renovate/major-apollo-graphql-packages
branch
2 times, most recently
from
June 7, 2022 18:04
fc5cf07
to
ec67715
Compare
renovate
bot
force-pushed
the
renovate/major-apollo-graphql-packages
branch
from
June 30, 2022 11:58
ec67715
to
dfab0af
Compare
/guild newsletter |
/the-guild newsletter |
@charlypoly, issue saved for the The Guild Newsletter - Issue #3! ⚡️ |
renovate
bot
force-pushed
the
renovate/major-apollo-graphql-packages
branch
from
August 15, 2022 23:56
dfab0af
to
26ab6ea
Compare
renovate
bot
force-pushed
the
renovate/major-apollo-graphql-packages
branch
2 times, most recently
from
August 31, 2022 17:38
74163d4
to
186c9a4
Compare
renovate
bot
force-pushed
the
renovate/major-apollo-graphql-packages
branch
2 times, most recently
from
September 23, 2022 16:21
2b5d480
to
95d5223
Compare
renovate
bot
changed the title
Update Apollo GraphQL packages to v2 (major)
chore(deps): update apollo graphql packages to v2 (major)
Sep 27, 2022
renovate
bot
force-pushed
the
renovate/major-apollo-graphql-packages
branch
from
November 20, 2022 16:06
95d5223
to
3d2f31a
Compare
renovate
bot
force-pushed
the
renovate/major-apollo-graphql-packages
branch
6 times, most recently
from
December 7, 2022 09:38
49f9cd7
to
bcb3693
Compare
renovate
bot
force-pushed
the
renovate/major-apollo-graphql-packages
branch
2 times, most recently
from
December 9, 2022 20:43
cad1dc5
to
6026e41
Compare
renovate
bot
changed the title
chore(deps): update apollo graphql packages to v2 (major)
Update Apollo GraphQL packages to v2 (major)
Dec 17, 2022
renovate
bot
changed the title
Update Apollo GraphQL packages to v2 (major)
chore(deps): update apollo graphql packages to v2 (major)
Dec 17, 2022
renovate
bot
force-pushed
the
renovate/major-apollo-graphql-packages
branch
from
January 10, 2023 22:01
6026e41
to
2da777b
Compare
renovate
bot
force-pushed
the
renovate/major-apollo-graphql-packages
branch
5 times, most recently
from
January 26, 2023 00:21
51b87ca
to
d5f4a6a
Compare
renovate
bot
force-pushed
the
renovate/major-apollo-graphql-packages
branch
10 times, most recently
from
January 29, 2023 07:48
ce534df
to
dd9a84e
Compare
renovate
bot
force-pushed
the
renovate/major-apollo-graphql-packages
branch
2 times, most recently
from
February 9, 2023 14:15
706bc3c
to
1808620
Compare
renovate
bot
force-pushed
the
renovate/major-apollo-graphql-packages
branch
from
February 10, 2023 16:23
1808620
to
5a2db2a
Compare
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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:
0.54.1
->2.3.2
0.6.1
->2.3.2
Release Notes
apollographql/federation (@apollo/gateway)
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.v2.2.3
Compare Source
v2.2.2
Compare Source
v2.2.1
Compare Source
v2.2.0
Compare Source
default), but users that have custom code making use of
GraphQLDataSourceProcessOptions.document
will now need to explicitly set
GatewayConfig.queryPlannerConfig.exposeDocumentNodeInFetchNode
.@shareable
on interface fields. The@shareable
directive is aboutcontrolling if multiple subgraphs can resolve a particular field, and as interface field are never directly resolved
(it's their implementation that are), having
@shareable
on interface fields is not completely meaningful andwas never meant to be supported. If an existing subgraph does have a
@shareable
on an interface field, thiswill now be rejected, but the
@shareable
can simply and safely be removed since it previously was ignored.@shareable
to be repeatable so it can be allowed on both a type definition and its extensions PR #2175.__
PR #2237.v2.1.4
Compare Source
@defer
/@stream
definitions of supergraph are not included in the API schema PR #2212.@override
PR #2181.v2.1.3
Compare Source
v2.1.2
Compare Source
@requires
PR #2120.__typename
PR #2137.v2.1.1
Compare Source
v2.1.0
Compare Source
RemoteGraphQLDataSource.errorFromResponse
now returns aGraphQLError
(as defined bygraphql
) rather than anApolloError
(as defined byapollo-server-errors
). PR #2028RemoteGraphQLDataSource.errorFromResponse
manually and expect its return value to be a particular subclass ofGraphQLError
, or if you expect the error received bydidEncounterError
to be a particular subclass ofGraphQLError
, then this change may affect you. We recommend checkingerror.extensions.code
instead.LocalGraphQLDataSource
class no longer supports the undocumented__resolveObject
Apollo Server feature. PR #2007__resolveObject
feature withLocalGraphQLDataSource
, it will no longer work. If this affects you, file an issue and we can help you find a workaround.@require
#1873.executeQueryPlan
method, which is technicallyexported by the gateway. Most users of the gateway should not call this method directly (which is exported mainly
for testing purposes in the first place) and will thus be unaffected, but if you do call this method directly, you
will have to pass the new argument when upgrading. See the method documentation for details.
fields
of@key
,@provides
and@requires
PR #1975.@key
,@provides
or@requires
were parsed butnot honored in any way. As this change reject such applications (at composition time), it could theoretically
require to remove some existing (ignored) directive applications within a
@key
,@provides
or@requires
.@defer
) PR #2093.@require
fetch were not previously fetched PR #2075.graphql
to^16.5.0
to useGraphQLErrorOptions
PR #2060@apollo/utils.fetcher
to support aborting a request. This is a type-only change, and will not impact the underlying runtime. PR #2017.GraphQLDataSource.process
, are defined using types from the@apollo/server-gateway-interface
package instead of fromapollo-server-types
andapollo-server-core
. This is intended to be fully backwards-compatible; please file an issue if this leads to TypeScript compilation issues. PR #2044@link
when using@composeDirective
PR #2046@composeDirective
directive to specify directives that should be merged to the supergraph during composition PR #1996.fetcher
s should now accept aRequest
object which has asignal: AbortSignal
property https://fetch.spec.whatwg.org/#requestinit for request timeout purposes. PR #2017DEFAULT_UPLINK_ENDPOINTS
to static member ofUplinkSupergraphManager
PR #1977.node-fetch
as a runtime dependency PR #1970.v2.0.5
Compare Source
v2.0.4
Compare Source
extend schema
PR #1875.v2.0.3
Compare Source
printSubgraphSchema
method, ensuring it can be read back by composition andbuildSubgraphSchema
PR #1831.@requires
and conditional queries (@include
/@skip
) 1835.v2.0.2
Compare Source
getDefaultFetcher
function. This function returned the defaultfetch
implementation used to talk to Uplink (which is distinct from the defaultfetch
implementation used byRemoteGraphQLDataSource
to talk to subgraphs). It was the fetcher frommake-fetch-happen
v8 with some preset configuration relating to caching and request headers. However, the caching configuration was not actually being used when talking to Uplink (as we talk to Uplink over POST requests, and the Uplink protocol has an application-level mechanism for avoiding unnecessary large responses), and the request headers were already being provided explicitly by the Uplink client code. Since this release is also upgradingmake-fetch-happen
, it is impossible to promise that there would be no behavior change at all to the fetcher returned frommake-fetch-happen
, and as none of the preset configuration is actually relevant to the internal use ofgetDefaultFetcher
(which now just usesmake-fetch-happens
without extra configuration), we have removed the function. If you were using this function, you can replaceconst fetcher = getDefaultFetcher()
withimport fetcher from 'make-fetch-happen'
. PR #1805fetch
implementation used by default byUplinkFetcher
andRemoteGraphQLDataSource
is now imported frommake-fetch-happen
v10 instead of v8. The fetcher used byRemoteGraphQLDataSource
no longer limits the number of simultaneous requests per subgraph (or specifically, per host/port pair) to 15 by default; instead, there is no limit. (If you want to restore the previous behavior, installmake-fetch-happen
, importfetcher
from it, and passnew RemoteGraphQLDataSource({ fetcher: fetcher.defaults(maxSockets: 15)}))
in yourbuildService
option.) Note that if you invoke thefetcher
yourself in aRemoteGraphQLDataSource
subclass, you should ensure that you pass "plain" objects rather thanHeaders
orRequest
objects, as the newer version has slightly different logic about how to recognizeHeaders
andRequest
objects. We have adjusted the TypeScript types forfetcher
so that only these "plain" objects (which result in consistent behavior across all fetcher implementations) are permitted. PR #1805Schema.clone
when directive application happens before definition PR #1785@require
impacts the plans of followup queries PR #1783.@require
handling in query planning PR #1732__resolveReference
resolvers on toextensions
PR #1746@apollo/utils
packages forcreateSHA
andisNodeLike
PR #1765v2.0.1
Compare Source
for: SECURITY
in the core/link directive application in the supergraph for@inaccessible
PR #1715v2.0.0
Compare Source
apollographql/federation (@apollo/subgraph)
v2.3.2
Compare Source
Patch Changes
v2.3.1
Compare Source
Patch Changes
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
@tag
directive support for theSCHEMA
location. This has been added to the 2.3 version of the federation spec, so to access this functionality you must bump your federation spec version to 2.3 by using@link(url: "https://specs.apollo.dev/federation/v2.3", ...)
on yourschema
element. PR #2314.v2.2.3
Compare Source
v2.2.2
Compare Source
v2.2.1
Compare Source
v2.2.0
Compare Source
@link(url: "https://specs.apollo.dev/federation/v2.2")
), which:@shareable
to be repeatable so it can be allowed on both a type definition and its extensions PR #2175.v2.1.4
Compare Source
v2.1.3
Compare Source
v2.1.2
Compare Source
v2.1.1
Compare Source
v2.1.0
Compare Source
graphql
to^16.5.0
to useGraphQLErrorOptions
PR #2060v2.0.5
Compare Source
v2.0.4
Compare Source
v2.0.3
Compare Source
printSubgraphSchema
method, ensuring it can be read back by composition andbuildSubgraphSchema
PR #1831.@key
to be repeatable PR #1826.v2.0.2
Compare Source
v2.0.1
Compare Source
v2.0.0
Compare Source
Configuration
📅 Schedule: Branch creation - "after 10pm,before 6:00am" in timezone Europe/Warsaw, 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.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate. View repository job log here.