chore(deps-dev): bump @graphql-tools/delegate from 10.0.13 to 10.0.18

[dependabot]

Bumps @graphql-tools/delegate from 10.0.13 to 10.0.18.

Changelog

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

10.0.18

Patch Changes

• #6420 a867bbc Thanks @​ardatan! - dependencies updates:

  • Added dependency @repeaterjs/repeater@^3.0.6 ↗︎ (to dependencies)

• #6420 a867bbc Thanks @​ardatan! - Pass operation directives correctly to the subschema;

  query {
    hello @someDir
  }

• #6418 da93c08 Thanks @​ardatan! - Fix extra inline fragments for all abstract types in the upstream schema call

  If there are two subschemas like below, the final Node interface is implemented by both Oven and Toaster while they are not implemented in both schemas. In this case the query { products { id ... on Node { id } } } will need to be transformed to { products { id ... on Oven { id } ... on Node { id } } } for the first subschema. But previously the query planner was automatically creating inline fragments for all possible types which was not optimal. Now it adds inline fragments only if this case is seen.

  type Query {
    products: [Product]
  }
  union Product = Oven | Toaster
  interface Node {
  id: ID!
  }
  type Oven {
  id: ID!
  }

... (truncated)

Commits

• 05c6121 chore(release): update monorepo packages versions (#6419)
• a867bbc fix: forward operation directives to the subschema requests (#6420)
• da93c08 fix(delegate): avoid extra inline fragments for all abstract types in the ups...
• 396a1a7 chore(release): update monorepo packages versions (#6404)
• 3803897 enhance(federation/delegate): cleanup extra fields, empty inline fragments an...
• 2ccfa49 chore(release): update monorepo packages versions (#6373)
• 33e8146 fix(federation): prevent execution if query plan fails
• e5841ae chore(release): update monorepo packages versions (#6362)
• d54b21a fix(federation): hide internal resolution errors
• 108d7b4 chore(release): update monorepo packages versions (#6357)
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)