Bump @apollo/gateway from 2.0.4 to 2.5.4 in /apollo-gateway

[dependabot[bot]]

Bumps @apollo/gateway from 2.0.4 to 2.5.4.

Release notes

Sourced from @​apollo/gateway's releases.

@​apollo/gateway@​2.5.4

Patch Changes

• Adds header to change the format of exposed query plans, and allows formatting it as json. (#2724)

  When the gateway is configured to allow it, adding the Apollo-Query-Plan-Experimental header to a request already allowed a "prettified" text version of the query plan used for the query is returned in the response extension. This changes adds support for a new (optional) accompanying header, Apollo-Query-Plan-Experimental-Format, which can be set to the value "internal" to have the query plan returned as a json object (that correspond to the internal representation of that query plan) instead of the text version otherwise sent. Note that if that new header is not provided, then the query plan continues to be send in the previous prettified text version.

• Fix some potentially incorrect query plans with @requires when some dependencies are involved. (#2726)

  In some rare case of @requires, an over-eager optimisation was incorrectly considering that a dependency between 2 subgraph fetches was unnecessary, leading to doing 2 subgraphs queries in parallel when those should be done sequentially (because the 2nd query rely on results from the 1st one). This effectively resulted in the required fields not being provided (the consequence of which depends a bit on the resolver detail, but if the resolver expected the required fields to be populated (as they should), then this could typically result in a message of the form GraphQLError: Cannot read properties of null).

• Updated dependencies [203b0a44]:

  • @​apollo/query-planner@​2.5.4
  • @​apollo/composition@​2.5.4
  • @​apollo/federation-internals@​2.5.4

@​apollo/gateway@​2.5.3

Patch Changes

• Fix execution error in some cases where aliases are used and some values are null. (#2716)

  The error would manifest itself as an INTERNAL_SERVER_ERROR with a message of the form Cannot read properties of null.

• Updated dependencies [4b9a512b, c6e0e76d, 1add932c, 6f1fddb2]:

  • @​apollo/composition@​2.5.3
  • @​apollo/federation-internals@​2.5.3
  • @​apollo/query-planner@​2.5.3

@​apollo/gateway@​2.5.2

Patch Changes

• Remove extraneous call to span.setStatus() on a span which has already ended. (#2697)

  In cases where a subgraph responded with an error, we would sometimes try to set the status of a span which had already ended. This resulted in a warning log to the console (but no effect otherwise). This warning should no longer happen.

• Fix fallbackPollIntervalInMs behavior. (#2709)

  The fallbackPollIntervalInMs serves 2 purposes:

  • it allows users to provide an Uplink poll interval if Uplink doesn't provide one
  • it allows users to use a longer poll interval that what's prescribed by Uplink

  The second bullet is how the configuration option is documented, but not how it was previously implemented. This change corrects the behavior to respect this configuration if it's provided AND is longer than the Uplink interval.

... (truncated)

Changelog

Sourced from @​apollo/gateway's changelog.

2.5.4

Patch Changes

• Adds header to change the format of exposed query plans, and allows formatting it as json. (#2724)

  When the gateway is configured to allow it, adding the Apollo-Query-Plan-Experimental header to a request already allowed a "prettified" text version of the query plan used for the query is returned in the response extension. This changes adds support for a new (optional) accompanying header, Apollo-Query-Plan-Experimental-Format, which can be set to the value "internal" to have the query plan returned as a json object (that correspond to the internal representation of that query plan) instead of the text version otherwise sent. Note that if that new header is not provided, then the query plan continues to be send in the previous prettified text version.

• Fix some potentially incorrect query plans with @requires when some dependencies are involved. (#2726)

  In some rare case of @requires, an over-eager optimisation was incorrectly considering that a dependency between 2 subgraph fetches was unnecessary, leading to doing 2 subgraphs queries in parallel when those should be done sequentially (because the 2nd query rely on results from the 1st one). This effectively resulted in the required fields not being provided (the consequence of which depends a bit on the resolver detail, but if the resolver expected the required fields to be populated (as they should), then this could typically result in a message of the form GraphQLError: Cannot read properties of null).

• Updated dependencies [203b0a44]:

  • @​apollo/query-planner@​2.5.4
  • @​apollo/composition@​2.5.4
  • @​apollo/federation-internals@​2.5.4

2.5.3

Patch Changes

• Fix execution error in some cases where aliases are used and some values are null. (#2716)

  The error would manifest itself as an INTERNAL_SERVER_ERROR with a message of the form Cannot read properties of null.

• Updated dependencies [4b9a512b, c6e0e76d, 1add932c, 6f1fddb2]:

  • @​apollo/composition@​2.5.3
  • @​apollo/federation-internals@​2.5.3
  • @​apollo/query-planner@​2.5.3

2.5.2

Patch Changes

• Remove extraneous call to span.setStatus() on a span which has already ended. (#2697)

  In cases where a subgraph responded with an error, we would sometimes try to set the status of a span which had already ended. This resulted in a warning log to the console (but no effect otherwise). This warning should no longer happen.

• Fix fallbackPollIntervalInMs behavior. (#2709)

  The fallbackPollIntervalInMs serves 2 purposes:

  • it allows users to provide an Uplink poll interval if Uplink doesn't provide one
  • it allows users to use a longer poll interval that what's prescribed by Uplink

... (truncated)

Commits

• d8930ec Version Packages (#2751)
• 203b0a4 Fix incorrect removal of dependencies between groups in some rare @requires...
• 7a1f299 feat: include query plan object in extensions (#2724)
• 7634e38 Version Packages (#2730)
• e963de1 Fix "TypeError: Cannot read properties of null" (#2716)
• d5241e8 Version Packages (#2699)
• aa5bd59 Fix fallbackPollIntervalInMs behavior (#2709)
• 06dbdc2 Remove extraneous span.setStatus() following span.end() (#2697)
• b2938ff Version Packages (#2690)
• b9052fd Reapply #2639 (with fix for #2680) (#2687)
• 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)