fix: Update dependency graphql-tools to v9 #366
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]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
9 times, most recently
from
6a4b05d
to
9bec9da
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
4 times, most recently
from
58398da
to
f394fef
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
f394fef
to
782c720
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
6 times, most recently
from
0915509
to
3e0e01a
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
3 times, most recently
from
e46ff72
to
aadde31
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
5 times, most recently
from
ac1a9cf
to
0cd9296
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
2 times, most recently
from
a4b4dd2
to
9b93ce0
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
c3d3bdf
to
bc66b9f
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
2 times, most recently
from
110eb09
to
d4fb19a
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
d4fb19a
to
890f449
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
3 times, most recently
from
3a24d52
to
ef50416
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
ef50416
to
6590007
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
5 times, most recently
from
7800e9b
to
db7f604
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
2 times, most recently
from
f087c5c
to
1f560ef
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
2 times, most recently
from
bb649be
to
73c14b1
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
73c14b1
to
fcdbce2
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
2 times, most recently
from
97c83fb
to
42eb005
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
42eb005
to
59afc66
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
59afc66
to
90c0c73
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
90c0c73
to
e95d6da
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
e95d6da
to
9b01eb0
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
9b01eb0
to
6bd68e1
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
6bd68e1
to
d3e70dd
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
d3e70dd
to
54c17f7
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
54c17f7
to
df9e72e
Compare
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.6->9.0.2Release Notes
ardatan/graphql-tools (graphql-tools)
v9.0.2Compare Source
Patch Changes
v9.0.1Compare Source
Patch Changes
83c0af0Thanks @enisdenjo! - dependencies updates:@graphql-tools/schema@^10.0.2↗︎ (from^10.0.0, independencies)83c0af0]:v9.0.0Compare Source
Major Changes
944a68e8Thanks @ardatan! - Drop Node 14 support. Require Node.js>= 16Patch Changes
944a68e8]:v8.3.20Compare Source
Patch Changes
1c95368aThanks @ardatan! - Use ranged versions for dependenciesUpdated dependencies [
1c95368a]:v8.3.19Compare Source
Patch Changes
v8.3.18Compare Source
Patch Changes
v8.3.17Compare Source
Patch Changes
v8.3.16Compare Source
Patch Changes
v8.3.15Compare Source
Patch Changes
a4d36fcc]:v8.3.14Compare Source
Patch Changes
v8.3.13Compare Source
Patch Changes
v8.3.12Compare Source
Patch Changes
v8.3.11Compare Source
Patch Changes
v8.3.10Compare Source
Patch Changes
v8.3.9Compare Source
Patch Changes
v8.3.8Compare Source
Patch Changes
v8.3.7Compare Source
Patch Changes
v8.3.6Compare Source
Patch Changes
v8.3.5Compare Source
Patch Changes
v8.3.4Compare Source
Patch Changes
v8.3.3Compare Source
Patch Changes
2609d71f]:v8.3.2Compare Source
Patch Changes
1c95368aThanks @ardatan! - Use ranged versions for dependenciesUpdated dependencies [
1c95368a]:v8.3.1Compare Source
Patch Changes
v8.3.0Compare Source
Minor Changes
d76a299: Support TypeScript module resolution.Patch Changes
d76a299]v8.2.13Compare Source
Patch Changes
4914970]v8.2.12Compare Source
Patch Changes
041c5ba: Use caret range for the tslib dependency041c5ba]v8.2.11Compare Source
Patch Changes
v8.2.10Compare Source
Patch Changes
v8.2.9Compare Source
Patch Changes
v8.2.8Compare Source
Patch Changes
v8.2.7Compare Source
Patch Changes
v8.2.6Compare Source
Patch Changes
v8.2.5Compare Source
Patch Changes
v8.2.4Compare Source
Patch Changes
722abad]v8.2.3Compare Source
Patch Changes
v8.2.2Compare Source
Patch Changes
v8.2.1Compare Source
Patch Changes
4914970]v8.2.0Compare Source
Minor Changes
c5b0719: feat: GraphQL v16 supportPatch Changes
c5b0719]v8.1.0Compare Source
Minor Changes
b39588c: Deprecategraphql-toolswith a more clear message;This package has been deprecated and now it only exports makeExecutableSchema.
It will no longer receive updates.
We strongly recommend you to migrate to scoped packages such as @graphql-tools/schema, @graphql-tools/utils and etc.
Check out https://www.graphql-tools.com to learn which packages you should use instead!
v8.0.0Compare Source
Major Changes
7d3e300: BREAKING CHANGEmakeExecutableSchemafrom@graphql-tools/schema@graphql-tools/*) because this npm package will no longer get updatedPatch Changes
7d3e300]7d3e300]7d3e300]7d3e300]7d3e300]v7.0.5Compare Source
Patch Changes
52971f4: fix(graphql-tools): provide @apollo/client as an optional packageeae2879]v7.0.4Compare Source
Patch Changes
v7.0.3Compare Source
Patch Changes
2492665]2492665]2492665]v7.0.2Compare Source
Patch Changes
fb14cd2: Added export from new optimize packagefb14cd2]v7.0.1Compare Source
Patch Changes
294dedd]294dedd]2b6c813]8133a90]2b6c813]v7.0.0Compare Source
Major Changes
a925449: - Resolver validation options should now be set toerror,warnorignorerather thantrueorfalse. In previous versions, some of the validators caused errors to be thrown, while some issued warnings. This changes brings consistency to validator behavior.allowResolversNotInSchemahas been renamed torequireResolversToMatchSchema, to harmonize the naming convention of all the validators. The default setting ofrequireResolversToMatchSchemaiserror, matching the previous behavior.The
delegateToSchemareturn value has matured and been formalized as anExternalObject, in which all errors are integrated into the GraphQL response, preserving their initial path. Those advanced users accessing the result directly will note the change in error handling. This also allows for the deprecation of unnecessary helper functions includingslicedError,getErrors,getErrorsByPathSegmentfunctions. Only external errors with missing or invalid paths must still be preserved by annotating the remote object with special properties. The newgetUnpathedErrorsfunction is therefore necessary for retrieving only these errors. Note also the newannotateExternalObjectandmergeExternalObjectsfunctions, as well as the renaming ofhandleResulttoresolveExternalValue.Transform types and the
applySchemaTransformsare now relocated to thedelegatepackage;applyRequestTransforms/applyResultTransformsfunctions have been deprecated, however, as this functionality has been replaced since v6 by theTransformerabstraction.The
transformRequest/transformResultmethods are now provided additionaldelegationContextandtransformationContextarguments -- these were introduced in v6, but previously optional.The
transformSchemamethod may wish to create additional delegating resolvers and so it is now provided thesubschemaConfigand final (non-executable)transformedSchemaparameters. As in v6, thetransformSchemais kicked off once to produce the non-executable version, and then, if a wrapping schema is being generated, proxying resolvers are created with access to the (non-executable) initial result. In v7, the individualtransformSchemamethods also get access to the result of the first run, if necessary, they can create additional wrapping schema proxying resolvers.applySchemaTransformsparameters have been updated to match and support thetransformSchemaparameters above.wrapSchemaandgenerateProxyingResolversnow only take a single options argument with named properties of typeSubschemaConfig. The previously possible shorthand version with first argument consisting of aGraphQLSchemaand second argument representing the transforms should be reworked as aSubschemaConfigobject.Similarly, the
ICreateProxyingResolverOptionsinterface that provides the options for thecreateProxyingResolverproperty ofSubschemaConfigoptions has been adjusted. Theschemaproperty previously could be set to aGraphQLSchemaor aSubschemaConfigobject. This property has been removed in favor of asubschemaConfigproperty that will always be aSubschemaConfigobject. Thetransformsproperty has been removed; transforms should be included within theSubschemaConfigobject.`The format of the wrapping schema has solidified. All non-root fields are expected to use identical resolvers, either
defaultMergedResolveror a custom equivalent, with root fields doing the hard work of proxying. Support for custom merged resolvers throughtcreateMergedResolverhas been deprecated, as custom merging resolvers conflicts when using stitching's type merging, where resolvers are expected to be identical across subschemas.The
WrapFieldstransform'swrappingResolveroption has been removed, as this complicates multiple wrapping layers, as well as planned functionality to wrap subscription root fields in potentially multiple layers, as the wrapping resolvers may be different in different layers. Modifying resolvers can still be performed by use of an additional transform such asTransformRootFieldsorTransformObjectFields.The
ExtendSchematransform has been removed, as it is conceptually simpler just to usestitchSchemaswith one subschema.The
ReplaceFieldsWithFragment,AddFragmentsByField,AddSelectionSetsByField, andAddMergedTypeSelectionSetstransforms has been removed, as they are superseded by theAddSelectionSetsandVisitSelectionSetstransforms. TheAddSelectionSetspurposely takes parsed SDL rather than strings, to nudge end users to parse these strings at build time (when possible), rather than at runtime. Parsing of selection set strings can be performed using theparseSelectionSetfunction from@graphql-tools/utils.stitchSchemas'smergeTypesoption is now true by default! This causes theonTypeConflictoption to be ignored by default. To useonTypeConflictto select a specific type instead of simply merging, simply setmergeTypesto false.schemasargument has been deprecated, usesubschemas,typeDefs, ortypes, depending on what you are stitching.When using batch delegation in type merging, the
argsFromKeysfunction is now set only via theargsFromKeysproperty. Previously, ifargsFromKeyswas absent, it could be read fromargs.Support for fragment hints has been removed in favor of selection set hints.
stitchSchemasnow processes allGraphQLSchemaandSubschemaConfigsubschema input into newSubschemaobjects, handling schema config directives such aso@computedas well as generating the final transformed schema, stored as thetransformedSchemaproperty, if transforms are used. Signatures of theonTypeConflict,fieldConfigMerger, andinputFieldConfigMergerhave been updated to include metadata related to the original and transformed subschemas. Note the property name change foronTypeConflictfromschematosubschema.args,context, andinfowithparentavailable asthisrather than as the first argument.filterSchema'sfieldFilterwill now filter all fields across Object, Interface, and Input types. For the previous Object-only behavior, switch to theobjectFieldFilteroption.fieldNodesutility functions have been removed.typeContainsSelectionSetfunction has been removed, andtypesContainSelectionSethas been moved to thestitchpackage.Operationtype has been removed in favor ofOperationTypeNodefrom upstream graphql-js.applySchemaTransforms/applyRequestTransforms/applyResultTransformshave been removed from theutilspackage, as they are implemented elsewhere or no longer necessary.Patch Changes
a925449]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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.