Skip to content

Conversation

@renovate
Copy link

@renovate renovate bot commented Jul 1, 2020

This PR contains the following updates:

Package Change Age Confidence
graphql-tools (source) 4.0.4 -> 9.0.23 age confidence

Release Notes

ardatan/graphql-tools (graphql-tools)

v9.0.23

Compare Source

Patch Changes

v9.0.22

Compare Source

Patch Changes

v9.0.21

Compare Source

Patch Changes

v9.0.20

Compare Source

Patch Changes

v9.0.19

Compare Source

Patch Changes

v9.0.18

Compare Source

Patch Changes

v9.0.17

Compare Source

Patch Changes

v9.0.16

Compare Source

Patch Changes

v9.0.15

Compare Source

Patch Changes

v9.0.14

Compare Source

Patch Changes

v9.0.13

Compare Source

Patch Changes

v9.0.12

Compare Source

Patch Changes

v9.0.11

Compare Source

Patch Changes

v9.0.10

Compare Source

Patch Changes

v9.0.9

Compare Source

Patch Changes

v9.0.8

Compare Source

Patch Changes

v9.0.7

Compare Source

Patch Changes

v9.0.6

Compare Source

Patch Changes

v9.0.5

Compare Source

Patch Changes

v9.0.4

Compare Source

Patch Changes

v9.0.3

Compare Source

Patch Changes

v9.0.2

Compare Source

Patch Changes

v9.0.1

Compare Source

Patch Changes

v9.0.0

Compare Source

Major Changes
Patch Changes

v8.3.20

Compare Source

Patch Changes

v8.3.19

Compare Source

Patch Changes

v8.3.18

Compare Source

Patch Changes

v8.3.17

Compare Source

Patch Changes

v8.3.16

Compare Source

Patch Changes

v8.3.15

Compare Source

Patch Changes

v8.3.14

Compare Source

Patch Changes

v8.3.13

Compare Source

Patch Changes

v8.3.12

Compare Source

Patch Changes

v8.3.11

Compare Source

Patch Changes

v8.3.10

Compare Source

Patch Changes

v8.3.9

Compare Source

Patch Changes

v8.3.8

Compare Source

Patch Changes

v8.3.7

Compare Source

Patch Changes

v8.3.6

Compare Source

Patch Changes

v8.3.5

Compare Source

Patch Changes

v8.3.4

Compare Source

Patch Changes

v8.3.3

Compare Source

Patch Changes

v8.3.2

Compare Source

Patch Changes

v8.3.1

Compare Source

Patch Changes

v8.3.0

Compare Source

Minor Changes
  • d76a299: Support TypeScript module resolution.
Patch Changes

v8.2.13

Compare Source

Patch Changes

v8.2.12

Compare Source

Patch Changes

v8.2.11

Compare Source

Patch Changes

v8.2.10

Compare Source

Patch Changes

v8.2.9

Compare Source

Patch Changes

v8.2.8

Compare Source

Patch Changes

v8.2.7

Compare Source

Patch Changes

v8.2.6

Compare Source

Patch Changes

v8.2.5

Compare Source

Patch Changes

v8.2.4

Compare Source

Patch Changes

v8.2.3

Compare Source

Patch Changes

v8.2.2

Compare Source

Patch Changes

v8.2.1

Compare Source

Patch Changes

v8.2.0

Compare Source

Minor Changes
  • c5b0719: feat: GraphQL v16 support
Patch Changes

v8.1.0

Compare Source

Minor Changes

v8.0.0

Compare Source

