Bump apollo-server-core from 3.9.0 to 3.11.1

[dependabot]

Bumps apollo-server-core from 3.9.0 to 3.11.1.

Changelog

Sourced from apollo-server-core's changelog.

v3.11.1

• apollo-server-core: Follow-up to v3.11.0: make GraphQLRequestContext.requestIsBatched optional for better compatibility with older versions of @apollo/gateway.

v3.11.0

• ⚠️ SECURITY: The cache control plugin no longer sets the cache-control HTTP response header if the operation is part of a batched HTTP request. Previously, it would set the header to a value describing the cache policy of only one of the operations in the request, which could lead to data being unintentionally cached by proxies or clients. This bug was introduced in v3.0.0 and this fix restores the behavior of Apollo Server 2. (In Apollo Server 4 (specifically, @apollo/server@4.1.0 or newer), the features work properly together, setting the header based on the combined cache policy of all operations.) This could theoretically have led to data tagged as uncacheable being cached and potentially served to different users. More details are available at the security advisory.
• apollo-server-core: New field GraphQLRequestContext.requestIsBatched available to plugins.

v3.10.4

• apollo-server-core: Manage memory more efficiently in the usage reporting plugin by allowing large objects to be garbage collected more quickly. [PR #7106](apollographql/apollo-server#7106)
• apollo-server-core: 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.) [PR #7106](apollographql/apollo-server#7106)

v3.10.3

• apollo-server-core: Fix memory leak in usage reporting plugin. [Issue #6983](apollographql/apollo-server#6983) [PR #6999](https://github.com/apollographql/apollo-server/[Issue #6983](apollographql/apollo-server#6983)

v3.10.2

• apollo-server-fastify: Use return reply.send in handlers to match the pattern encouraged by Fastify 4 (although apollo-server-fastify@3 only works with Fastify 3). [PR #6798](apollographql/apollo-server#6798)
• apollo-datasource-rest@3.7.0: Add option memoizeGetRequests to disable GET cache [PR #6650](apollographql/apollo-server#6650) and [PR #6834](apollographql/apollo-server#6834)

v3.10.1

• ⚠️ SECURITY: The default landing page contained HTML to display a sample curl command which is made visible if the full landing page bundle could not be fetched from Apollo's CDN. The server's URL is directly interpolated into this command inside the browser from window.location.href. On some older browsers such as IE11, this value is not URI-encoded. On such browsers, opening a malicious URL pointing at an Apollo Router could cause execution of attacker-controlled JavaScript. In this release, the fallback page does not display a curl command. More details are available at the security advisory.
• Improve error message when both a graph ref and a graph variant are specified. [PR #6709](apollographql/apollo-server#6709)
• Fix the TypeScript declaration of the fieldLevelInstrumentation option to ApolloServerPluginUsageReporting to show that the function may return a number in addition to a boolean. This now matches the implementation and docs. [PR #6763](apollographql/apollo-server#6763)

v3.10.0

• Add document, variables, headers as an option in the ApolloServerPluginLandingPageLocalDefault plugins. The embedded version of Apollo Sandbox can now use these options as an initial state. [PR #6628](apollographql/apollo-server#6628)
• Add generateCacheKey to ApolloServerPluginResponseCache to allow for custom cache keys. [PR #6655](apollographql/apollo-server#6655)

Commits

• 6247d96 Release
• 538151b Release
• 69be2f7 Merge pull request from GHSA-8r69-3cvp-wxc3
• 40fcd3d Backport #7107 (docs: document new usage reporting option)
• f519e1d Release
• 8ca2c11 Backport usage reporting improvements #7101 to AS3 (#7106)
• 985c079 Release
• cd31e33 usage reporting: fix memory leak (#7000)
• ca928e4 Upgrade typescript version and resolve "unconstrained generic" errors (#6940)
• 40ed23f chore(deps): update dependency uuid to v9 (main) (#6883)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.