fix(deps): update all apollo server non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@apollo/server (source)	4.8.1 -> 4.10.4
@types/node (source)	18.17.0 -> 18.19.41
apollo-server (source)	3.12.0 -> 3.13.0
apollo-server (source)	2.26.1 -> 2.26.2
graphql	16.7.1 -> 16.9.0
graphql	15.8.0 -> 15.9.0

---

Release Notes

apollographql/apollo-server (@​apollo/server)

v4.10.4

Compare Source

Patch Changes

• #​7871 18a3827 Thanks @​tninesling! - Subscription heartbeats are initialized prior to awaiting subscribe(). This allows long-running setup to happen in the returned Promise without the subscription being terminated prior to resolution.

v4.10.3

Compare Source

Patch Changes

• #​7866 5f335a5 Thanks @​tninesling! - Catch errors thrown by subscription generators, and gracefully clean up the subscription instead of crashing.

v4.10.2

Compare Source

Patch Changes

• #​7849 c7e514c Thanks @​TylerBloom! - In the subscription callback server plugin, terminating a subscription now immediately closes the internal async generator. This avoids that generator existing after termination and until the next message is received.

v4.10.1

Compare Source

Patch Changes

• #​7843 72f568e Thanks @​bscherlein! - Improves timing of the willResolveField end hook on fields which return Promises resolving to Arrays. This makes the use of the setCacheHint method more reliable.

v4.10.0

Compare Source

Minor Changes

• #​7786 869ec98 Thanks @​ganemone! - Restore missing v1 skipValidation option as dangerouslyDisableValidation. Note that enabling this option exposes your server to potential security and unexpected runtime issues. Apollo will not support issues that arise as a result of using this option.

• #​7803 e9a0d6e Thanks @​favna! - allow stringifyResult to return a Promise<string>

  Users who implemented the stringifyResult hook can now expect error responses to be formatted with the hook as well. Please take care when updating to this version to ensure this is the desired behavior, or implement the desired behavior accordingly in your stringifyResult hook. This was considered a non-breaking change as we consider that it was an oversight in the original PR that introduced stringifyResult hook.

Patch Changes

• #​7793 9bd7748 Thanks @​bnjjj! - General availability of subscription callback protocol

• #​7799 63dc50f Thanks @​stijnbe! - Fix type of ApolloServerPluginUsageReporting reportTimer

• #​7740 fe68c1b Thanks @​barnisanov! - Uninstalled body-parser and used express built-in body-parser functionality instead(mainly the json middleware)

v4.9.5

Compare Source

Patch Changes

• #​7741 07585fe39 Thanks @​mayakoneval! - Pin major releases of embeddable Explorer & Sandbox code.

• #​7769 4fac1628c Thanks @​cwikla! - Change SchemaReporter.pollTimer from being a NodeJS.Timer to a NodeJS.Timeout

v4.9.4

Compare Source

Patch Changes

