graphql-middleware-apollo-upload-server
graphql-middleware-apollo-upload-server copied to clipboard
chore(deps): update dependency graphql-tools to v9
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| graphql-tools (source) | 4.0.4 -> 9.0.18 |
Release Notes
ardatan/graphql-tools (graphql-tools)
v9.0.18
Patch Changes
- Updated dependencies []:
v9.0.17
Patch Changes
- Updated dependencies []:
v9.0.16
Patch Changes
- Updated dependencies []:
v9.0.15
Patch Changes
- Updated dependencies []:
v9.0.14
Patch Changes
- Updated dependencies []:
v9.0.13
Patch Changes
- Updated dependencies []:
v9.0.12
Patch Changes
- Updated dependencies
[
357b2ee]:
v9.0.11
Patch Changes
- Updated dependencies []:
v9.0.10
Patch Changes
- Updated dependencies []:
v9.0.9
Patch Changes
- Updated dependencies []:
v9.0.8
Patch Changes
- Updated dependencies []:
v9.0.7
Patch Changes
- Updated dependencies
[
020b9e4]:
v9.0.6
Patch Changes
- #6662
696a0d5Thanks @renovate! - dependencies updates:- Updated dependency
@graphql-tools/schema@^10.0.10↗︎ (from^10.0.9, independencies)
- Updated dependency
- Updated dependencies
[
696a0d5]:
v9.0.5
Patch Changes
- Updated dependencies []:
v9.0.4
Patch Changes
- Updated dependencies []:
v9.0.3
Patch Changes
- Updated dependencies []:
v9.0.2
Patch Changes
- Updated dependencies []:
v9.0.1
Patch Changes
- Updated dependencies []:
v9.0.0
Major Changes
Patch Changes
- Updated dependencies
[
944a68e8]:
v8.3.20
Patch Changes
v8.3.19
Patch Changes
- Updated dependencies []:
v8.3.18
Patch Changes
- Updated dependencies []:
v8.3.17
Patch Changes
- Updated dependencies []:
v8.3.16
Patch Changes
- Updated dependencies []:
v8.3.15
Patch Changes
- Updated dependencies
[
a4d36fcc]:
v8.3.14
Patch Changes
- Updated dependencies []:
v8.3.13
Patch Changes
- Updated dependencies []:
v8.3.12
Patch Changes
- Updated dependencies []:
v8.3.11
Patch Changes
- Updated dependencies []:
v8.3.10
Patch Changes
- Updated dependencies []:
v8.3.9
Patch Changes
- Updated dependencies []:
v8.3.8
Patch Changes
- Updated dependencies []:
v8.3.7
Patch Changes
- Updated dependencies []:
v8.3.6
Patch Changes
- Updated dependencies []:
v8.3.5
Patch Changes
- Updated dependencies []:
v8.3.4
Patch Changes
- Updated dependencies []:
v8.3.3
Patch Changes
- Updated dependencies
[
2609d71f]:
v8.3.2
Patch Changes
v8.3.1
Patch Changes
- Updated dependencies []:
v8.3.0
Minor Changes
d76a299: Support TypeScript module resolution.
Patch Changes
- Updated dependencies [
d76a299]
v8.2.13
Patch Changes
- Updated dependencies [
4914970]
v8.2.12
Patch Changes
v8.2.11
Patch Changes
v8.2.10
Patch Changes
v8.2.9
Patch Changes
v8.2.8
Patch Changes
v8.2.7
Patch Changes
v8.2.6
Patch Changes
v8.2.5
Patch Changes
v8.2.4
Patch Changes
- Updated dependencies [
722abad]
v8.2.3
Patch Changes
v8.2.2
Patch Changes
v8.2.1
Patch Changes
- Updated dependencies [
4914970]
v8.2.0
Minor Changes
c5b0719: feat: GraphQL v16 support
Patch Changes
- Updated dependencies [
c5b0719]
v8.1.0
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.0
Major Changes
7d3e300: BREAKING CHANGE- Now it only exports
makeExecutableSchemafrom@graphql-tools/schema - Please migrate to scoped packages(
@graphql-tools/*) because this npm package will no longer get updated
- Now it only exports
Patch Changes
- Updated dependencies [
7d3e300] - Updated dependencies [
7d3e300] - Updated dependencies [
7d3e300] - Updated dependencies [
7d3e300] - Updated dependencies [
7d3e300]
v7.0.5
Patch Changes
52971f4: fix(graphql-tools): provide @apollo/client as an optional package- Updated dependencies [
eae2879]
v7.0.4
Patch Changes
- Revert mock package to v7 to avoid breaking changes
v7.0.3
Patch Changes
v7.0.2
Patch Changes
v7.0.1
Patch Changes
- Updated dependencies [
294dedd] - Updated dependencies [
294dedd] - Updated dependencies [
2b6c813] - Updated dependencies [
8133a90] - Updated dependencies [
2b6c813]
v7.0.0
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.- The
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.
- Mocks returning objects with fields set as functions are now operating according to upstream
graphql-js convention, i.e. these functions take three arguments,
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.- Unused
fieldNodesutility functions have been removed. - Unused
typeContainsSelectionSetfunction has been removed, andtypesContainSelectionSethas been moved to thestitchpackage. - Unnecessary
Operationtype has been removed in favor ofOperationTypeNodefrom upstream graphql-js. - As above,
applySchemaTransforms/applyRequestTransforms/applyResultTransformshave been removed from theutilspackage, as they are implemented elsewhere or no longer necessary.
- The
Patch Changes
- Updated dependencies [
a925449]
v6.2.6
Patch Changes
-
96a7555: Fix releaseLast PATCH release actually transitively updated graphql-tools and @graphql-tools/delegate to use latest MAJOR version of dependencies.
-
Updated dependencies [
96a7555]
v6.2.5
Patch Changes
- Updated dependencies [
be1a157]- @graphql-tools/batch-execute@7.0.0
- @graphql-tools/delegate@7.0.0
- @graphql-tools/mock@7.0.0
- @graphql-tools/schema@7.0.0
- @graphql-tools/stitch@7.0.0
- @graphql-tools/utils@7.0.0
- @graphql-tools/wrap@7.0.0
- @graphql-tools/links@6.2.5
- @graphql-tools/merge@6.2.5
- @graphql-tools/batch-delegate@6.2.5
- @graphql-tools/url-loader@6.3.1
- @graphql-tools/graphql-tag-pluck@6.2.6
- @graphql-tools/load@6.2.5
- @graphql-tools/code-file-loader@6.2.5
- @graphql-tools/git-loader@6.2.5
- @graphql-tools/github-loader@6.2.5
- @graphql-tools/graphql-file-loader@6.2.5
- @graphql-tools/json-file-loader@6.2.5
- @graphql-tools/module-loader@6.2.5
- @graphql-tools/relay-operation-optimizer@6.2.5
- @graphql-tools/resolvers-composition@6.2.5
v6.2.4
Patch Changes
533d6d5: Bump all packages to allow adjustments- Updated dependencies [
32c3c4f] - Updated dependencies [
32c3c4f] - Updated dependencies [
32c3c4f] - Updated dependencies [
32c3c4f] - Updated dependencies [
32c3c4f] - Updated dependencies [
533d6d5]- @graphql-tools/stitch@6.2.4
- @graphql-tools/wrap@6.2.4
- @graphql-tools/import@6.2.4
- @graphql-tools/merge@6.2.4
- @graphql-tools/utils@6.2.4
- @graphql-tools/delegate@6.2.4
- @graphql-tools/batch-delegate@6.2.4
- @graphql-tools/graphql-tag-pluck@6.2.4
- @graphql-tools/links@6.2.4
- @graphql-tools/load@6.2.4
- @graphql-tools/code-file-loader@6.2.4
- @graphql-tools/git-loader@6.2.4
- @graphql-tools/github-loader@6.2.4
- @graphql-tools/graphql-file-loader@6.2.4
- @graphql-tools/json-file-loader@6.2.4
- @graphql-tools/module-loader@6.2.4
- @graphql-tools/url-loader@6.2.4
- @graphql-tools/mock@6.2.4
- @graphql-tools/relay-operation-optimizer@6.2.4
- @graphql-tools/resolvers-composition@6.2.4
- @graphql-tools/schema@6.2.4
- @graphql-tools/load-files@6.2.4
v6.2.3
Come talk to us directly on our Discord channel Contact us here: the-guild.dev
What’s Changed
- Update dependencies
🚀 Features
v6.2.2
Come talk to us directly on our Discord channel Contact us here: the-guild.dev
What’s Changed
🧰 Enhancements
🐛 Bug Fixes
- Handle recursive input types when pruning schemas @mdlavin (#2023)
- Increase maxBuffer to 1MB @standy (#2018)
v6.2.1
Come talk to us directly on our Discord channel Contact us here: the-guild.dev
What’s Changed
🧰 Enhancements
- enhance(stitch): simplify subschema sets @yaacovCR (#2001)
- enhance(stitch): introduce SubschemaSetConfig @yaacovCR (#1994)
- enhance(stitching): improve query batching @yaacovCR (#1987)
- enhance(typeMerging): add options @yaacovCR (#1982)
🐛 Bug Fixes
- fix(url-loader): should preserve ws and http in the middle of a pointer @kamilkisiela (#1991)
- fix(stitch) fix abstract type merge failure @gmac (#1981)
- fix(typeMerging): fix scalar type merging @yaacovCR (#1980)
v6.2.0
Come talk to us directly on our Discord channel Contact us here: the-guild.dev
What’s Changed
🚀 Features
- enable batch execution @yaacovCR (#1971)
🐛 Bug Fixes
- Support InputObjectTypeDefinition & InputObjectTypeExtension for getFieldsWithDirectives @danstarns (#1934)
- fix(mocking): support subscriptions @ardatan (#1952)
- fix(typeMerging): field selection sets @yaacovCR (#1958)
v6.1.0
Come talk to us directly on our Discord channel Contact us here: the-guild.dev
What’s Changed
🧰 Enhancements
- Expand extended interface selections for subservice compatibility @gmac (#1912)
- streamline imports @yaacovCR (#1940)
- Transforms for normalizing stitched subschema deprecations @gmac (#1925)
- refactor(typesContainSelectionSet): memoize @yaacovCR (#1921)
🐛 Bug Fixes
- fix(build-operation-for-field): respect field depth @ardatan (#1953)
- fix(typeMerging): fix interface merging @yaacovCR (#1917)
v6.0.18
Come talk to us directly on our Discord channel Contact us here: the-guild.dev
✏️ Docs
- Fix build:api-docs @danielrearden (#1899)
🧰 Enhancements
- enhance(load/utils): Improved
parseto support converting comments into descriptions @dotansimha (#1900) - enhance(stitching): increase key flexibility when type merging @yaacovCR (#1888)
v6.0.17
Come talk to us directly on our Discord channel Contact us here: the-guild.dev
What’s Changed
🚀 Features
🐛 Bug Fixes
- fix(url-loader): pass variables correctly on HTTP GET @ardatan (#1898)
- fix: change use of
instanceof Promiseto useis-promiselibrary @cajames (#1837)
v6.0.16
Come talk to us directly on our Discord channel Contact us here: the-guild.dev
What’s Changed
- fix(webpack-loader): use javascript compatible with IE @kamilkisiela (#1886)
🧰 Enhancements
- chore(batchDelegate): fix property names @yaacovCR (#1868)
- Make batch delegate send key arrays to loadMany @gmac (#1865)
- chore(batchDelegate): add tests, docs @yaacovCR (#1856)
- refactor(batchDelegate): simplify batch delegation @yaacovCR (#1855)
- Ensure UrlLoader uses introspection options @danielrearden (#1854)
- feat(batch-delegate): added mapping function to createBatchDelegateFn @jakeblaxon ([#
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.
- [ ] If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.