fix(deps): update apollo graphql packages

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@apollo/gateway	2.3.3 -> 2.4.0
@apollo/server	4.4.1 -> 4.5.0
@apollo/subgraph	2.3.3 -> 2.4.0
@apollo/subgraph	2.2.3 -> 2.4.0

---

Release Notes

apollographql/federation (@​apollo/gateway)

v2.4.0

Compare Source

Minor Changes

• This change introduces a configurable query plan cache. This option allows (#​2385)
  developers to provide their own query plan cache like so:

  new ApolloGateway({
    queryPlannerConfig: {
      cache: new MyCustomQueryPlanCache(),
    },
  });
  

  The current default implementation is effectively as follows:

  import { InMemoryLRUCache } from "@​apollo/utils.keyvaluecache";
  
  const cache = new InMemoryLRUCache<string>({
    maxSize: Math.pow(2, 20) * 30,
    sizeCalculation<T>(obj: T): number {
      return Buffer.byteLength(JSON.stringify(obj), "utf8");
    },
  });
  

  TypeScript users should implement the QueryPlanCache type which is now
  exported by @apollo/query-planner:

  import { QueryPlanCache } from '@​apollo/query-planner';
  
  class MyCustomQueryPlanCache implements QueryPlanCache {
    // ...
  }
  

• Adds debug/testing query planner options (debug.bypassPlannerForSingleSubgraph) to bypass the query planning (#​2441)
  process for federated supergraph having only a single subgraph. The option is disabled by default, is not recommended
  for production, and is not supported (it may be removed later). It is meant for debugging/testing purposes.

Patch Changes

• Refactor the internal implementation of selection sets used by the query planner to decrease the code complexity and (#​2387)
  improve query plan generation performance in many cases.

• Optimises query plan generation for parts of queries that can statically be known to not cross across subgraphs (#​2449)

• Updated dependencies [260c357c, 7bc0f8e8, d4426ff9, a9385bdb, 1a555d98, ade7ceb8, 09382e74, cab383b2]:

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

v2.3.5

Compare Source

Patch Changes

• Updated dependencies [09382e74]:
  • @​apollo/query-planner@​2.3.5
  • @​apollo/composition@​2.3.5
  • @​apollo/federation-internals@​2.3.5

v2.3.4

Compare Source

Patch Changes

• Handle defaulted variables correctly during post-processing. (#​2443)

  Users who tried to use built-in conditional directives (skip/include) with defaulted variables and no variable provided would encounter an error thrown by operation post-processing saying that the variables weren't provided. The defaulted values went unaccounted for, so the operation would validate but then fail an assertion while resolving the conditional.

  With this change, defaulted variable values are now collected and provided to post-processing (with defaults being overwritten by variables that are actually provided).

• Updated dependencies [6e2d24b5]:

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

apollographql/apollo-server

v4.5.0

Compare Source

Minor Changes

• #​7431 7cc163ac8 Thanks @​mayakoneval! - In the Apollo Server Landing Page Local config, you can now automatically turn off autopolling on your endpoints as well as pass headers used to introspect your schema, embed an operation from a collection, and configure whether the endpoint input box is editable. In the Apollo Server Landing Page Prod config, you can embed an operation from a collection & we fixed a bug introduced in release 4.4.0

  Example of all new config options:

  const server = new ApolloServer({
    typeDefs,
    resolvers,
    plugins: [
      process.env.NODE_ENV === 'production'
        ? ApolloServerPluginLandingPageProductionDefault({
            graphRef: 'my-graph-id@my-graph-variant',
            collectionId: 'abcdef',
            operationId: '12345'
            embed: true,
            footer: false,
          })
        : ApolloServerPluginLandingPageLocalDefault({
            collectionId: 'abcdef',
            operationId: '12345'
            embed: {
              initialState: {
                pollForSchemaUpdates: false,
                sharedHeaders: {
                  "HeaderNeededForIntrospection": "ValueForIntrospection"
                },
              },
              endpointIsEditable: true,
            },
            footer: false,
          }),
    ],
  });
  
  

• #​7430 b694bb1dd Thanks @​mayakoneval! - We now send your @​apollo/server version to the embedded Explorer & Sandbox used in the landing pages for analytics.

Patch Changes

• #​7432 8cbc61406 Thanks @​mayakoneval! - Bug fix: TL;DR revert a previous change that stops passing includeCookies from the prod landing page config.

  Who was affected?

  Any Apollo Server instance that passes a graphRef to a production landing page with a non-default includeCookies value that does not match the Include cookies setting on your registered variant on studio.apollographql.com.

  How were they affected?

  From release 4.4.0 to this patch release, folks affected would have seen their Explorer requests being sent with cookies included only if they had set Include cookies on their variant. Cookies would not have been included by default.

apollographql/federation (@​apollo/subgraph)

v2.4.0

Compare Source

Patch Changes

• Optimises query plan generation for parts of queries that can statically be known to not cross across subgraphs (#​2449)

• Updated dependencies [260c357c, 7bc0f8e8, 1a555d98, cab383b2]:

  • @​apollo/federation-internals@​2.4.0

v2.3.5

Compare Source

Patch Changes

• Updated dependencies []:
  • @​apollo/federation-internals@​2.3.5

v2.3.4

Compare Source

Patch Changes

• Updated dependencies [6e2d24b5]:
  • @​apollo/federation-internals@​2.3.4

---

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.

[renovate]

⚠ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: sample/32-graphql-federation-schema-first/users-application/package-lock.json

Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

File name: sample/32-graphql-federation-schema-first/posts-application/package-lock.json

Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

File name: sample/32-graphql-federation-schema-first/gateway/package-lock.json

Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

File name: sample/31-graphql-federation-code-first/users-application/package-lock.json

Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

File name: sample/31-graphql-federation-code-first/posts-application/package-lock.json

Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

File name: sample/31-graphql-federation-code-first/gateway/package-lock.json

Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

File name: sample/23-graphql-code-first/package-lock.json

Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

File name: sample/22-graphql-prisma/package-lock.json

Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

File name: sample/12-graphql-schema-first/package-lock.json

Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

[coveralls]

Pull Request Test Coverage Report for Build 26a10991-c6d5-462b-8945-514e015605bd

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 92.656%

---

Totals
Change from base Build 47144a88-6f14-4e70-80c9-f0571ab5d310:	0.0%
Covered Lines:	6498
Relevant Lines:	7013

---

💛 - Coveralls