Upcoming Release Changes #3011
Merged
Upcoming Release Changes #3011
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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
github-actions
bot
force-pushed
the
changeset-release/master
branch
13 times, most recently
from
73e0ba0
to
1515fba
Compare
github-actions
bot
force-pushed
the
changeset-release/master
branch
17 times, most recently
from
a3cad88
to
ee87892
Compare
github-actions
bot
force-pushed
the
changeset-release/master
branch
12 times, most recently
from
760a3e3
to
3caec61
Compare
github-actions
bot
force-pushed
the
changeset-release/master
branch
5 times, most recently
from
cdc78b7
to
cea0849
Compare
github-actions
bot
force-pushed
the
changeset-release/master
branch
from
cea0849
to
ae09dcb
Compare
github-actions
bot
force-pushed
the
changeset-release/master
branch
3 times, most recently
from
eb287f5
to
372b48d
Compare
github-actions
bot
force-pushed
the
changeset-release/master
branch
2 times, most recently
from
85dcc2f
to
d60bb25
Compare
github-actions
bot
force-pushed
the
changeset-release/master
branch
from
d60bb25
to
fb90631
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 was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Releases
@graphql-tools/batch-delegate@8.0.0
Major Changes
dae6dc7: refactor: ExecutionParams type replaced by Request type
rootValue property is now a part of the Request type.
When delegating with delegateToSchema, rootValue can be set multiple ways:
-- rootValue can be passed to delegateToSchema via a named option
-- rootValue can be included within a subschemaConfig
-- otherwise, rootValue is inferred from the originating schema
When using wrapSchema/stitchSchemas, a subschemaConfig can specify the createProxyingResolver function which can pass whatever rootValue it wants to delegateToSchema as above.
Patch Changes
@graphql-tools/batch-execute@8.0.0
Major Changes
dae6dc7: refactor: ExecutionParams type replaced by Request type
rootValue property is now a part of the Request type.
When delegating with delegateToSchema, rootValue can be set multiple ways:
-- rootValue can be passed to delegateToSchema via a named option
-- rootValue can be included within a subschemaConfig
-- otherwise, rootValue is inferred from the originating schema
When using wrapSchema/stitchSchemas, a subschemaConfig can specify the createProxyingResolver function which can pass whatever rootValue it wants to delegateToSchema as above.
c42e811: BREAKING CHANGES;
RequesttoExecutionRequestoperationType: OperationTypeNodefield inExecutionRequestcontextincreateRequestandcreateRequestInfoinstead ofdelegateToSchemaImprovements;
defaultExecutorfor a singleGraphQLSchemaso allowgetBatchingExecutorto memoizebatchingExecutorcorrectly.defaultExecutoris created forsubscriptionand other operation types. Only one executor is used.c0ca319: BREAKING CHANGE
Executorcan receiveAsyncIterableand subscriptions will also be handled byExecutor. This is a future-proof change for defer, stream and live queriesPatch Changes
@graphql-tools/delegate@8.0.0
Major Changes
7d3e300: BREAKING CHANGE
rootValuefrom subschemaConfigExecutionParamsor delegation optionsinfo.rootValueifrootValueis falsyd53e3be: BREAKING CHANGES;
Refactor the core delegation transforms into individual functions to modify request and results. This will improve the performance considerably by reducing the number of visits over the request document.
CheckResultAndHandleErrorswithcheckResultAndHandleErrorsdelegationBindingsAddArgumentsAsVariables,AddSelectionSets,AddTypenameToAbstract,ExpandAbstractTypes,FilterToSchema,VisitSelectionSetsandWrapConcreteTypeswithprepareGatewayRequestandfinalizeGatewayRequestdae6dc7: refactor: ExecutionParams type replaced by Request type
rootValue property is now a part of the Request type.
When delegating with delegateToSchema, rootValue can be set multiple ways:
-- rootValue can be passed to delegateToSchema via a named option
-- rootValue can be included within a subschemaConfig
-- otherwise, rootValue is inferred from the originating schema
When using wrapSchema/stitchSchemas, a subschemaConfig can specify the createProxyingResolver function which can pass whatever rootValue it wants to delegateToSchema as above.
c42e811: BREAKING CHANGES;
RequesttoExecutionRequestoperationType: OperationTypeNodefield inExecutionRequestcontextincreateRequestandcreateRequestInfoinstead ofdelegateToSchemaImprovements;
defaultExecutorfor a singleGraphQLSchemaso allowgetBatchingExecutorto memoizebatchingExecutorcorrectly.defaultExecutoris created forsubscriptionand other operation types. Only one executor is used.7d3e300: BREAKING CHANGE
AggregateErrorimplementation. The major difference is the individual errors are kept undererrorsproperty instead of the object itself withSymbol.iterator.aa43054: BREAKING CHANGE: validations are skipped by default, use validateRequest: true to reenable
c0ca319: BREAKING CHANGE
Executorcan receiveAsyncIterableand subscriptions will also be handled byExecutor. This is a future-proof change for defer, stream and live queriesPatch Changes
@graphql-tools/graphql-tag-pluck@7.0.0
Major Changes
Patch Changes
graphql-tools@8.0.0
Major Changes
makeExecutableSchemafrom@graphql-tools/schema@graphql-tools/*) because this npm package will no longer get updatedPatch Changes
@graphql-tools/jest-transform@1.0.0
Major Changes
Patch Changes
@graphql-tools/links@8.0.0
Major Changes
dae6dc7: refactor: ExecutionParams type replaced by Request type
rootValue property is now a part of the Request type.
When delegating with delegateToSchema, rootValue can be set multiple ways:
-- rootValue can be passed to delegateToSchema via a named option
-- rootValue can be included within a subschemaConfig
-- otherwise, rootValue is inferred from the originating schema
When using wrapSchema/stitchSchemas, a subschemaConfig can specify the createProxyingResolver function which can pass whatever rootValue it wants to delegateToSchema as above.
c42e811: BREAKING CHANGES;
RequesttoExecutionRequestoperationType: OperationTypeNodefield inExecutionRequestcontextincreateRequestandcreateRequestInfoinstead ofdelegateToSchemaImprovements;
defaultExecutorfor a singleGraphQLSchemaso allowgetBatchingExecutorto memoizebatchingExecutorcorrectly.defaultExecutoris created forsubscriptionand other operation types. Only one executor is used.c0ca319: BREAKING CHANGE
Executorcan receiveAsyncIterableand subscriptions will also be handled byExecutor. This is a future-proof change for defer, stream and live queriesMinor Changes
Patch Changes
@graphql-tools/load@7.0.0
Major Changes
af9a78d: BREAKING CHANGE
Now each loader handles glob patterns internally and returns an array of
Sourceobject instead of singleSourceGraphQL Tag Pluck now respects code locations and returns graphql-js
Sourceobjects for each found code blockThanks to the one above,
CodeFileLoadernow returns differentSourceobjects for each found SDL code block.Patch Changes
@graphql-tools/apollo-engine-loader@7.0.0
Major Changes
af9a78d: BREAKING CHANGE
Now each loader handles glob patterns internally and returns an array of
Sourceobject instead of singleSourceGraphQL Tag Pluck now respects code locations and returns graphql-js
Sourceobjects for each found code blockThanks to the one above,
CodeFileLoadernow returns differentSourceobjects for each found SDL code block.7d3e300: BREAKING CHANGE
AggregateErrorimplementation. The major difference is the individual errors are kept undererrorsproperty instead of the object itself withSymbol.iterator.Minor Changes
Patch Changes
@graphql-tools/code-file-loader@7.0.0
Major Changes
af9a78d: BREAKING CHANGE
Now each loader handles glob patterns internally and returns an array of
Sourceobject instead of singleSourceGraphQL Tag Pluck now respects code locations and returns graphql-js
Sourceobjects for each found code blockThanks to the one above,
CodeFileLoadernow returns differentSourceobjects for each found SDL code block.c5342de: Loader.canLoad and Loader.canLoadSync can only handle file paths not glob patterns
Minor Changes
Patch Changes
@graphql-tools/git-loader@7.0.0
Major Changes
af9a78d: BREAKING CHANGE
Now each loader handles glob patterns internally and returns an array of
Sourceobject instead of singleSourceGraphQL Tag Pluck now respects code locations and returns graphql-js
Sourceobjects for each found code blockThanks to the one above,
CodeFileLoadernow returns differentSourceobjects for each found SDL code block.c5342de: Loader.canLoad and Loader.canLoadSync can only handle file paths not glob patterns
Minor Changes
Patch Changes
@graphql-tools/github-loader@7.0.0
Major Changes
af9a78d: BREAKING CHANGE
Now each loader handles glob patterns internally and returns an array of
Sourceobject instead of singleSourceGraphQL Tag Pluck now respects code locations and returns graphql-js
Sourceobjects for each found code blockThanks to the one above,
CodeFileLoadernow returns differentSourceobjects for each found SDL code block.Minor Changes
Patch Changes
@graphql-tools/graphql-file-loader@7.0.0
Major Changes
af9a78d: BREAKING CHANGE
Now each loader handles glob patterns internally and returns an array of
Sourceobject instead of singleSourceGraphQL Tag Pluck now respects code locations and returns graphql-js
Sourceobjects for each found code blockThanks to the one above,
CodeFileLoadernow returns differentSourceobjects for each found SDL code block.c5342de: Loader.canLoad and Loader.canLoadSync can only handle file paths not glob patterns
Patch Changes
@graphql-tools/json-file-loader@7.0.0
Major Changes
af9a78d: BREAKING CHANGE
Now each loader handles glob patterns internally and returns an array of
Sourceobject instead of singleSourceGraphQL Tag Pluck now respects code locations and returns graphql-js
Sourceobjects for each found code blockThanks to the one above,
CodeFileLoadernow returns differentSourceobjects for each found SDL code block.Patch Changes
@graphql-tools/module-loader@7.0.0
Major Changes
af9a78d: BREAKING CHANGE
Now each loader handles glob patterns internally and returns an array of
Sourceobject instead of singleSourceGraphQL Tag Pluck now respects code locations and returns graphql-js
Sourceobjects for each found code blockThanks to the one above,
CodeFileLoadernow returns differentSourceobjects for each found SDL code block.Minor Changes
Patch Changes
@graphql-tools/url-loader@7.0.0
Major Changes
af9a78d: BREAKING CHANGE
Now each loader handles glob patterns internally and returns an array of
Sourceobject instead of singleSourceGraphQL Tag Pluck now respects code locations and returns graphql-js
Sourceobjects for each found code blockThanks to the one above,
CodeFileLoadernow returns differentSourceobjects for each found SDL code block.614c08c: BREAKING CHANGE
handleSDLAsyncandhandleSDLSync; usehandleSDLinsteaduseSSEForSubscriptionanduseWebSocketLegacyProtocol; usesubscriptionProtocolinsteadendpointfor remote execution sourcebuildHTTPExecutorwith a new signaturebuild*Subscribermethods are renamed tobuildWSLegacyExecutor,buildWSExecutorandbuildSSEExecutorwith new signaturesgetFetchno longer takesasyncflagdae6dc7: refactor: ExecutionParams type replaced by Request type
rootValue property is now a part of the Request type.
When delegating with delegateToSchema, rootValue can be set multiple ways:
-- rootValue can be passed to delegateToSchema via a named option
-- rootValue can be included within a subschemaConfig
-- otherwise, rootValue is inferred from the originating schema
When using wrapSchema/stitchSchemas, a subschemaConfig can specify the createProxyingResolver function which can pass whatever rootValue it wants to delegateToSchema as above.
c0ca319: BREAKING CHANGE
Executorcan receiveAsyncIterableand subscriptions will also be handled byExecutor. This is a future-proof change for defer, stream and live queries7d3e300: BREAKING CHANGE
headersNEW FEATURES
operationNameandextensionsextensions.headersPatch Changes
@graphql-tools/schema@8.0.0
Major Changes
loggerandaddErrorLoggingToSchemaaddSchemaLevelResolverbuildSchemaFromTypeDefinitions, usebuildSchemafromgraphql-jsinsteadallowUndefinedResolveoption inmakeExecutableSchemabecause GraphQL Schema itself does this checkingPatch Changes
@graphql-tools/stitch@8.0.0
Major Changes
7d3e300: BREAKING CHANGE
dae6dc7: refactor: ExecutionParams type replaced by Request type
rootValue property is now a part of the Request type.
When delegating with delegateToSchema, rootValue can be set multiple ways:
-- rootValue can be passed to delegateToSchema via a named option
-- rootValue can be included within a subschemaConfig
-- otherwise, rootValue is inferred from the originating schema
When using wrapSchema/stitchSchemas, a subschemaConfig can specify the createProxyingResolver function which can pass whatever rootValue it wants to delegateToSchema as above.
74581cf: fix(getDirectives): preserve order around repeatable directives
BREAKING CHANGE: getDirectives now always return an array of individual DirectiveAnnotation objects consisting of
nameandargsproperties.New useful function
getDirectivereturns an array of objects representing any args for each use of a single directive (returning the empty object{}when a directive is used without arguments).Note: The
getDirectivefunction returns an array even when the specified directive is non-repeatable. This is because one use of this function is to throw an error if more than one directive annotation is used for a non repeatable directive!When specifying directives in extensions, one can use either the old or new format.
c0ca319: BREAKING CHANGE
Executorcan receiveAsyncIterableand subscriptions will also be handled byExecutor. This is a future-proof change for defer, stream and live queriesMinor Changes
Patch Changes
@graphql-tools/stitching-directives@2.0.0
Major Changes
74581cf: fix(getDirectives): preserve order around repeatable directives
BREAKING CHANGE: getDirectives now always return an array of individual DirectiveAnnotation objects consisting of
nameandargsproperties.New useful function
getDirectivereturns an array of objects representing any args for each use of a single directive (returning the empty object{}when a directive is used without arguments).Note: The
getDirectivefunction returns an array even when the specified directive is non-repeatable. This is because one use of this function is to throw an error if more than one directive annotation is used for a non repeatable directive!When specifying directives in extensions, one can use either the old or new format.
Minor Changes
Patch Changes
@graphql-tools/utils@8.0.0
Major Changes
af9a78d: BREAKING CHANGE
Now each loader handles glob patterns internally and returns an array of
Sourceobject instead of singleSourceGraphQL Tag Pluck now respects code locations and returns graphql-js
Sourceobjects for each found code blockThanks to the one above,
CodeFileLoadernow returns differentSourceobjects for each found SDL code block.7d3e300: BREAKING CHANGE
fieldToFieldConfig,argsToFieldConfigArgumentandargumentToArgumentConfig.toConfigmethod instead for each.7d3e300: BREAKING CHANGE
dae6dc7: refactor: ExecutionParams type replaced by Request type
rootValue property is now a part of the Request type.
When delegating with delegateToSchema, rootValue can be set multiple ways:
-- rootValue can be passed to delegateToSchema via a named option
-- rootValue can be included within a subschemaConfig
-- otherwise, rootValue is inferred from the originating schema
When using wrapSchema/stitchSchemas, a subschemaConfig can specify the createProxyingResolver function which can pass whatever rootValue it wants to delegateToSchema as above.
6877b91: BREAKING CHANGES;
mergeDeepnow takes an array of sources instead of set of parameters as input and it takes an additional flag to enable prototype mergingInstead of
mergeDeep(...sources)=>mergeDeep(sources)c42e811: BREAKING CHANGES;
RequesttoExecutionRequestoperationType: OperationTypeNodefield inExecutionRequestcontextincreateRequestandcreateRequestInfoinstead ofdelegateToSchemaImprovements;
defaultExecutorfor a singleGraphQLSchemaso allowgetBatchingExecutorto memoizebatchingExecutorcorrectly.defaultExecutoris created forsubscriptionand other operation types. Only one executor is used.7d3e300: BREAKING CHANGE
AggregateErrorimplementation. The major difference is the individual errors are kept undererrorsproperty instead of the object itself withSymbol.iterator.8c8d4fc: BREAKING CHANGE: remove cloneSchema
7d3e300: BREAKING CHANGE
debugLogbut usesconsole.logdirectly only ifDEBUGis available underprocess.env7d3e300: BREAKING CHANGE
camelCasenaming convention inbuildOperationNodeForField74581cf: fix(getDirectives): preserve order around repeatable directives
BREAKING CHANGE: getDirectives now always return an array of individual DirectiveAnnotation objects consisting of
nameandargsproperties.New useful function
getDirectivereturns an array of objects representing any args for each use of a single directive (returning the empty object{}when a directive is used without arguments).Note: The
getDirectivefunction returns an array even when the specified directive is non-repeatable. This is because one use of this function is to throw an error if more than one directive annotation is used for a non repeatable directive!When specifying directives in extensions, one can use either the old or new format.
c0ca319: BREAKING CHANGE
Executorcan receiveAsyncIterableand subscriptions will also be handled byExecutor. This is a future-proof change for defer, stream and live queries7d3e300: BREAKING CHANGE
SchemaVisitor,visitSchemaandVisitSchemaKindmapSchemainsteadMinor Changes
Patch Changes
@graphql-tools/wrap@8.0.0
Major Changes
7d3e300: BREAKING CHANGE
makeRemoteExecutableSchemahas been removed.wrapSchemainsteaddae6dc7: refactor: ExecutionParams type replaced by Request type
rootValue property is now a part of the Request type.
When delegating with delegateToSchema, rootValue can be set multiple ways:
-- rootValue can be passed to delegateToSchema via a named option
-- rootValue can be included within a subschemaConfig
-- otherwise, rootValue is inferred from the originating schema
When using wrapSchema/stitchSchemas, a subschemaConfig can specify the createProxyingResolver function which can pass whatever rootValue it wants to delegateToSchema as above.
c42e811: BREAKING CHANGES;
RequesttoExecutionRequestoperationType: OperationTypeNodefield inExecutionRequestcontextincreateRequestandcreateRequestInfoinstead ofdelegateToSchemaImprovements;
defaultExecutorfor a singleGraphQLSchemaso allowgetBatchingExecutorto memoizebatchingExecutorcorrectly.defaultExecutoris created forsubscriptionand other operation types. Only one executor is used.7d3e300: BREAKING CHANGE
AggregateErrorimplementation. The major difference is the individual errors are kept undererrorsproperty instead of the object itself withSymbol.iterator.c0ca319: BREAKING CHANGE
introspectSchemaSync,introspectSchemaalready handles sync execution74581cf: fix(getDirectives): preserve order around repeatable directives
BREAKING CHANGE: getDirectives now always return an array of individual DirectiveAnnotation objects consisting of
nameandargsproperties.New useful function
getDirectivereturns an array of objects representing any args for each use of a single directive (returning the empty object{}when a directive is used without arguments).Note: The
getDirectivefunction returns an array even when the specified directive is non-repeatable. This is because one use of this function is to throw an error if more than one directive annotation is used for a non repeatable directive!When specifying directives in extensions, one can use either the old or new format.
c0ca319: BREAKING CHANGE
Executorcan receiveAsyncIterableand subscriptions will also be handled byExecutor. This is a future-proof change for defer, stream and live queriesPatch Changes
@graphql-tools/resolvers-composition@6.3.0
Minor Changes
Patch Changes
@graphql-tools/webpack-loader@6.5.0
Minor Changes
@graphql-tools/prisma-loader@6.3.1
Patch Changes
@graphql-tools/merge@6.2.15
Patch Changes
@graphql-tools/mock@8.1.4
Patch Changes
Object.prototype.hasOwnProperty#3069@graphql-tools/node-require@6.2.5
Patch Changes
@graphql-tools/relay-operation-optimizer@6.3.1
Patch Changes
federation-benchmark@0.0.1
Patch Changes