@apollo/server@4.1.0

Minor Changes

• 2a2d1e3b4 Thanks @glasser! - The cache-control HTTP response header set by the cache control plugin now properly reflects the cache policy of all operations in a batched HTTP request. (If you write the cache-control response header via a different mechanism to a format that the plugin would not produce, the plugin no longer writes the header.) For more information, see advisory GHSA-8r69-3cvp-wxc3.

• 2a2d1e3b4 Thanks @glasser! - Plugins processing multiple operations in a batched HTTP request now have a shared requestContext.request.http object. Changes to HTTP response headers and HTTP status code made by plugins operating on one operation can be immediately seen by plugins operating on other operations in the same HTTP request.

• 2a2d1e3b4 Thanks @glasser! - New field GraphQLRequestContext.requestIsBatched available to plugins.

@apollo/server-integration-testsuite@4.1.0

Minor Changes

• 2a2d1e3b4 Thanks @glasser! - The cache-control HTTP response header set by the cache control plugin now properly reflects the cache policy of all operations in a batched HTTP request. (If you write the cache-control response header via a different mechanism to a format that the plugin would not produce, the plugin no longer writes the header.) For more information, see advisory GHSA-8r69-3cvp-wxc3.

• 2a2d1e3b4 Thanks @glasser! - Plugins processing multiple operations in a batched HTTP request now have a shared requestContext.request.http object. Changes to HTTP response headers and HTTP status code made by plugins operating on one operation can be immediately seen by plugins operating on other operations in the same HTTP request.

• 2a2d1e3b4 Thanks @glasser! - New field GraphQLRequestContext.requestIsBatched available to plugins.

• #7114 c1651bfac Thanks @trevor-scheer! - Directly depend on Apollo Server rather than as a peer

Patch Changes

• Updated dependencies [2a2d1e3b4, 2a2d1e3b4, 2a2d1e3b4]:
  • @apollo/server@4.1.0

@apollo/server@4.0.5

Patch Changes

• #7104 15d8d65e0 Thanks @glasser! - New ApolloServerPluginSchemaReportingDisabled plugin which can override the APOLLO_SCHEMA_REPORTING environment variable.

• #7101 e4e7738be Thanks @glasser! - Manage memory more efficiently in the usage reporting plugin by allowing large objects to be garbage collected more quickly.

• #7101 e4e7738be Thanks @glasser! - The usage reporting plugin now defaults to a 30 second timeout for each attempt to send reports to Apollo Server instead of no timeout; the timeout can be adjusted with the new requestTimeoutMs option to ApolloServerPluginUsageReporting. (Apollo's servers already enforced a 30 second timeout, so this is unlikely to break any existing use cases.)

• #7104 15d8d65e0 Thanks @glasser! - It is now an error to combine a "disabled" plugin such as ApolloServerPluginUsageReportingDisabled with its enabled counterpart such as ApolloServerPluginUsageReporting.

@apollo/server-integration-testsuite@4.0.5

Patch Changes

• Updated dependencies [15d8d65e0, e4e7738be, e4e7738be, 15d8d65e0]:
  • @apollo/server@4.0.5

@apollo/usage-reporting-protobuf@4.0.1

Patch Changes

• #7095 72111f970 Thanks @alex-statsig! - Include main and module fields in package.json for build tools that look for them instead of exports.

@apollo/server@4.0.4

This version has no changes; @apollo/server and @apollo/server-integration-test are published with matching version numbers and we published a new version of @apollo/server-integration-test.

@apollo/server-integration-testsuite@4.0.4

Patch Changes

• #7080 540f3d97c Thanks @martinnabhan! - Recognize malformed JSON error messages from Next.js.

• Updated dependencies []:

  • @apollo/server@4.0.4

@apollo/server@4.0.3

Patch Changes

• #7073 e7f524eac Thanks @glasser! - Never interpret GET requests as batched. In previous versions of Apollo Server 4, a GET request whose body was a JSON array with N elements would be interpreted as a batch of the operation specified in the query string repeated N times. Now we just ignore the body for GET requests (like in Apollo Server 3), and never treat them as batched.

• #7071 0ed389ce8 Thanks @glasser! - Fix v4 regression: gateway implementations should be able to set HTTP response headers and the status code.

@apollo/server-integration-testsuite@4.0.3

Patch Changes

• #7073 e7f524eac Thanks @glasser! - Never interpret GET requests as batched. In previous versions of Apollo Server 4, a GET request whose body was a JSON array with N elements would be interpreted as a batch of the operation specified in the query string repeated N times. Now we just ignore the body for GET requests (like in Apollo Server 3), and never treat them as batched.

• #7071 0ed389ce8 Thanks @glasser! - Fix v4 regression: gateway implementations should be able to set HTTP response headers and the status code.

• Updated dependencies [e7f524eac, 0ed389ce8]:

  • @apollo/server@4.0.3

@apollo/server@4.0.2

Patch Changes

• #7035 b3f400063 Thanks @barryhagan! - Errors resulting from an attempt to use introspection when it is not enabled now have an additional validationErrorCode: 'INTROSPECTION_DISABLED' extension; this value is part of a new enum ApolloServerValidationErrorCode exported from @apollo/server/errors.