Skip to content
This repository has been archived by the owner on Apr 17, 2023. It is now read-only.

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 18, 2021

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@graphql-tools/load-files 6.2.5 -> 6.6.1 age adoption passing confidence
@graphql-tools/merge 6.2.7 -> 6.2.17 age adoption passing 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
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

v6.2.8

Patch Changes

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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/graphql-tools-monorepo branch from d8f35d6 to af07754 Compare March 24, 2021 12:05
@renovate renovate bot force-pushed the renovate/graphql-tools-monorepo branch from af07754 to de1c1a1 Compare March 31, 2021 13:13
@renovate renovate bot force-pushed the renovate/graphql-tools-monorepo branch 2 times, most recently from 6bb5a37 to f3317a5 Compare April 17, 2021 13:32
@renovate renovate bot force-pushed the renovate/graphql-tools-monorepo branch from f3317a5 to ed56bff Compare May 11, 2021 05:05
@renovate renovate bot force-pushed the renovate/graphql-tools-monorepo branch from ed56bff to 2bc1065 Compare October 18, 2021 16:34
@renovate renovate bot force-pushed the renovate/graphql-tools-monorepo branch from 2bc1065 to 8c5468e Compare March 7, 2022 13:49
@renovate renovate bot force-pushed the renovate/graphql-tools-monorepo branch from 8c5468e to 149b843 Compare June 18, 2022 21:21
@renovate renovate bot force-pushed the renovate/graphql-tools-monorepo branch from 149b843 to 5d8115a Compare September 25, 2022 20:26
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants