-
-
Notifications
You must be signed in to change notification settings - Fork 14
chore(deps): update apollo graphql packages #274
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov Report
@@ Coverage Diff @@
## master #274 +/- ##
=======================================
Coverage 62.19% 62.19%
=======================================
Files 95 95
Lines 1521 1521
Branches 152 152
=======================================
Hits 946 946
Misses 566 566
Partials 9 9 Continue to review full report at Codecov.
|
cd3560e to
4b7a5d7
Compare
4b7a5d7 to
b877c72
Compare
b877c72 to
caeaeda
Compare
caeaeda to
4521d1d
Compare
4521d1d to
5c3e8a0
Compare
5c3e8a0 to
6cab2cf
Compare
6cab2cf to
8b98c47
Compare
8b98c47 to
14566bf
Compare
14566bf to
a20ecff
Compare
a20ecff to
33a2b16
Compare
33a2b16 to
2e3ee6c
Compare
|
This PR contains the following updates:
3.1.1->3.1.41.6.2->1.6.62.6.3->2.6.101.2.12->1.2.141.0.18->1.0.201.1.11->1.1.131.5.15->1.5.171.0.18->1.0.202.9.0->2.17.01.3.2->1.3.42.10.1->2.11.0Release Notes
apollographql/react-apollo
v3.1.4Compare Source
v3.1.3Compare Source
onCompletedbeing called more often than necessary.@hwillson in 0901f4a
v3.1.2Compare Source
Bug Fixes
ssr: falseandssrMode: true.@maapteh in #3515
MockLink's brokennewDatafunction handling.@pawelkleczek in #3539
networkStatusfrom changingreadyat the end of pagination.@mu29 in #3514
apollographql/apollo-client
v1.6.6Compare Source
v1.6.5Compare Source
v1.6.3Compare Source
apollographql/apollo-link
v1.2.14Compare Source
v1.2.13Compare Source
apollographql/apollo-server
v2.17.0Compare Source
installSubscriptionHandlersfrom accepting awebsocket.Server(as intended in PR #1966) and also added support for otherhttp.Servervariations (e.g., Tls). Issue #4198 PR #4200v2.16.1Compare Source
v2.16.0Compare Source
apollo-server-fastify: Pass Fastify'srequestandreplyobjects into thecontextfunction, which previously had been receiving nothing. Issue #3156 [PR #3895(#3895)apollo-server-lamdbda: Automatically decode payloads which are Base64-encoded when theisBase64Encodedboolean is present on Lambdaeventpayloads. PR #4311v2.15.1Compare Source
main. As this changed a number of references in the repository'spackage.jsonandREADME.mdfiles (e.g., for badges, links, etc.), this necessitates a release to publish those changes to npm. PR #4302v2.15.0Compare Source
apollo-engine-reporting: Added areportTimingAPI 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 aGraphQLRequestContextDidResolveOperationorGraphQLRequestContextDidEncounterErrorsand 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 istrueso all traces will get instrumented and sent, which is the same as the previous default behavior. PR #3918apollo-engine-reporting: RemovedGraphQLServerOptions.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 fieldrequestContext.metrics.captureTracesis now initialized later in the request pipeline. PR #3918apollo-engine-reporting: Make Apollo Server throw if schema reporting is enabled for a gateway or federated service. PR #4246apollo-engine-reporting: Remove theexperimental_prefix from schema reporting options, and specifically renameexperimental_schemaReportingoption name toreportSchema. (The old option names remain functional, but are deprecated.) PR #4236v2.14.5Compare Source
apollo-engine-reporting: Make Apollo Server throw if schema reporting is enabled for a gateway or federated service. PR #4246v2.14.4Compare Source
apollo-engine-reporting: Add environment variableAPOLLO_SCHEMA_REPORTINGthat can enable schema reporting. Ifexperimental__schemaReportingis set it will override the environment variable. PR #4206apollo-engine-reporting: The schema reporting URL has been changed to use the new dedicated sub-domainhttps://edge-server-reporting.api.apollographql.com. PR #4232apollo-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 we have published the same patch on our@apollographql/graphql-playground-htmlfork and bumped Apollo Server to use it. Again, this was done out of an abundance of caution since the way that Apollo Server utilizesrenderPlaygroundPageis not vulnerable as it does not allow per-request Playground configuration that could allow interpolation of user-input. PR #4231v2.14.3Compare Source
v2.14.2Compare Source
v2.14.1Compare Source
apollo-server-testing: Ensure that user-provided context is cloned when usingcreateTestClient, per the instructions in the intergration testing section of the Apollo Server documentation. Issue #4170 PR #4175v2.14.0Compare Source
apollo-server-core/apollo-server-plugin-base: Add support forwillResolveFieldand corresponding end-handler withinexecutionDidStart. This brings the remaining bit of functionality that was previously only available fromgraphql-extensionsto the new plugin API. Thegraphql-extensionsAPI (which was never documented) will be deprecated in Apollo Server 3.x. To see the documentation for the request pipeline API, see its documentation. For more details, see the attached PR. PR #3988apollo-server-core: Deprecategraphql-extensions. All internal usages of thegraphql-extensionsAPI have been migrated to the request pipeline plugin API. For any implementor-suppliedextensions, a deprecation warning will be printed once per-extension, per-server-startup, notifying of the intention to deprecate. Extensions should migrate to the plugin API, which is outlined in its documentation. PR #4135apollo-engine-reporting: Currently only for non-federated graphs.Added an experimental schema reporting option,
experimental_schemaReporting, for Apollo Graph Manager users. Duringthis experiment, we'd appreciate testing and feedback from current and new
users of the schema registry!
Prior to the introduction of this feature, the only way to get schemas into
the schema registry in Apollo Graph Manager was to use the CLI and run
apollo schema:push. Apollo schema reporting protocol is a newspecification for GraphQL servers to automatically report schemas to the
Apollo Graph Manager schema registry.
To enable schema reporting, provide a Graph Manager API key (available
free from Apollo Graph Manager) in the
APOLLO_KEYenvironment variable and set theexperimental_schemaReportingoption to
truein the Apollo Server constructor options, like so:For more details on the implementation of this new protocol, see the PR which
introduced it to Apollo Server and the preview documentation.
PR #4084
apollo-engine-reporting: The underlying integration of this plugin, which instruments and traces the graph's resolver performance and transmits these metrics to Apollo Graph Manager, has been changed from the (soon to be deprecated)graphql-extensionsAPI to the new request pipelinepluginsAPI. PR #3998This change should be purely an implementation detail for a majority of users. There are, however, some special considerations which are worth noting:
ftv1response onextensions(which is present on the response from an implementing service to the gateway) is now placed on theextensionsafter theformatResponsehook. Anyone leveraging theextensions.ftv1data from theformatResponsehook will find that it is no longer present at that phase.apollo-tracing: This package's internal integration with Apollo Server has been switched from using the soon-to-be-deprecatedgraphql-extensionsAPI to using the request pipeline plugin API. Behavior should remain otherwise the same. PR #3991apollo-cache-control: This package's internal integration with Apollo Server has been switched from using the soon-to-be-deprecatedgraphql-extensionsAPI to using the request pipeline plugin API. Behavior should remain otherwise the same. PR #3997v2.13.1Compare Source
v2.13.0Compare Source
WebSocket.ServertoApolloServer.installSubscriptionHandlers. PR #2314apollo-server-lambda: Support file uploads on AWS Lambda Issue #1419 Issue #1703 PR #3926apollo-engine-reporting: Fix inadvertant conditional formatting which prevented automated persisted query (APQ) hits and misses from being reported to Apollo Graph Manager. PR #3986apollo-engine-reporting: Deprecate theENGINE_API_KEYenvironment variable in favor of its new name,APOLLO_KEY. Continued use ofENGINE_API_KEYwill result in deprecation warnings and support for it will be removed in a future major version. #3923apollo-engine-reporting: Deprecated theAPOLLO_SCHEMA_TAGenvironment variable in favor of its new name,APOLLO_GRAPH_VARIANT. Similarly, within theengineconfiguration object, theschemaTagproperty has been renamedgraphVariant. 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 #3855apollo-engine-reporting-protobuf: (This is a breaking change only if you directly depend onapollo-engine-reporting-protobuf.) Drop legacy fields that were never used byapollo-engine-reporting. Added new fieldsStatsContextto allowapollo-serverto send summary stats instead of full traces, and renamedFullTracesReporttoReportandTracestoTracesAndStatssince reports now can include stats as well as traces.v2.12.0Compare Source
apollo-server-core: Support providing a custom logger implementation (e.g.winston,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 aloggerproperty to theGraphQLRequestContextthat 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 toconsole. PR #3894apollo-server-core: When operating in gateway mode using thegatewayproperty 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 #3811apollo-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 withInvalid options provided to ApolloServer:on each request. PR #3811apollo-server-express: Disable the automatic inclusion of thex-powered-by: expressheader. PR #3821apollo-engine-reporting: Avoid creating new arrays when building trace trees. PR #3479apollo-server-core: BumpgraphqlpeerDependenciesrange to include^15.0.0. PR #3944v2.11.0Compare Source
peerDepedenciesversions forgraphqlhas been widened to includegraphql@^15.0.0-rc.2so as to accommodate the latest release-candidate of thegraphql@15package, and an intention to support it when it is finally released on thelatestnpm tag. While this change will subdue peer dependency warnings for Apollo Server packages, many dependencies from outside of this repository will continue to raise similar warnings until those packages ownpeerDependenciesare updated. It is unlikely that all of those packages will update their ranges prior to the final version ofgraphql@15being released, but if everything is working as expected, the warnings can be safely ignored. PR #3825v2.10.1Compare Source
apollo-server-core: Update GraphQL Playground to latest version to remove a rogue curly-brace appearing in the top-right corner of the interface under certain conditions. PR #3702 Playground PRapollo-server-core: Typings: Allow thecacheproperty insidepersistedQueriesto be optional. This was already optional at runtime where it defaults to the top-level global cache when unspecified, but with the introduction of thettlproperty, it now makes sense that one may be provided without the other. #3671v2.10.0Compare Source
apollo-server-express: SupportCorsOptionsDelegatetype oncorsparameter toapplyMiddleware, to align with the supported type of the underlyingcorsmiddleware itself. #3613apollo-server-core: Allow asynchronous initialization of datasources: theinitializemethod on datasources may now return a Promise, which will be settled before any resolvers are called. #3639apollo-server-core: experimental: Allow configuration of the parsed/validated document store by introducing anexperimental_approximateDocumentStoreMiBproperty to theApolloServerconstructor options which overrides the default cache size of 30MiB. #3755v2.9.16Compare Source
apollo-server-core: Update apollo-tooling dependencies, resolve TS build error (missing types for node-fetch) #3662v2.9.15Compare Source
apollo-engine-reporting: Fix regression introduced by #3614 which causedPersistedQueryNotFoundError,PersistedQueryNotSupportedErrorandInvalidGraphQLRequestErrorerrors to be triggered before therequestDidStarthandler triggeredtreeBuilder'sstartTimingmethod. This fix preserves the existing behavior by special-casing these specific errors. #3638 fixes #3627apollo-server-cloud-functions: Transmit CORS headers onOPTIONSrequest. #3557apollo-server-caching: De-compose options interface forKeyValueCache.prototype.setto accommodate better TSDoc annotations for its properties (e.g. to specify thatttlis defined in seconds). #3619apollo-server-core,apollo-server-caching: Introduce attlproperty, specified in seconds, on the options for automated persisted queries (APQ) which applies specific TTL settings to the cachesets during APQ registration. Previously, all APQ cache records were set to 300 seconds. Additionally, this adds support (to the underlyingapollo-server-cachingmechanisms) for a time-to-live (TTL) value ofnullwhich, when supported by the cache implementation, skips the assignment of a TTL value altogether. This allows the cache's controller to determine when eviction happens (e.g. cache forever, and purge least recently used when the cache is full), which may be desireable for network cache stores (e.g. Memcached, Redis). #3623apollo-server-core: Upgrade TS to 3.7.3 #3618v2.9.14Compare Source
apollo-server-core: Ensure that plugin'sdidEncounterErrorshooks are invoked for known automated persisted query (APQ) errors. #3614apollo-server-plugin-base: MoveTContextgeneric fromrequestDidStartmethod toApolloServerPluginInterface. #3525v2.9.13Compare Source
@apollo/gateway: Add@types/node-fetchas a regular dependency to avoid missing dependency for TypeScript consumers. #3546 fixes #3471apollo-engine-reporting: Declare acceptablegraphqlversions ranges inpeerDependenciesrather than allowing it to occur implicitly (and less ideally) via its consumers (e.g. mostapollo-server-*packages). #3496v2.9.12Compare Source
@apollo/protobufjsfork, the build issue for consumers should be resolved.v2.9.11Compare Source
@apollo/protobufjsfork is causing TS errors in consumer projects. Reverting this change for now, and will reintroduce it after the issue is resolved within the forked package.v2.9.10Compare Source
apollo-engine-reporting: Swap usage ofprotobufjsfor a newly published fork located at@apollo/protobufjs. This is to account for the relative uncertainty into the continued on-going maintenance of the officialprotobuf.jsproject. This should immediately resolve a bug that affectedLongtypes inapollo-engine-reportingand other non-Apollo projects that rely onprotobuf.js'sLongtype. #3530v2.9.9Compare Source
apollo-server-core: Don't try parsingvariablesandextensionsas JSON if they are defined but empty strings. #3501apollo-server-lambda: IntroduceonHealthCheckoncreateHandlerin the same fashion as implemented in other integrations. #3458apollo-server-core: Usegraphql'sisSchemato more defensively check the user-specified schema's type at runtime and prevent unexpected errors. #3462v2.9.8Compare Source
apollo-server-core: Provide accurate type forformatResponserather than genericFunctiontype. #3431apollo-server-core: Pass complete request context toformatResponse, rather than justcontext. #3431v2.9.7Compare Source
apollo-server-errors: FixApolloErrorbug andGraphQLErrorspec compliance #3408v2.9.6Compare Source
@apollo/gateway,@apollo/federation,apollo-engine-reporting: Updateapollo-graphqldependency to bring inapollo-tooling's #1551 which resolve runtime errors when its source is minified. While this fixes a particular minification bug when Apollo Server packages are minified, we do not recommend minification of server code in most cases. #3387 fixes #3335apollo-server-koa: Correctly declare dependency onkoa-compose. #3356apollo-server-core: Preserve anyextensionsthat have been placed on the response when pre-execution errors occur. #3394v2.9.5Compare Source
v2.9.4Compare Source
v2.9.3Compare Source
apollo-server-express: Add direct dependency onexpressto allow for usage ofexpress.RouterforgetMiddlewarefunctionality (from #2435). Previously, unlike other server integration packages,apollo-server-expressdid not directly needexpressas a dependency since it only relied onexpressfor TypeScript typings. #3239 fixes #3238apollo-server-lambda: Add@types/aws-lambdaas a direct dependency toapollo-server-expressto allow usage of its typings without needing to separately install it. #3242 fixes #2351v2.9.2Compare Source
apollo-server-koa: Drop support for Node.js v6 within the Apollo Server Koa integration in order to updatekoa-bodyparserdependency fromv3.0.0tov4.2.1. #3229 fixes #3050apollo-server-express: Use explicit return type for newgetMiddlewaremethod. #3230 (hopefully) fixes #3222v2.9.1Compare Source
apollo-server-core: Update apollo-tooling dependencies, resolve TS build error (missing types for node-fetch) #3662apollographql/graphql-tag
v2.11.0Compare Source
package.jsonsideEffectschanges to clearly identify thatgraphql-tagdoesn't have side effects.@hwillson in #313
v2.10.4Compare Source
graphql15.@adriencohen in #299
v2.10.3Compare Source
index.d.tsdeclaration file.@Guillaumez in #289
v2.10.2Compare Source
index.d.tsdeclaration file.@hwillson in #285
Renovate configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻️ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 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.