apollographql/apollo-server
### [`v2.13.1`](https://togithub.com/apollographql/apollo-server/compare/e37384a49b2bf474eed0de3e9f4a1bebaeee64c7...05df0790346facb64d7bf76d4520f4ba734b114c)
[Compare Source](https://togithub.com/apollographql/apollo-server/compare/e37384a49b2bf474eed0de3e9f4a1bebaeee64c7...05df0790346facb64d7bf76d4520f4ba734b114c)
### [`v2.13.0`](https://togithub.com/apollographql/apollo-server/blob/master/CHANGELOG.md#v2130)
[Compare Source](https://togithub.com/apollographql/apollo-server/compare/71a3863f59f4ab2c9052c316479d94c6708c4309...e37384a49b2bf474eed0de3e9f4a1bebaeee64c7)
> [See complete versioning details.](https://togithub.com/apollographql/apollo-server/commit/e37384a49b2bf474eed0de3e9f4a1bebaeee64c7)
- Allow passing a `WebSocket.Server` to `ApolloServer.installSubscriptionHandlers`. [PR #2314](https://togithub.com/apollographql/apollo-server/pull/2314)
- `apollo-server-lambda`: Support file uploads on AWS Lambda [Issue #1419](https://togithub.com/apollographql/apollo-server/issues/1419) [Issue #1703](https://togithub.com/apollographql/apollo-server/issues/1703) [PR #3926](https://togithub.com/apollographql/apollo-server/pull/3926)
- `apollo-engine-reporting`: Fix inadvertant conditional formatting which prevented automated persisted query (APQ) hits and misses from being reported to Apollo Graph Manager. [PR #3986](https://togithub.com/apollographql/apollo-server/pull/3986)
- `apollo-engine-reporting`: Deprecate the `ENGINE_API_KEY` environment variable in favor of its new name, `APOLLO_KEY`. Continued use of `ENGINE_API_KEY` will result in deprecation warnings and support for it will be removed in a future major version. [#3923](https://togithub.com/apollographql/apollo-server/pull/3923)
- `apollo-engine-reporting`: Deprecated the `APOLLO_SCHEMA_TAG` environment variable in favor of its new name, `APOLLO_GRAPH_VARIANT`. Similarly, within the `engine` configuration object, the `schemaTag` property has been renamed `graphVariant`. The functionality remains otherwise unchanged, but their new names mirror the name used within Apollo Graph Manager. Continued use of the now-deprecated names will result in deprecation warnings and support will be dropped completely in the next "major" update. To avoid misconfiguration, a runtime error will be thrown if _both_ new and deprecated names are set. [PR #3855](https://togithub.com/apollographql/apollo-server/pull/3855)
- `apollo-engine-reporting-protobuf`: **(This is a breaking change only if you directly depend on `apollo-engine-reporting-protobuf`.)** Drop legacy fields that were never used by `apollo-engine-reporting`. Added new fields `StatsContext` to allow `apollo-server` to send summary stats instead of full traces, and renamed `FullTracesReport` to `Report` and `Traces` to `TracesAndStats` since reports now can include stats as well as traces.
### [`v2.12.0`](https://togithub.com/apollographql/apollo-server/blob/master/CHANGELOG.md#v2120)
[Compare Source](https://togithub.com/apollographql/apollo-server/compare/056f083ddaf116633e6f759a2b3d69248bb18f66...71a3863f59f4ab2c9052c316479d94c6708c4309)
> [See complete versioning details.](https://togithub.com/apollographql/apollo-server/commit/71a3863f59f4ab2c9052c316479d94c6708c4309)
- `apollo-server-core`: Support providing a custom logger implementation (e.g. [`winston`](https://npm.im/winston), [`bunyan`](https://npm.im/bunyan), etc.) to capture server console messages. Though there has historically been limited output from Apollo Server, some messages are important to capture in the larger context of production logging facilities or can benefit from using more advanced structure, like JSON-based logging. This also introduces a `logger` property to the `GraphQLRequestContext` that is exposed to plugins, making it possible for plugins to leverage the same server-level logger, and allowing implementors to create request-specific log contexts, if desired. When not provided, these will still output to `console`. [PR #3894](https://togithub.com/apollographql/apollo-server/pull/3894)
- `apollo-server-core`: When operating in gateway mode using the `gateway` property of the Apollo Server constructor options, the failure to initialize a schema during initial start-up, e.g. connectivity problems, will no longer result in the federated executor from being assigned when the schema eventually becomes available. This precludes a state where the gateway may never become available to serve federated requests, even when failure conditions are no longer present. [PR #3811](https://togithub.com/apollographql/apollo-server/pull/3811)
- `apollo-server-core`: Prevent a condition which prefixed an error message on each request when the initial gateway initialization resulted in a Promise-rejection which was memoized and re-prepended with `Invalid options provided to ApolloServer:` on each request. [PR #3811](https://togithub.com/apollographql/apollo-server/pull/3811)
- `apollo-server-express`: Disable the automatic inclusion of the `x-powered-by: express` header. [PR #3821](https://togithub.com/apollographql/apollo-server/pull/3821)
- `apollo-engine-reporting`: Avoid creating new arrays when building trace trees. [PR #3479](https://togithub.com/apollographql/apollo-server/pull/3479)
- `apollo-server-core`: Bump `graphql` `peerDependencies` range to include `^15.0.0`. [PR #3944](https://togithub.com/apollographql/apollo-server/pull/3944)
apollographql/graphql-tools
### [`v4.0.8`](https://togithub.com/apollographql/graphql-tools/compare/v4.0.7...v4.0.8)
[Compare Source](https://togithub.com/apollographql/graphql-tools/compare/v4.0.7...v4.0.8)
Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
:ghost: 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 contains the following updates:
2.11.0
->2.13.1
4.0.7
->4.0.8
Release Notes
apollographql/apollo-server
### [`v2.13.1`](https://togithub.com/apollographql/apollo-server/compare/e37384a49b2bf474eed0de3e9f4a1bebaeee64c7...05df0790346facb64d7bf76d4520f4ba734b114c) [Compare Source](https://togithub.com/apollographql/apollo-server/compare/e37384a49b2bf474eed0de3e9f4a1bebaeee64c7...05df0790346facb64d7bf76d4520f4ba734b114c) ### [`v2.13.0`](https://togithub.com/apollographql/apollo-server/blob/master/CHANGELOG.md#v2130) [Compare Source](https://togithub.com/apollographql/apollo-server/compare/71a3863f59f4ab2c9052c316479d94c6708c4309...e37384a49b2bf474eed0de3e9f4a1bebaeee64c7) > [See complete versioning details.](https://togithub.com/apollographql/apollo-server/commit/e37384a49b2bf474eed0de3e9f4a1bebaeee64c7) - Allow passing a `WebSocket.Server` to `ApolloServer.installSubscriptionHandlers`. [PR #2314](https://togithub.com/apollographql/apollo-server/pull/2314) - `apollo-server-lambda`: Support file uploads on AWS Lambda [Issue #1419](https://togithub.com/apollographql/apollo-server/issues/1419) [Issue #1703](https://togithub.com/apollographql/apollo-server/issues/1703) [PR #3926](https://togithub.com/apollographql/apollo-server/pull/3926) - `apollo-engine-reporting`: Fix inadvertant conditional formatting which prevented automated persisted query (APQ) hits and misses from being reported to Apollo Graph Manager. [PR #3986](https://togithub.com/apollographql/apollo-server/pull/3986) - `apollo-engine-reporting`: Deprecate the `ENGINE_API_KEY` environment variable in favor of its new name, `APOLLO_KEY`. Continued use of `ENGINE_API_KEY` will result in deprecation warnings and support for it will be removed in a future major version. [#3923](https://togithub.com/apollographql/apollo-server/pull/3923) - `apollo-engine-reporting`: Deprecated the `APOLLO_SCHEMA_TAG` environment variable in favor of its new name, `APOLLO_GRAPH_VARIANT`. Similarly, within the `engine` configuration object, the `schemaTag` property has been renamed `graphVariant`. The functionality remains otherwise unchanged, but their new names mirror the name used within Apollo Graph Manager. Continued use of the now-deprecated names will result in deprecation warnings and support will be dropped completely in the next "major" update. To avoid misconfiguration, a runtime error will be thrown if _both_ new and deprecated names are set. [PR #3855](https://togithub.com/apollographql/apollo-server/pull/3855) - `apollo-engine-reporting-protobuf`: **(This is a breaking change only if you directly depend on `apollo-engine-reporting-protobuf`.)** Drop legacy fields that were never used by `apollo-engine-reporting`. Added new fields `StatsContext` to allow `apollo-server` to send summary stats instead of full traces, and renamed `FullTracesReport` to `Report` and `Traces` to `TracesAndStats` since reports now can include stats as well as traces. ### [`v2.12.0`](https://togithub.com/apollographql/apollo-server/blob/master/CHANGELOG.md#v2120) [Compare Source](https://togithub.com/apollographql/apollo-server/compare/056f083ddaf116633e6f759a2b3d69248bb18f66...71a3863f59f4ab2c9052c316479d94c6708c4309) > [See complete versioning details.](https://togithub.com/apollographql/apollo-server/commit/71a3863f59f4ab2c9052c316479d94c6708c4309) - `apollo-server-core`: Support providing a custom logger implementation (e.g. [`winston`](https://npm.im/winston), [`bunyan`](https://npm.im/bunyan), etc.) to capture server console messages. Though there has historically been limited output from Apollo Server, some messages are important to capture in the larger context of production logging facilities or can benefit from using more advanced structure, like JSON-based logging. This also introduces a `logger` property to the `GraphQLRequestContext` that is exposed to plugins, making it possible for plugins to leverage the same server-level logger, and allowing implementors to create request-specific log contexts, if desired. When not provided, these will still output to `console`. [PR #3894](https://togithub.com/apollographql/apollo-server/pull/3894) - `apollo-server-core`: When operating in gateway mode using the `gateway` property of the Apollo Server constructor options, the failure to initialize a schema during initial start-up, e.g. connectivity problems, will no longer result in the federated executor from being assigned when the schema eventually becomes available. This precludes a state where the gateway may never become available to serve federated requests, even when failure conditions are no longer present. [PR #3811](https://togithub.com/apollographql/apollo-server/pull/3811) - `apollo-server-core`: Prevent a condition which prefixed an error message on each request when the initial gateway initialization resulted in a Promise-rejection which was memoized and re-prepended with `Invalid options provided to ApolloServer:` on each request. [PR #3811](https://togithub.com/apollographql/apollo-server/pull/3811) - `apollo-server-express`: Disable the automatic inclusion of the `x-powered-by: express` header. [PR #3821](https://togithub.com/apollographql/apollo-server/pull/3821) - `apollo-engine-reporting`: Avoid creating new arrays when building trace trees. [PR #3479](https://togithub.com/apollographql/apollo-server/pull/3479) - `apollo-server-core`: Bump `graphql` `peerDependencies` range to include `^15.0.0`. [PR #3944](https://togithub.com/apollographql/apollo-server/pull/3944)apollographql/graphql-tools
### [`v4.0.8`](https://togithub.com/apollographql/graphql-tools/compare/v4.0.7...v4.0.8) [Compare Source](https://togithub.com/apollographql/graphql-tools/compare/v4.0.7...v4.0.8)Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
:ghost: Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by WhiteSource Renovate. View repository job log here.