Major Changes
  • 7d3e300: BREAKING CHANGE
    • Now it only exports makeExecutableSchema from @graphql-tools/schema
    • Please migrate to scoped packages(@graphql-tools/*) because this npm package will no longer
      get updated
Patch Changes

v7.0.5

Compare Source

Patch Changes

v7.0.4

Compare Source

Patch Changes
  • Revert mock package to v7 to avoid breaking changes

v7.0.3

Compare Source

Patch Changes

v7.0.2

Compare Source

Patch Changes

v7.0.1

Compare Source

Patch Changes

v7.0.0

Compare Source

Major Changes
  • a925449: - Resolver validation options should now be set to error, warn or ignore rather
    than true or false. In previous versions, some of the validators caused errors to be thrown,
    while some issued warnings. This changes brings consistency to validator behavior.
    • The allowResolversNotInSchema has been renamed to requireResolversToMatchSchema, to
      harmonize the naming convention of all the validators. The default setting of
      requireResolversToMatchSchema is error, matching the previous behavior.
    • The delegateToSchema return value has matured and been formalized as an ExternalObject, 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 including slicedError, getErrors,
      getErrorsByPathSegment functions. Only external errors with missing or invalid paths must
      still be preserved by annotating the remote object with special properties. The new
      getUnpathedErrors function is therefore necessary for retrieving only these errors. Note also
      the new annotateExternalObject and mergeExternalObjects functions, as well as the renaming
      of handleResult to resolveExternalValue.

    • Transform types and the applySchemaTransforms are now relocated to the delegate package;
      applyRequestTransforms/applyResultTransforms functions have been deprecated, however, as
      this functionality has been replaced since v6 by the Transformer abstraction.

    • The transformRequest/transformResult methods are now provided additional delegationContext
      and transformationContext arguments -- these were introduced in v6, but previously optional.

    • The transformSchema method may wish to create additional delegating resolvers and so it is now
      provided the subschemaConfig and final (non-executable) transformedSchema parameters. As in
      v6, the transformSchema is 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 individual transformSchema methods also get access
      to the result of the first run, if necessary, they can create additional wrapping schema
      proxying resolvers.

    • applySchemaTransforms parameters have been updated to match and support the transformSchema
      parameters above.

    • wrapSchema and generateProxyingResolvers now only take a single options argument with named
      properties of type SubschemaConfig. The previously possible shorthand version with first
      argument consisting of a GraphQLSchema and second argument representing the transforms should
      be reworked as a SubschemaConfig object.

    • Similarly, the ICreateProxyingResolverOptions interface that provides the options for the
      createProxyingResolver property of SubschemaConfig options has been adjusted. The schema
      property previously could be set to a GraphQLSchema or a SubschemaConfig object. This
      property has been removed in favor of a subschemaConfig property that will always be a
      SubschemaConfig object. The transforms property has been removed; transforms should be
      included within the SubschemaConfig object.`

    • The format of the wrapping schema has solidified. All non-root fields are expected to use
      identical resolvers, either defaultMergedResolver or a custom equivalent, with root fields
      doing the hard work of proxying. Support for custom merged resolvers throught
      createMergedResolver has been deprecated, as custom merging resolvers conflicts when using
      stitching's type merging, where resolvers are expected to be identical across subschemas.

    • The WrapFields transform's wrappingResolver option 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 as
      TransformRootFields or TransformObjectFields.

    • The ExtendSchema transform has been removed, as it is conceptually simpler just to use
      stitchSchemas with one subschema.

    • The ReplaceFieldsWithFragment, AddFragmentsByField, AddSelectionSetsByField, and
      AddMergedTypeSelectionSets transforms has been removed, as they are superseded by the
      AddSelectionSets and VisitSelectionSets transforms. The AddSelectionSets purposely 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 the
      parseSelectionSet function from @graphql-tools/utils.

    • stitchSchemas's mergeTypes option is now true by default! This causes the onTypeConflict
      option to be ignored by default. To use onTypeConflict to select a specific type instead of
      simply merging, simply set mergeTypes to false.

    • schemas argument has been deprecated, use subschemas, typeDefs, or types, depending on
      what you are stitching.

    • When using batch delegation in type merging, the argsFromKeys function is now set only via the
      argsFromKeys property. Previously, if argsFromKeys was absent, it could be read from args.

    • Support for fragment hints has been removed in favor of selection set hints.

    • stitchSchemas now processes all GraphQLSchema and SubschemaConfig subschema input into new
      Subschema objects, handling schema config directives such aso@computed as well as generating
      the final transformed schema, stored as the transformedSchema property, if transforms are
      used. Signatures of the onTypeConflict, fieldConfigMerger, and inputFieldConfigMerger have
      been updated to include metadata related to the original and transformed subschemas. Note the
      property name change for onTypeConflict from schema to subschema.

    • 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, and info
      with parent available as this rather than as the first argument.
    • filterSchema's fieldFilter will now filter all fields across Object, Interface, and Input
      types. For the previous Object-only behavior, switch to the objectFieldFilter option.
    • Unused fieldNodes utility functions have been removed.
    • Unused typeContainsSelectionSet function has been removed, and typesContainSelectionSet has
      been moved to the stitch package.
    • Unnecessary Operation type has been removed in favor of OperationTypeNode from upstream
      graphql-js.
    • As above, applySchemaTransforms/applyRequestTransforms/applyResultTransforms have been
      removed from the utils package, as they are implemented elsewhere or no longer necessary.
Patch Changes

v6.2.6

Compare Source

Patch Changes

v6.2.5

Compare Source

Patch Changes

v6.2.4

Compare Source

Patch Changes

v6.2.3

Compare Source

Come talk to us directly on our Discord channel
Contact us here: the-guild.dev

What’s Changed
  • Update dependencies
🚀 Features

v6.2.2

Compare Source

Come talk to us directly on our Discord channel
Contact us here: the-guild.dev

What’s Changed
🧰 Enhancements
🐛 Bug Fixes

v6.2.1

Compare Source

Come talk to us directly on our Discord channel
Contact us here: the-guild.dev

What’s Changed
🧰 Enhancements
🐛 Bug Fixes

v6.2.0

Compare Source

Come talk to us directly on our Discord channel
Contact us here: the-guild.dev

What’s Changed
🚀 Features
🐛 Bug Fixes

v6.1.0

Compare Source

Come talk to us directly on our Discord channel
Contact us here: the-guild.dev

What’s Changed
🧰 Enhancements
🐛 Bug Fixes

v6.0.18

Compare Source

Come talk to us directly on our Discord channel
Contact us here: the-guild.dev

✏️ Docs
🧰 Enhancements

v6.0.17

Compare Source

Come talk to us directly on our Discord channel
Contact us here: the-guild.dev

What’s Changed
🚀 Features
🐛 Bug Fixes

v6.0.16

Compare Source

Come talk to us directly on our Discord channel
Contact us here: the-guild.dev

What’s Changed
🧰 Enhancements
🐛 Bug Fixes
  • fix(mapSchema): mapping fields to new types @​yaacovCR (#​1877)
  • fix(createRequest): selectionSet overrides fieldNodes @​yaacovCR (#​1820)
  • Fix issue with graphql-upload-client [@​danielrear

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.

@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 436904d to 2b2f765 Compare July 5, 2020 11:58
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 2b2f765 to 6955e4c Compare August 24, 2020 14:59
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 6955e4c to 4aa0b3b Compare October 26, 2020 08:58
@renovate renovate bot changed the title chore(deps): update dependency graphql-tools to v6 chore(deps): update dependency graphql-tools to v7 Oct 26, 2020
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 4aa0b3b to 9b5c685 Compare November 27, 2020 11:54
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 9b5c685 to c6bc751 Compare February 11, 2021 11:25
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from c6bc751 to 6b3c188 Compare April 26, 2021 17:09
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 6b3c188 to 25be13a Compare May 15, 2021 21:11
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 25be13a to 2c7c614 Compare October 18, 2021 21:30
@renovate renovate bot changed the title chore(deps): update dependency graphql-tools to v7 chore(deps): update dependency graphql-tools to v8 Oct 18, 2021
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 2c7c614 to e435d7d Compare March 26, 2022 15:45
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from e435d7d to 17d48d2 Compare April 24, 2022 19:48
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 17d48d2 to 331b63f Compare May 15, 2022 20:30
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch 2 times, most recently from f8b1ea7 to 79db2fe Compare June 23, 2022 23:53
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 79db2fe to 1634c39 Compare September 25, 2022 16:08
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 1634c39 to 59cf1fa Compare November 20, 2022 17:16
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 59cf1fa to c72d685 Compare March 18, 2023 22:07
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from c72d685 to 627387a Compare April 17, 2023 10:17
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 627387a to 95914a4 Compare May 28, 2023 11:25
@renovate renovate bot changed the title chore(deps): update dependency graphql-tools to v8 chore(deps): update dependency graphql-tools to v9 May 28, 2023
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 95914a4 to c791e97 Compare February 23, 2024 17:03
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from c791e97 to 7a2ec21 Compare October 15, 2024 13:50
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 7a2ec21 to 73d61ee Compare November 13, 2024 17:03
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch 2 times, most recently from dd4a9a3 to cf4ee4a Compare November 27, 2024 21:25
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from cf4ee4a to 1c7f2e8 Compare December 4, 2024 13:27
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch 2 times, most recently from 5d268c5 to ba9db11 Compare December 14, 2024 18:45
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from ba9db11 to cc322b2 Compare December 24, 2024 12:57
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch 2 times, most recently from cc32a2c to 5923a40 Compare January 6, 2025 13:01
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 5923a40 to 80c5469 Compare February 11, 2025 12:50
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch 2 times, most recently from d68d525 to 5f829c5 Compare February 25, 2025 18:48
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 5f829c5 to 225208b Compare March 4, 2025 03:34
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch 2 times, most recently from 3a98f34 to d9a5932 Compare March 14, 2025 02:39
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch 2 times, most recently from 9aaeaa0 to 737b5b3 Compare July 21, 2025 07:09
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 737b5b3 to 1407e8c Compare August 10, 2025 14:28
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch 2 times, most recently from 714e743 to 0a3a416 Compare November 4, 2025 16:07
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 0a3a416 to 6379919 Compare November 12, 2025 04:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant