Update external major (major) - #73
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
requested review from
LSantha,
buuhuu,
dplaton,
herzog31,
laurentiumagureanu and
mhaack
July 19, 2021 12:09
renovate
Bot
force-pushed
the
renovate/major-external-major
branch
8 times, most recently
from
July 25, 2021 16:46
373cc7f to
d8da2ad
Compare
renovate
Bot
force-pushed
the
renovate/major-external-major
branch
12 times, most recently
from
July 31, 2021 00:54
ea934e3 to
9c5e087
Compare
renovate
Bot
force-pushed
the
renovate/major-external-major
branch
3 times, most recently
from
August 10, 2021 16:29
25f470b to
2fa2495
Compare
renovate
Bot
force-pushed
the
renovate/major-external-major
branch
from
August 18, 2021 14:54
2fa2495 to
6961675
Compare
renovate
Bot
force-pushed
the
renovate/major-external-major
branch
7 times, most recently
from
September 2, 2021 19:36
eee68d8 to
612904b
Compare
renovate
Bot
force-pushed
the
renovate/major-external-major
branch
2 times, most recently
from
September 9, 2021 11:35
e7d7ebf to
1623526
Compare
renovate
Bot
force-pushed
the
renovate/major-external-major
branch
4 times, most recently
from
September 19, 2021 21:59
b559f11 to
094dba6
Compare
renovate
Bot
force-pushed
the
renovate/major-external-major
branch
5 times, most recently
from
September 27, 2021 03:17
2db976e to
7ba62ae
Compare
renovate
Bot
force-pushed
the
renovate/major-external-major
branch
3 times, most recently
from
October 4, 2021 21:34
ef08d66 to
129206f
Compare
renovate
Bot
force-pushed
the
renovate/major-external-major
branch
8 times, most recently
from
October 8, 2021 14:51
db7f4e9 to
a02d938
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
6.2.4→10.1.06.2.4→10.2.26.2.4→11.1.21v4→v7v4→v7v5→v72.0.1→4.1.0^0.27.2→^1.0.04.3.5→6.2.2^4.1.2→^6.0.01.2.5→6.0.01.4.0→2.2.37.32.0→10.8.11.5.16→5.2.414.7.0→17.0.2^8.2.0→^14.0.08.4.0→11.8.01.23.3→2.2.115.1.0→18.0.017.0.2→19.2.817.0.2→19.2.87.5.0→22.1.0Release Notes
ardatan/graphql-tools (@graphql-tools/schema)
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]:v10.0.38Compare Source
Patch Changes
[
e90719b]:v10.0.37Compare Source
Patch Changes
[
615c1a2]:v10.0.36Compare Source
Patch Changes
[
79f1998]:v10.0.35Compare Source
Patch Changes
[
2609c94]:v10.0.34Compare Source
Patch Changes
[
981d461]:v10.0.33Compare Source
Patch Changes
[
a4b7dce]:v10.0.32Compare Source
Patch Changes
[
ae36a0e]:v10.0.31Compare Source
Patch Changes
[
6f3776c]:v10.0.30Compare Source
Patch Changes
[
2118a80]:v10.0.29Compare Source
Patch Changes
[
2fe123a]:v10.0.28Compare Source
Patch Changes
[
dddc5f6]:v10.0.27Compare Source
Patch Changes
[
fbb58b5]:v10.0.26Compare Source
Patch Changes
[
fd105f4,fded91e,3b99a9b]:v10.0.25Compare Source
Patch Changes
[
984d542,984d542,32d0457]:v10.0.24Compare Source
Patch Changes
[
e5f98c2,3c21496,e5f98c2,22af985,53db005]:v10.0.23Compare Source
Patch Changes
[
d123e26]:v10.0.22Compare Source
Patch Changes
[
4899c62,90a717e,26518de]:v10.0.21Compare Source
Patch Changes
[
155944b]:v10.0.20Compare Source
Patch Changes
[
4a2eb14]:v10.0.19Compare Source
Patch Changes
[
3547bba]:v10.0.18Compare Source
Patch Changes
[
651a5dc]:v10.0.17Compare Source
Patch Changes
357b2eeThanks @renovate! - dependencies updates:
value-or-promise@^1.0.12↗︎ (fromdependencies)[
0a3e193,357b2ee]:v10.0.16Compare Source
Patch Changes
[
53bb601,53bb601]:v10.0.15Compare Source
Patch Changes
[
4912f19]:v10.0.14Compare Source
Patch Changes
[
2c70d27]:v10.0.13Compare Source
Patch Changes
[
6a8123b]:v10.0.12Compare Source
Patch Changes
020b9e4Thanks @ardatan! - `AbortSignal` in `GraphQLResolveInfo`, and
`AbortSignal` in `ExecutionRequest`
Updated dependencies
[
020b9e4]:v10.0.11Compare Source
Patch Changes
696a0d5Thanks @renovate! - dependencies updates:
@graphql-tools/merge@^9.0.11↗︎(from
^9.0.10, independencies)@graphql-tools/utils@^10.6.1↗︎(from
^10.6.0, independencies)[
696a0d5,1b24656]:v10.0.10Compare Source
Patch Changes
[
1e02935]:v10.0.9Compare Source
Patch Changes
[
414e404]:v10.0.8Compare Source
Patch Changes
[
dc5043b]:v10.0.7Compare Source
Patch Changes
[
cf2ce5e]:v10.0.6Compare Source
Patch Changes
0286437Thanks @ardatan! - Improve directive extraction
Updated dependencies
[
0286437]:v10.0.5Compare Source
Patch Changes
b8bf584Thanks @ardatan! - Introduce `getDirectiveExtensions` and refactor
directive handling in the extensions
Updated dependencies
[
b8bf584]:v10.0.4Compare Source
Patch Changes
#6194
7368829Thanks @ardatan! - Handle interface objects in a different way
Updated dependencies
[
7368829,e10c13a]:v10.0.3Compare Source
Patch Changes
[
a4b7dce]:v10.0.2Compare Source
Patch Changes
[
2fe123a]:v10.0.1Compare Source
Patch Changes
[
3547bba]:v10.0.0Compare Source
Major Changes
944a68e8Thanks @ardatan! - Drop Node 14 support. Require Node.js
>= 16Patch Changes
[
944a68e8,944a68e8]:v9.0.19Compare Source
Patch Changes
05c97eb8Thanks @ardatan! - dependencies updates:
value-or-promise@^1.0.12↗︎ (from1.0.12, independencies)v9.0.18Compare Source
Patch Changes
1c95368aThanks @ardatan! - Use ranged versions for dependencies
Updated dependencies
[
1c95368a]:v9.0.17Compare Source
Patch Changes
[
04e3ecb9]:v9.0.16Compare Source
Patch Changes
[
b5c8f640]:v9.0.15Compare Source
Patch Changes
[
a94217e9,62d074be]:v9.0.14Compare Source
Patch Changes
[
8555c5c5]:v9.0.13Compare Source
Patch Changes
a4d36fccThanks @renovate! - dependencies updates:
value-or-promise@1.0.12↗︎ (from1.0.11, independencies)[
e3ec35ed]:v9.0.12Compare Source
Patch Changes
[
904fe770]:v9.0.11Compare Source
Patch Changes
[
13c24883]:v9.0.10Compare Source
Patch Changes
[
7411a5e7]:v9.0.9Compare Source
Patch Changes
[
c0639dd0]:v9.0.8Compare Source
Patch Changes
[
d83b1960]:v9.0.7Compare Source
Patch Changes
[
80836fa7,8f6d3efc,80836fa7,80836fa7,80836fa7]:v9.0.6Compare Source
Patch Changes
[
f7daf777]:v9.0.5Compare Source
Patch Changes
[
df5848b8,df5848b8,df5848b8]:v9.0.4Compare Source
Patch Changes
[
43c736bd]:v9.0.3Compare Source
Patch Changes
[
71cb4fae,403ed450]:v9.0.2Compare Source
Patch Changes
[
4fe3d9c0]:v9.0.1Compare Source
Patch Changes
05c97eb8Thanks @ardatan! - dependencies updates:
value-or-promise@^1.0.12↗︎ (from1.0.12, independencies)v9.0.0Compare Source
Major Changes
8cc8721fThanks @ardatan! - Thanks @mattkrick and @borisno2!
v8.5.1Compare Source
Patch Changes
2a3b45e]v8.5.0Compare Source
Minor Changes
d76a299: Support TypeScript module resolution.Patch Changes
a0abbbc]d76a299]v8.4.0Compare Source
Minor Changes
4914970:mergeSchemaswas skippingdefaultFieldResolveranddefaultMergedResolverbydefault while extracting resolvers for each given schema to reduce the overhead. But this doesn't
work properly if you mix wrapped schemas and local schemas. So new
includeDefaultMergedResolverflag is introduced in
getResolversFromSchemato put default "proxy" resolvers in the extractedresolver map for
mergeSchemas.This fixes an issue with alias issue, so nested aliased fields weren't resolved properly because
of the missing
defaultMergedResolverin the final merged schema which should come from thewrapped schema.
Patch Changes
4914970]v8.3.14Compare Source
Patch Changes
041c5ba: Use caret range for the tslib dependency041c5ba]v8.3.13Compare Source
Patch Changes
da7ad43]v8.3.12Compare Source
Patch Changes
c0762ee]v8.3.11Compare Source
Patch Changes
0fc510c](https://redirect.github.com/ardatan/graphql