@apollo/[email protected]

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.

@apollo/[email protected]

Patch Changes

• Updated dependencies [72f568e]:
  • @apollo/[email protected]

@apollo/[email protected]

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)

@apollo/[email protected]

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.

Patch Changes

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

• Updated dependencies [869ec98, 9bd7748, 63dc50f, fe68c1b, e9a0d6e]:

  • @apollo/[email protected]

@apollo/[email protected]

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

@apollo/[email protected]

Patch Changes

• #7717 681bdd0dc Thanks @renovate! - Update graphql-http dependency

• Updated dependencies [07585fe39, 4fac1628c]:

  • @apollo/[email protected]

@apollo/[email protected]

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, [email protected], 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.

@apollo/[email protected]

Patch Changes

• Updated dependencies [ddce036e1]:
  • @apollo/[email protected]

@apollo/[email protected]

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

@apollo/[email protected]

Patch Changes

• Updated dependencies [a1c725eaf]:
  • @apollo/[email protected]