chore(deps): bump @graphql-tools/utils from 8.6.9 to 8.9.0

[dependabot[bot]]

Bumps @graphql-tools/utils from 8.6.9 to 8.9.0.

Release notes

Sourced from @​graphql-tools/utils's releases.

@​graphql-tools/utils@​8.9.0

Minor Changes

• 2a3b45e3: Allow & in filenames.

  Related to dotansimha/graphql-code-generator#6174

@​graphql-tools/utils@​8.8.0

Minor Changes

• d76a299c: Support TypeScript module resolution.

Patch Changes

• a0abbbcd: fix(visitResult): handle introspection fields correctly with an introspection query result

@​graphql-tools/utils@​8.7.0

Minor Changes

• 4914970b: 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.

Changelog

Sourced from @​graphql-tools/utils's changelog.

8.9.0

Minor Changes

• 2a3b45e3: Allow & in filenames.

  Related to dotansimha/graphql-code-generator#6174

8.8.0

Minor Changes

• d76a299c: Support TypeScript module resolution.

Patch Changes

• a0abbbcd: fix(visitResult): handle introspection fields correctly with an introspection query result

8.7.0

Minor Changes

• 4914970b: 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.

8.6.13

Patch Changes

• 041c5ba1: Use caret range for the tslib dependency

8.6.12

Patch Changes

• da7ad43b: Fix GraphQL v17 incompatibility issues and introduce createGraphQLError helper function for backwards compatibility.

8.6.11

Patch Changes

• c0762ee3: Incoming GraphQL v17 compatibility #4468

8.6.10

Patch Changes

• 0fc510cb: Interface implementations should be included when a return type is an interface.

Commits

• fbb0709 chore(release): update monorepo packages versions (#4604)
• 2a3b45e feat: allow ampersand in file names to load (#4603)
• b9b8dd7 chore(release): update monorepo packages versions (#4542)
• d76a299 feat: support TypeScript esm + esm and cjs import tests on CI (#4539)
• a0abbbc fix(visitResult): handle introspection fields correctly with an introspection...
• d8558da chore(release): update monorepo packages versions (#4534)
• 4914970 Introduce 'batch' flag, improve loadSchema and merge wrapped schemas properly...
• 31e1726 chore(deps): update all non-major dependencies (#4526)
• 5233256 chore(deps): update dependency graphql-upload to v15 (#4490)
• 8b63198 chore(release): update monorepo packages versions (#4513)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)