Skip to content
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.

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

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

Merged
merged 1 commit into from
Jul 13, 2022

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 12, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@graphql-tools/merge 8.2.13 -> 8.3.0 age adoption passing confidence
@graphql-tools/schema 8.3.13 -> 8.5.0 age adoption passing confidence
@graphql-tools/utils 8.6.12 -> 8.8.0 age adoption passing confidence

Release Notes

ardatan/graphql-tools (@​graphql-tools/merge)

v8.3.0

Compare Source

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

v8.2.15

Compare Source

Patch Changes

v8.2.14

Compare Source

Patch Changes
ardatan/graphql-tools (@​graphql-tools/schema)

v8.5.0

Compare Source

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

v8.4.0

Compare Source

Minor Changes
  • 4914970: mergeSchemas was skipping defaultFieldResolver and defaultMergedResolver by default while extracting resolvers for each given schema to reduce the overhead. But this doesn't work properly if you mix wrapped schemas and local schemas. So new includeDefaultMergedResolver flag is introduced in getResolversFromSchema to put default "proxy" resolvers in the extracted resolver map for mergeSchemas.

    This fixes an issue with alias issue, so nested aliased fields weren't resolved properly because of the missing defaultMergedResolver in the final merged schema which should come from the wrapped schema.

Patch Changes

v8.3.14

Compare Source

Patch Changes
ardatan/graphql-tools (@​graphql-tools/utils)

v8.8.0

Compare Source

Minor Changes
  • d76a299: Support TypeScript module resolution.
Patch Changes
  • a0abbbc: fix(visitResult): handle introspection fields correctly with an introspection query result

v8.7.0

Compare Source

Minor Changes
  • 4914970: mergeSchemas was skipping defaultFieldResolver and defaultMergedResolver by default while extracting resolvers for each given schema to reduce the overhead. But this doesn't work properly if you mix wrapped schemas and local schemas. So new includeDefaultMergedResolver flag is introduced in getResolversFromSchema to put default "proxy" resolvers in the extracted resolver map for mergeSchemas.

    This fixes an issue with alias issue, so nested aliased fields weren't resolved properly because of the missing defaultMergedResolver in the final merged schema which should come from the wrapped schema.

v8.6.13

Compare Source

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

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the release:chore This PR is a chore (means nothing for users) label Jul 12, 2022
@netlify
Copy link

netlify bot commented Jul 12, 2022

Deploy Preview for redwoodjs-docs canceled.

Name Link
🔨 Latest commit 5bda7d0
🔍 Latest deploy log https://app.netlify.com/sites/redwoodjs-docs/deploys/62cdf766c307290008992466

@renovate renovate bot force-pushed the renovate/graphql-tools-monorepo branch from 1364aa9 to 5bda7d0 Compare July 12, 2022 22:36
@renovate renovate bot merged commit fa71004 into main Jul 13, 2022
@renovate renovate bot deleted the renovate/graphql-tools-monorepo branch July 13, 2022 00:33
@redwoodjs-bot redwoodjs-bot bot added this to the next-release milestone Jul 13, 2022
@jtoar jtoar modified the milestones: next-release, v2.2.0 Jul 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release:chore This PR is a chore (means nothing for users)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant