fix(deps): update graphql-tools monorepo

Open renovate[bot] opened this issue 4 years ago • 0 comments

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@graphql-tools/load-files	`6.2.5` -> `6.6.1`
@graphql-tools/merge	`6.2.7` -> `6.2.17`

Release Notes

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

`v6.6.1`

Compare Source

Patch Changes

#4624 e3167edc Thanks @n1ru4l! - Fix CommonJS TypeScript resolution with moduleResolution node16 or nodenext

`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

7c6e008: Remove duplicate code

`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)

Patch Changes

a31f959: fix(merge): handle schema definitions correctly
Updated dependencies [af9a78d]
Updated dependencies [9c26b84]
Updated dependencies [7d3e300]
Updated dependencies [7d3e300]
Updated dependencies [dae6dc7]
Updated dependencies [6877b91]
Updated dependencies [7d3e300]
Updated dependencies [c42e811]
Updated dependencies [7d3e300]
Updated dependencies [8c8d4fc]
Updated dependencies [7d3e300]
Updated dependencies [7d3e300]
Updated dependencies [7d3e300]
Updated dependencies [74581cf]
Updated dependencies [c0ca319]
Updated dependencies [7d3e300]
Updated dependencies [982c8f5]
Updated dependencies [7d3e300]
Updated dependencies [7d3e300]
Updated dependencies [7d3e300]
- @graphql-tools/utils @8.0.0
- @graphql-tools/schema @8.0.0

`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

43da6b5: enhance(merge): reduce number of iterations
Updated dependencies [58fd4b2]
Updated dependencies [43da6b5]
- @graphql-tools/utils @7.7.0

`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]
- @graphql-tools/utils @7.5.0

`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]
- @graphql-tools/utils @7.4.0

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.

Mar 18 '21 19:03 renovate[bot]