• #​7747 ddce036e1 Thanks @​trevor-scheer! - The minimum version of graphql officially supported by Apollo Server 4 as a peer dependency, v16.6.0, contains a serious bug that can crash your Node server. This bug is fixed in the immediate next version, graphql@16.7.0, and we strongly encourage you to upgrade your installation of graphql to at least v16.7.0 to avoid this bug. (For backwards compatibility reasons, we cannot change Apollo Server 4's minimum peer dependency, but will change it when we release Apollo Server 5.)

  Apollo Server 4 contained a particular line of code that makes triggering this crashing bug much more likely. This line was already removed in Apollo Server v3.8.2 (see #​6398) but the fix was accidentally not included in Apollo Server 4. We are now including this change in Apollo Server 4, which will reduce the likelihood of hitting this crashing bug for users of graphql v16.6.0. That said, taking this @apollo/server upgrade does not prevent this bug from being triggered in other ways, and the real fix to this crashing bug is to upgrade graphql.

v4.9.3

Compare Source

Patch Changes

• a1c725eaf Thanks @​trevor-scheer! - Ensure API keys are valid header values on startup

  Apollo Server previously performed no sanitization or validation of API keys on startup. In the case that an API key was provided which contained characters that are invalid as header values, Apollo Server could inadvertently log the API key in cleartext.

  This only affected users who:

  • Provide an API key with characters that are invalid as header values
  • Use either schema or usage reporting
  • Use the default fetcher provided by Apollo Server or configure their own node-fetch fetcher

  Apollo Server now trims whitespace from API keys and validates that they are valid header values. If an invalid API key is provided, Apollo Server will throw an error on startup.

  For more details, see the security advisory:
  GHSA-j5g3-5c8r-7qfx

v4.9.2

Compare Source

Patch Changes

• #​7699 62e7d940d Thanks @​trevor-scheer! - Fix error path attachment for list items

  Previously, when errors occurred while resolving a list item, the trace builder would fail to place the error at the correct path and just default to the root node with a warning message:

  Could not find node with path x.y.1, defaulting to put errors on root node.

  This change places these errors at their correct paths and removes the log.

v4.9.1

Compare Source

Patch Changes

• #​7672 ebfde0007 Thanks @​trevor-scheer! - Add missing nonce on script tag for non-embedded landing page

v4.9.0

Compare Source

Minor Changes

• #​7617 4ff81ca50 Thanks @​trevor-scheer! - Introduce new ApolloServerPluginSubscriptionCallback plugin. This plugin implements the subscription callback protocol which is used by Apollo Router. This feature implements subscriptions over HTTP via a callback URL which Apollo Router registers with Apollo Server. This feature is currently in preview and is subject to change.

  You can enable callback subscriptions like so:

  import { ApolloServerPluginSubscriptionCallback } from '@​apollo/server/plugin/subscriptionCallback';
  import { ApolloServer } from '@​apollo/server';
  
  const server = new ApolloServer({
    // ...
    plugins: [ApolloServerPluginSubscriptionCallback()],
  });

  Note that there is currently no tracing or metrics mechanism in place for callback subscriptions. Additionally, this plugin "intercepts" callback subscription requests and bypasses some of Apollo Server's internals. The result of this is that certain plugin hooks (notably executionDidStart and willResolveField) will not be called when handling callback subscription requests or when sending subscription events.

  For more information on the subscription callback protocol, visit the docs:
  https://www.apollographql.com/docs/router/executing-operations/subscription-callback-protocol/

Patch Changes

• #​7659 4784f46fb Thanks @​renovate! - Update graphql-http dependency

apollographql/apollo-server (apollo-server)

v3.13.0

Compare Source

v3.12.1

Compare Source

graphql/graphql-js (graphql)

v16.9.0

Compare Source

v16.9.0 (2024-06-21)

New Feature 🚀

• #​4119 backport[v16]: Introduce "recommended" validation rules (@​benjie)
• #​4122 backport[v16]: Enable passing values configuration to GraphQLEnumType as a thunk (@​benjie)
• #​4124 backport[v16]: Implement OneOf Input Objects via @oneOf directive (@​benjie)

Committers: 1

• Benjie(@​benjie)

v16.8.2

Compare Source

v16.8.2 (2024-06-12)

Bug Fix 🐞* #​4022 fix: remove globalThis check and align with what bundlers can accept (@​JoviDeCroock)

Internal 🏠* #​4104 Fix publish scripts (@​benjie)

Committers: 2

• Benjie(@​benjie)
• Jovi De Croock(@​JoviDeCroock)

v16.8.1

Compare Source

v16.8.1 (2023-09-19)

Bug Fix 🐞

• #​3967 OverlappingFieldsCanBeMergedRule: Fix performance degradation (@​AaronMoat)

Committers: 1

• Aaron Moat(@​AaronMoat)

v16.8.0

Compare Source

v16.8.0 (2023-08-14)

New Feature 🚀

• #​3950 Support fourfold nested lists (@​gschulze)

Committers: 1

• Gunnar Schulze(@​gschulze)

---

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 was generated by Mend Renovate. View the repository job log.