Skip to content

fix(deps): update graphql-tools monorepo #15

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix(deps): update graphql-tools monorepo #15

wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 11, 2023 •
edited
Loading

This PR contains the following updates:

Package Change Age Confidence
@graphql-tools/load-files (source) 6.0.18 -> 6.6.1 age confidence
@graphql-tools/merge (source) 6.0.18 -> 6.2.17 age confidence
@graphql-tools/schema (source) 6.0.18 -> 6.2.4 age confidence

Release Notes

ardatan/graphql-tools (@​graphql-tools/load-files)

v6.6.1

Compare Source

Patch Changes

v6.6.0

Compare Source

Minor Changes
  • d76a299: Support TypeScript module resolution.

v6.5.4

Compare Source

Patch Changes
  • 041c5ba: Use caret range for the tslib dependency

v6.5.3

Compare Source

Patch Changes
  • 525e391: fix(load-files): use createRequire in case of ESM

v6.5.2

Compare Source

Patch Changes
  • 4bfb342: enhance: use ^ for tslib dependency

v6.5.1

Compare Source

Patch Changes
  • 1043219: fix implicit dependencies

v6.5.0

Compare Source

Minor Changes
  • eb80821: enhance(load-files): return DocumentNode if it is an SDL

v6.4.0

Compare Source

Minor Changes
  • c5b0719: feat: GraphQL v16 support

v6.3.2

Compare Source

Patch Changes

v6.3.1

Compare Source

Patch Changes
  • 61889f2: fix(load-files): respect ignoredExtensions even if there is a specific file glob

v6.3.0

Compare Source

Minor Changes
  • efe8b8a: feat(load-files): ability to provide a custom extractExports

v6.2.7

Compare Source

Patch Changes
  • a2e7ff7: Allow extensions and ignoredExtensions options to have a trailing dot

v6.2.6

Compare Source

Patch Changes
  • 5c7a20d: fix(load-files): fix ignored file bug when filename finishes with extension

v6.2.5

Compare Source

Patch Changes
  • eacf0dc: Replace fs-extra with native methods

v6.2.4

Compare Source

Patch Changes
  • 533d6d5: Bump all packages to allow adjustments

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
ardatan/graphql-tools (@​graphql-tools/merge)

v6.2.17

Compare Source

Patch Changes

v6.2.16

Compare Source

Patch Changes

v6.2.15

Compare Source

Patch Changes

v6.2.14

Compare Source

Patch Changes
  • eae2879: fix(merge): handle undefined interfaces array on ObjectTypeDefinitionNode #​2629

v6.2.13

Compare Source

Patch Changes
  • 60a9c9a: fix(merge): handle arrays correctly

v6.2.12

Compare Source

Patch Changes
  • 6894666: fix(merge): fix handling schema definitions with convertExtensions flag

v6.2.11

Compare Source

Patch Changes

v6.2.10

Compare Source

Patch Changes

  • 0194118: Introduces a suite of stitched schema validations that enforce the integrity of merged
    schemas. This includes validations for:

    • Strict and safe null consistency (the later of which allows safe transitions in nullability).
    • Named type consistency with the option to whitelist proxiable scalar mappings.
    • Argument and input field name consistency.
    • Enum value consistency when used as an input value.

    Validations may be adjusted by setting validationLevel to off|warn|error globally or scoped
    for specific types and fields. In this initial v7 release, all validations are introduced at the
    warn threshold for backwards compatibility. Most of these validations will become automatic
    errors in v8. To enable validation errors now, set validationLevel: 'error'. Full configuration
    options look like this:

    const gatewaySchema = stitchSchemas({
  subschemas: [...],
  typeMergingOptions: {
    validationSettings: {
      validationLevel: 'error',
      strictNullComparison: false, // << gateway "String" may proxy subschema "String!"
      proxiableScalars: {
        ID: ['String'], // << gateway "ID" may proxy subschema "String"
      }
    },
    validationScopes: {
      // scope to specific element paths
      'User.id': {
        validationLevel: 'warn',
        strictNullComparison: true,
      },
    }
  },
});

v6.2.9

Patch Changes
  • 219ed39: enhance(load/module-loader/merge): use getDocumentNodeFromSchema instead of parse and
    printSchemaWithDirectives together
  • Updated dependencies [219ed39]
  • Updated dependencies [219ed39]
  • Updated dependencies [219ed39]

v6.2.8

Patch Changes
  • 8f331aa: enhance(load/module-loader/merge): use getDocumentNodeFromSchema instead of parse and
    printSchemaWithDirectives together
  • Updated dependencies [8f331aa]
  • Updated dependencies [8f331aa]

v6.2.7

Compare Source

Patch Changes
  • d9b82a2: fix(merge/stitch) consistent enum value merge
  • d9b82a2: enhance(stitch) canonical merged type and field definitions. Use the @​canonical
    directive to promote preferred type and field descriptions into the combined gateway schema.

v6.2.6

Compare Source

Patch Changes
  • 878c36b: enhance(stitch): use mergeScalar from merge

v6.2.5

Compare Source

Patch Changes
Schema Generation and Decoration API (@graphql-tools/schema)

  • 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.

Schema Delegation (delegateToSchema & @graphql-tools/delegate)

  • 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.

Remote Schemas & Wrapping (wrapSchema, makeRemoteExecutableSchema, and @graphql-tools/wrap)

  • 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.

Schema Stitching (stitchSchemas & @graphql-tools/stitch)

  • 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.

Mocking (addMocksToSchema and @graphql-tools/mock)
  • 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.
Other Utilities (@graphql-tools/utils)
  • 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.

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

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

What’s Changed
🧰 Enhancements
🐛 Bug Fixes

v6.2.1

Patch Changes

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
ardatan/graphql-tools (@​graphql-tools/schema)

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

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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Contributor Author

renovate bot commented Jan 11, 2023

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: undefined@undefined
npm ERR! Found: [email protected]
npm ERR! node_modules/jest
npm ERR!   dev jest@"^27.2.5" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer jest@"^29.0.0" from [email protected]
npm ERR! node_modules/ts-jest
npm ERR!   dev ts-jest@"^29.0.3" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate-cache/others/npm/_logs/2023-01-11T10_24_46_673Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2023-01-11T10_24_46_673Z-debug-0.log

@renovate
Copy link
Contributor Author

renovate bot commented Aug 11, 2025 •
edited
Loading

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: undefined@undefined
npm ERR! Found: [email protected]
npm ERR! node_modules/jest
npm ERR!   dev jest@"^27.2.5" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer jest@"^29.0.0 || ^30.0.0" from [email protected]
npm ERR! node_modules/ts-jest
npm ERR!   dev ts-jest@"^29.0.3" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2025-10-23T16_12_33_720Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant