apollographql/apollo-server @apollo/server-integration-testsuite@4.2.0 on GitHub

#7171 37b3b7fb5 Thanks @glasser! - If a POST body contains a non-string operationName or a non-object variables or extensions, fail with status code 400 instead of ignoring the field.
In addition to being a reasonable idea, this provides more compliance with the "GraphQL over HTTP" spec.
This is a backwards incompatible change, but we are still early in the Apollo Server 4 adoption cycle and this is in line with the change already made in Apollo Server 4 to reject requests providing variables or extensions as strings. If this causes major problems for users who have already upgraded to Apollo Server 4 in production, we can consider reverting or partially reverting this change.

#7170 4ce738193 Thanks @trevor-scheer! - Update @apollo/utils packages to v2 (dropping node 12 support)
#7179 c8129c23f Thanks @renovate! - Fix a few tests to support (but not require) TypeScript 4.9.
#7171 37b3b7fb5 Thanks @glasser! - The integration test suite now incorporates the graphql-http package's audit suite for the "GraphQL over HTTP" specification.
#7183 46af8255c Thanks @glasser! - Apollo Server tries to detect if execution errors are variable coercion errors in order to give them a code extension of BAD_USER_INPUT rather than INTERNAL_SERVER_ERROR. Previously this would unconditionally set the code; now, it only sets the code if no code is already set, so that (for example) custom scalar parseValue methods can throw errors with specific codes. (Note that a separate graphql-js bug can lead to these extensions being lost; see graphql/graphql-js#3785 for details.)
Updated dependencies [4ce738193, 37b3b7fb5, b1548c1d6, 7ff96f533, 46af8255c]:
- @apollo/server@4.2.0