search

aerogear / keycloak-connect-graphql

Add Keyloak Authentication and Authorization to your GraphQL server.
Apache License 2.0
155 stars 22 forks source link

chore(deps): update dependency apollo-server-express to v2.19.1 #106

Closed renovate[bot] closed 3 years ago

renovate[bot] commented 4 years ago

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
apollo-server-express 2.14.2 -> 2.19.1 age adoption passing confidence

Release Notes

apollographql/apollo-server ### [`v2.19.1`](https://togithub.com/apollographql/apollo-server/blob/master/CHANGELOG.md#v2191) [Compare Source](https://togithub.com/apollographql/apollo-server/compare/4c6d16f14ab735ba0361057d75e51adb6790426c...7e543ed5540ce5995b30b1bb2a7b54367fd49d6f) - `apollo-server-core`: The `debugPrintReports` option to `ApolloServerPluginUsageReporting` now prints traces as well. [PR #​4805](https://togithub.com/apollographql/apollo-server/pull/4805) ### [`v2.19.0`](https://togithub.com/apollographql/apollo-server/blob/master/CHANGELOG.md#v2190) [Compare Source](https://togithub.com/apollographql/apollo-server/compare/a4786b2fbfd2ae60e1bf1cfaaced3f9c8d174a93...4c6d16f14ab735ba0361057d75e51adb6790426c) - `apollo-server-testing`: types: Allow generic `variables` usage of `query` and `mutate` functions. [PR #​4383](https://togithub.com/apollograpqh/apollo-server/pull/4383) - `apollo-server-express`: Export the `GetMiddlewareOptions` type. [PR #​4599](https://togithub.com/apollograpqh/apollo-server/pull/4599) - `apollo-server-lambda`: Fix file uploads - ignore base64 decoding for multipart queries. [PR #​4506](https://togithub.com/apollographql/apollo-server/pull/4506) - `apollo-server-core`: Do not send operation documents that cannot be executed to Apollo Studio. Instead, information about these operations will be combined into one "operation" for parse failures, one for validation failures, and one for unknown operation names. ### [`v2.18.2`](https://togithub.com/apollographql/apollo-server/blob/master/CHANGELOG.md#v2182) [Compare Source](https://togithub.com/apollographql/apollo-server/compare/83e22003c717e93bc57655d4849b0833369f1152...a4786b2fbfd2ae60e1bf1cfaaced3f9c8d174a93) - `apollo-server-core`: Explicitly include `lru-cache` dependency in `apollo-server-core`'s dependencies. [PR #​4600](https://togithub.com/apollographql/apollo-server/pull/4600) ### [`v2.18.1`](https://togithub.com/apollographql/apollo-server/blob/master/CHANGELOG.md#v2181) [Compare Source](https://togithub.com/apollographql/apollo-server/compare/2aab7fd973bf352a0de28b2385dbad4be7c7fabc...83e22003c717e93bc57655d4849b0833369f1152) - `apollo-server-core`: Fix support for legacy option `engine: {logger}`, broken in v2.18.0. [PR #​4588](https://togithub.com/apollographql/apollo-server/pull/4588) - `apollo-server-plugin-base`: The `ApolloServerPlugin` TypeScript type does not need to extend `AnyFunctionMap`, which was an unnecessary change in v2.18.0. [PR #​4588](https://togithub.com/apollographql/apollo-server/pull/4588) - `apollo-server-core`: Improve a usage reporting error which occurs when you use Apollo Server in an unsupported way. [PR #​4588](https://togithub.com/apollographql/apollo-server/pull/4588) - `apollo-server-core`: Fix typo in error message for unparsable/invalid schemas provided via `overrideReportedSchema`. [PR #​4581](https://togithub.com/apollographql/apollo-server/pull/4581) ### [`v2.18.0`](https://togithub.com/apollographql/apollo-server/blob/master/CHANGELOG.md#v2180) [Compare Source](https://togithub.com/apollographql/apollo-server/compare/2db096051fc5bad822c0d37b530c792da39eb6f3...2aab7fd973bf352a0de28b2385dbad4be7c7fabc) - `apollo-server-core`: When Apollo Server is configured with an Apollo API key, the URLs it uses to connect to Apollo's servers have changed. If the environment in which you run your servers requires you to explicitly allow connections by domain, you will need to add the new domain names. Usage reporting previously connected to and now connects to ; schema reporting previously connected to and now connects to . [PR #​4453](https://togithub.com/apollographql/apollo-server/pull/4453) - Apollo Server's support for communicating with Apollo’s commercial products has been refactored into three separate plugins exported from `apollo-server-core` (for usage reporting, schema reporting, and inline tracing), configured using the standard `plugins` option. The `engine` option continues to work for backwards compatibility in the 2.x series; support for `engine` will be deprecated in Apollo Server 3.x. Full details are available in [the migration guide](https://www.apollographql.com/docs/apollo-server/migration-engine-plugins/). [PR #​4453](https://togithub.com/apollographql/apollo-server/pull/4453) - To consistently support tracing, inline tracing is enabled by default on federated implementing services, even when an Apollo API key is provided. Previously it was not enabled when an API key was provided. You can disable it with `ApolloServerPluginInlineTraceDisabled`. [PR #​4453](https://togithub.com/apollographql/apollo-server/pull/4453) - The `apollo-engine-reporting` npm package has been obsoleted and will no longer receive updates. [PR #​4453](https://togithub.com/apollographql/apollo-server/pull/4453) - The `apollo-engine-reporting-protobuf` package has been renamed to `apollo-reporting-protobuf`. No new versions of the old package will be published. [PR #​4453](https://togithub.com/apollographql/apollo-server/pull/4453) - Implementations of `ApolloServer` for serverless frameworks such as Lambda now override the `serverlessFramework()` method to return true. We have changed our own integrations, but other implementations that extend `ApolloServer` which need this behavior should do the same. Support for `engine.sendReportsImmediately` will be dropped in Apollo Server 3.x. [PR #​4453](https://togithub.com/apollographql/apollo-server/pull/4453) - The `GraphQLServiceContext` type passed to the plugin serverWillStart method now contains `apollo` and `serverlessFramework` values. [PR #​4453](https://togithub.com/apollographql/apollo-server/pull/4453) - `apollo-server-core` / `apollo-server-plugin-base`: The request pipeline plugin API now supports a `serverWillStop` lifecycle hook. [PR #​4453](https://togithub.com/apollographql/apollo-server/pull/4453) - `apollo-server-core`: Previously, the usage reporting functionality registered one-shot handlers for the `SIGINT` and `SIGTERM` signals, which it used to send one final usage report before re-sending the signal to itself to continue shutdown. These signals handlers were installed by default if you enabled usage or schema reporting, and could be disabled by passing `engine.handleSignals: false`. Now, termination signal handling is the responsibility of Apollo Server as a whole rather than something specific to usage reporting. Apollo Server itself now registers these one-shot signal handlers, which trigger `ApolloServer.stop()`. This allows any plugin that implements the new `serverWillStop` callback to hook into shutdown logic, not just the usage reporting code. Similarly to before, these signal handlers are registered by default but can be disabled by via an option. We've changed the option name to `stopOnTerminationSignals: false` as it is more explicit about the behavior. [PR #​4453](https://togithub.com/apollographql/apollo-server/pull/4453) - `apollo-server-core`: The default logger implementation (if you don't specify your own `logger` or specify `debug`) now logs at the INFO level instead of the WARN level. The main effect is on a few built-in plugins which log one INFO message at startup; if a custom plugin logs at the INFO level then those messages will be visible by default as well. [PR #​4453](https://togithub.com/apollographql/apollo-server/pull/4453) - `apollo-server-core`: Parse and validate any schema passed via `overrideReportedSchema` to the schema reporting plugin, and throw accordingly on unparsable or invalid schemas. - Using Apollo Server from TypeScript now requires TypeScript 3.8 due to the use of the `import type` and `export type` directives. (If this proves to be a major problem we can revert this choice, but it makes it easier for us to ensure that certain large dependencies are only loaded when needed.) [PR #​4453](https://togithub.com/apollographql/apollo-server/pull/4453) - Updated `@apollographql/graphql-playground-react` to 1.7.33 to include [an upstream fix](https://togithub.com/apollographql/graphql-playground/commit/1c102692bfbb717688827204186c15cb92629b3a). [PR #​4550](https://togithub.com/apollographql/apollo-server/pull/4550) ### [`v2.17.0`](https://togithub.com/apollographql/apollo-server/blob/master/CHANGELOG.md#v2170) [Compare Source](https://togithub.com/apollographql/apollo-server/compare/128c1b0930ff789c55ac258a0b579f18c6d5312b...2db096051fc5bad822c0d37b530c792da39eb6f3) - subscriptions: Fix bug which prevented `installSubscriptionHandlers` from accepting a `websocket.Server` (as intended in [PR #​1966](https://togithub.com/apollographql/apollo-server/pull/1966)) and also added support for other `http.Server` variations (e.g., Tls). [Issue #​4198](https://togithub.com/apollographql/apollo-server/issues/4198) [PR #​4200](https://togithub.com/apollographql/apollo-server/pull/4200) ### [`v2.16.1`](https://togithub.com/apollographql/apollo-server/blob/master/CHANGELOG.md#v2161) [Compare Source](https://togithub.com/apollographql/apollo-server/compare/f4cfb22b93913c98e54c638ae39f39ed153daf66...128c1b0930ff789c55ac258a0b579f18c6d5312b) - This release only includes patch updates to dependencies. ### [`v2.16.0`](https://togithub.com/apollographql/apollo-server/blob/master/CHANGELOG.md#v2160) [Compare Source](https://togithub.com/apollographql/apollo-server/compare/8cfc947ed56fa3f32b82b32b4bcca53470712984...f4cfb22b93913c98e54c638ae39f39ed153daf66) - `apollo-server-fastify`: Pass Fastify's `request` and `reply` objects into the `context` function, which previously had been receiving nothing. [Issue #​3156](https://togithub.com/apollographql/apollo-server/issues/3156) \[PR [#​3895](https://togithub.com/apollographql/apollo-server/issues/3895)([#​3895](https://togithub.com/apollographql/apollo-server/pull/3895)) - `apollo-server-lamdbda`: Automatically decode payloads which are Base64-encoded when the `isBase64Encoded` boolean is present on Lambda `event` payloads. [PR #​4311](https://togithub.com/apollographql/apollo-server/pull/4311) ### [`v2.15.1`](https://togithub.com/apollographql/apollo-server/blob/master/CHANGELOG.md#v2151) [Compare Source](https://togithub.com/apollographql/apollo-server/compare/6f7bdc6099669728926ea88f6317cb17cc6a4b43...8cfc947ed56fa3f32b82b32b4bcca53470712984) - The default branch of the repository has been changed to `main`. As this changed a number of references in the repository's `package.json` and `README.md` files (e.g., for badges, links, etc.), this necessitates a release to publish those changes to npm. [PR #​4302](https://togithub.com/apollographql/apollo-server/pull/4302) ### [`v2.15.0`](https://togithub.com/apollographql/apollo-server/blob/master/CHANGELOG.md#v2150) [Compare Source](https://togithub.com/apollographql/apollo-server/compare/1824b55f68531b01c2ed965ea44a250e16e5e46b...6f7bdc6099669728926ea88f6317cb17cc6a4b43) - `apollo-engine-reporting`: Added a `reportTiming` API to allow trace reporting to be enabled or disabled on a per request basis. The option takes either a boolean or a predicate function that takes a [`GraphQLRequestContextDidResolveOperation`](https://togithub.com/apollographql/apollo-server/blob/a926b7eedbb87abab2ec70fb03d71743985cb18d/packages/apollo-server-types/src/index.ts#L185-L190) or [`GraphQLRequestContextDidEncounterErrors`](https://togithub.com/apollographql/apollo-server/blob/a926b7eedbb87abab2ec70fb03d71743985cb18d/packages/apollo-server-types/src/index.ts#L191-L195) and returns a boolean. If the boolean is false the request will not be instrumented for tracing and no trace will be sent to Apollo Graph Manager. The default is `true` so all traces will get instrumented and sent, which is the same as the previous default behavior. [PR #​3918](https://togithub.com/apollographql/apollo-server/pull/3918) - `apollo-engine-reporting`: Removed `GraphQLServerOptions.reporting`. It isn't known whether a trace will be reported at the beginning of the request because of the above change. We believe this field was only used internally within Apollo Server; let us know if this is a problem and we can suggest alternatives. Additionally, the field `requestContext.metrics.captureTraces` is now initialized later in the request pipeline. [PR #​3918](https://togithub.com/apollographql/apollo-server/pull/3918) - `apollo-engine-reporting`: Make Apollo Server throw if schema reporting is enabled for a gateway or federated service. [PR #​4246](https://togithub.com/apollographql/apollo-server/pull/4246) - `apollo-engine-reporting`: Remove the `experimental_` prefix from schema reporting options, and specifically rename `experimental_schemaReporting` option name to `reportSchema`. (The old option names remain functional, but are deprecated.) [PR #​4236](https://togithub.com/apollographql/apollo-server/pull/4236) ### [`v2.14.5`](https://togithub.com/apollographql/apollo-server/blob/master/CHANGELOG.md#v2145) [Compare Source](https://togithub.com/apollographql/apollo-server/compare/0ddf084f8c8a107774ce49e534bb2733b7e56c5b...1824b55f68531b01c2ed965ea44a250e16e5e46b) - `apollo-engine-reporting`: Make Apollo Server throw if schema reporting is enabled for a gateway or federated service. [PR #​4246](https://togithub.com/apollographql/apollo-server/pull/4246) ### [`v2.14.4`](https://togithub.com/apollographql/apollo-server/blob/master/CHANGELOG.md#v2144) [Compare Source](https://togithub.com/apollographql/apollo-server/compare/724806fed355dfcb9203032bcf9d7ec74e8529cd...0ddf084f8c8a107774ce49e534bb2733b7e56c5b) - `apollo-engine-reporting`: Add environment variable `APOLLO_SCHEMA_REPORTING` that can enable schema reporting. If `experimental__schemaReporting` is set it will override the environment variable. [PR #​4206](https://togithub.com/apollographql/apollo-server/pull/4206) - `apollo-engine-reporting`: The schema reporting URL has been changed to use the new dedicated sub-domain `https://edge-server-reporting.api.apollographql.com`. [PR #​4232](https://togithub.com/apollographql/apollo-server/pull/4232) - `apollo-server-core`: Though Apollo Server **is not affected** due to the way it is integrated, in response to [an upstream security advisory for GraphQL Playground](https://togithub.com/prisma-labs/graphql-playground/security/advisories/GHSA-4852-vrh7-28rf) we have published [the same patch](https://togithub.com/prisma-labs/graphql-playground/commit/bf1883db538c97b076801a60677733816cb3cfb7) on our `@apollographql/graphql-playground-html` fork and bumped Apollo Server to use it. Again, this was done out of an **abundance of caution** since the way that Apollo Server utilizes `renderPlaygroundPage` is _not_ vulnerable as it does not allow per-request Playground configuration that could allow interpolation of user-input. [PR #​4231](https://togithub.com/apollographql/apollo-server/pull/4231) ### [`v2.14.3`](https://togithub.com/apollographql/apollo-server/blob/master/CHANGELOG.md#v2143) [Compare Source](https://togithub.com/apollographql/apollo-server/compare/a17f26bf3ee2892f5c3751713cf59920049cc73a...724806fed355dfcb9203032bcf9d7ec74e8529cd) - This release only includes patch updates to dependencies.

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.

:no_bell: Ignore: Close this PR and you won't be reminded about this update again.

This PR has been generated by WhiteSource Renovate. View repository job log here.