Skip to content
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

Update Apollo GraphQL packages #134

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jan 17, 2019

This PR contains the following updates:

Package Type Update Change
apollo-cache-inmemory dependencies minor 1.3.12 -> 1.6.5
apollo-client dependencies minor 2.4.8 -> 2.6.8
apollo-link-ws dependencies patch 1.0.12 -> 1.0.20
apollo-server-core dependencies minor 2.3.1 -> 2.12.0
graphql-tag devDependencies patch 2.10.0 -> 2.10.3
graphql-tools dependencies patch 4.0.3 -> 4.0.8

Release Notes

apollographql/apollo-client

v1.6.5

Compare Source

v1.6.3

Compare Source

v1.6.2

Compare Source

v1.6.1

Compare Source

  • Pretend that __typename exists on the root Query when matching fragments.

    @​benjamn in #​4853

v1.6.0

Compare Source

  • Support new InMemoryCache({ freezeResults: true }) to help enforce immutability.

    @​benjamn in #​4514

  • Allow IntrospectionFragmentMatcher to match fragments against the root Query, as HeuristicFragmentMatcher does.

    @​rynobax in #​4620

  • Rerential identity (===) of arrays in cache results will now be preserved for unchanged data.

    @​benjamn in commit f3091d6a

  • Avoid adding __typename field to @client selection sets that have been @exported as input variables.

    @​benjamn in #​4784

v1.5.1

Compare Source

v1.5.0

Compare Source

v1.4.3

Compare Source

v1.4.2

Compare Source

v1.4.1

Compare Source

  • The optimism npm package has been updated to a version (0.6.9) that
    provides its own TypeScript declarations, which should fix problems like
    Issue #​4327.

    PR #​4331

  • Error messages involving GraphQL queries now print the queries using
    JSON.stringify instead of the print function exported by the
    graphql package, to avoid pulling unnecessary printing logic into your
    JavaScript bundle.

    PR #​4234

  • The QueryKeyMaker abstraction has been removed, meaning that cache
    results for non-identical queries (or sub-queries) with equivalent
    structure will no longer be cached together. This feature was a nice
    optimization in certain specific use cases, but it was not worth the
    additional complexity or bundle size.

    PR #​4245

v1.4.0

Compare Source

  • The speed and memory usage of optimistic reads and writes has been
    improved dramatically using a new layering technique that does not
    require copying the non-optimistic contents of the cache.

    PR #​4319

  • The RecordingCache abstraction has been removed, and thus is no longer
    exported from apollo-cache-inmemory.

    PR #​4319

  • Export the optimism wrap function using ES2015 export syntax, instead of
    CommonJS.

    @​ardatan in #​4158

apollographql/apollo-link

v1.0.20

Compare Source

v1.0.19

Compare Source

v1.0.18

Compare Source

  • Fixes an issue introduced in #​984
    where subscriber next and/or error calls might have already deleted the
    key the new dedupe changes were intended to help with.

    @​JoviDeCroock in #​988

v1.0.17

Compare Source

  • Fixes an issue caused by the DedupLink shared observable returning
    cleanup logic that unsubscribes from the real observable, without
    checking whether only one of the many (shared) subscribers are
    unsubscribing. This caused problems when using DedupLink in front of
    HttpLink, as this lead to HttpLink aborting HTTP requests while some
    callers were still waiting for a response.

    @​ms in #​984

v1.0.16

Compare Source

v1.0.15

Compare Source

v1.0.14

Compare Source

v1.0.13

Compare Source

apollographql/apollo-server

v2.12.0

Compare Source

See complete versioning details.

  • 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 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
  • 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
  • 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
  • apollo-server-express: Disable the automatic inclusion of the x-powered-by: express header. PR #​3821
  • apollo-engine-reporting: Avoid creating new arrays when building trace trees. PR #​3479
  • apollo-server-core: Bump graphql peerDependencies range to include ^15.0.0. PR #​3944

v2.11.0

Compare Source

See complete versioning details.

  • The range of accepted peerDepedencies versions for graphql has been widened to include graphql@^15.0.0-rc.2 so as to accommodate the latest release-candidate of the graphql@15 package, and an intention to support it when it is finally released on the latest npm 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 own peerDependencies are updated. It is unlikely that all of those packages will update their ranges prior to the final version of graphql@15 being released, but if everything is working as expected, the warnings can be safely ignored. PR #​3825

v2.10.1

Compare Source

See complete versioning details.

  • 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 PR
  • apollo-server-core: Typings: Allow the cache property inside persistedQueries to be optional. This was already optional at runtime where it defaults to the top-level global cache when unspecified, but with the introduction of the ttl property, it now makes sense that one may be provided without the other. #​3671

v2.10.0

Compare Source

See complete versioning details.

  • apollo-server-express: Support CorsOptionsDelegate type on cors parameter to applyMiddleware, to align with the supported type of the underlying cors middleware itself. #​3613
  • apollo-server-core: Allow asynchronous initialization of datasources: the initialize method on datasources may now return a Promise, which will be settled before any resolvers are called. #​3639
  • apollo-server-core: experimental: Allow configuration of the parsed/validated document store by introducing an experimental_approximateDocumentStoreMiB property to the ApolloServer constructor options which overrides the default cache size of 30MiB. #​3755

v2.9.16

Compare Source

See complete versioning details.

  • apollo-server-core: Update apollo-tooling dependencies, resolve TS build error (missing types for node-fetch) #​3662

v2.9.15

Compare Source

See complete versioning details.

  • apollo-engine-reporting: Fix regression introduced by #​3614 which caused PersistedQueryNotFoundError, PersistedQueryNotSupportedError and InvalidGraphQLRequestError errors to be triggered before the requestDidStart handler triggered treeBuilder's startTiming method. This fix preserves the existing behavior by special-casing these specific errors. #​3638 fixes #​3627
  • apollo-server-cloud-functions: Transmit CORS headers on OPTIONS request. #​3557
  • apollo-server-caching: De-compose options interface for KeyValueCache.prototype.set to accommodate better TSDoc annotations for its properties (e.g. to specify that ttl is defined in seconds). #​3619
  • apollo-server-core, apollo-server-caching: Introduce a ttl property, specified in seconds, on the options for automated persisted queries (APQ) which applies specific TTL settings to the cache sets during APQ registration. Previously, all APQ cache records were set to 300 seconds. Additionally, this adds support (to the underlying apollo-server-caching mechanisms) for a time-to-live (TTL) value of null which, 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). #​3623
  • apollo-server-core: Upgrade TS to 3.7.3 #​3618

v2.9.14

Compare Source

See complete versioning details.

  • apollo-server-core: Ensure that plugin's didEncounterErrors hooks are invoked for known automated persisted query (APQ) errors. #​3614
  • apollo-server-plugin-base: Move TContext generic from requestDidStart method to ApolloServerPlugin Interface. #​3525

v2.9.13

Compare Source

See complete versioning details.

  • @apollo/gateway: Add @types/node-fetch as a regular dependency to avoid missing dependency for TypeScript consumers. #​3546 fixes #​3471
  • apollo-engine-reporting: Declare acceptable graphql versions ranges in peerDependencies rather than allowing it to occur implicitly (and less ideally) via its consumers (e.g. most apollo-server-* packages). #​3496

v2.9.12

Compare Source

  • Reinstate #​3530 via #​3539 - after a patch release of the @apollo/protobufjs fork, the build issue for consumers should be resolved.

v2.9.11

Compare Source

  • Revert #​3530 via #​3535- the introduction of the @apollo/protobufjs fork 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.10

Compare Source

See complete versioning details.

  • apollo-engine-reporting: Swap usage of protobufjs for a newly published fork located at @apollo/protobufjs. This is to account for the relative uncertainty into the continued on-going maintenance of the official protobuf.js project. This should immediately resolve a bug that affected Long types in apollo-engine-reporting and other non-Apollo projects that rely on protobuf.js's Long type. #​3530

v2.9.9

Compare Source

See complete versioning details.

  • apollo-server-core: Don't try parsing variables and extensions as JSON if they are defined but empty strings. #​3501
  • apollo-server-lambda: Introduce onHealthCheck on createHandler in the same fashion as implemented in other integrations. #​3458
  • apollo-server-core: Use graphql's isSchema to more defensively check the user-specified schema's type at runtime and prevent unexpected errors. #​3462

v2.9.8

Compare Source

See complete versioning details.

  • apollo-server-core: Provide accurate type for formatResponse rather than generic Function type. #​3431
  • apollo-server-core: Pass complete request context to formatResponse, rather than just context. #​3431

v2.9.7

Compare Source

See complete versioning details.

  • apollo-server-errors: Fix ApolloError bug and GraphQLError spec compliance #​3408

v2.9.6

Compare Source

See complete versioning details.

  • @apollo/gateway, @apollo/federation, apollo-engine-reporting: Update apollo-graphql dependency to bring in apollo-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 #​3335
  • apollo-server-koa: Correctly declare dependency on koa-compose. #​3356
  • apollo-server-core: Preserve any extensions that have been placed on the response when pre-execution errors occur. #​3394

v2.9.5

Compare Source

v2.9.4

Compare Source

v2.9.3

Compare Source

See complete versioning details.

  • apollo-server-express: Add direct dependency on express to allow for usage of express.Router for getMiddleware functionality (from #​2435). Previously, unlike other server integration packages, apollo-server-express did not directly need express as a dependency since it only relied on express for TypeScript typings. #​3239 fixes #​3238
  • apollo-server-lambda: Add @types/aws-lambda as a direct dependency to apollo-server-express to allow usage of its typings without needing to separately install it. #​3242 fixes #​2351

v2.9.2

Compare Source

See complete versioning details.

  • apollo-server-koa: Drop support for Node.js v6 within the Apollo Server Koa integration in order to update koa-bodyparser dependency from v3.0.0 to v4.2.1. #​3229 fixes #​3050
  • apollo-server-express: Use explicit return type for new getMiddleware method. #​3230 (hopefully) fixes #​3222

v2.9.1

Compare Source

See complete versioning details.

  • apollo-server-core: Update apollo-tooling dependencies, resolve TS build error (missing types for node-fetch) #​3662

v2.9.0

Compare Source

See complete versioning details.

  • apollo-server-express, apollo-server-koa: A new getMiddleware method has been introduced, which accepts the same parameters as applyMiddleware with the exception of the app property. This allows implementors to obtain the middleware directly and "use" it within an existing app. In the near-term, this should ease some of the pain points with the previous technique. Longer-term, we are exploring what we consider to be a much more natural approach by introducing an "HTTP transport" in Apollo Server 3.x. See this proposal issue for more information. #​2435
  • @apollo/federation: buildFederatedSchema's typeDefs parameter now accepts arrays of DocumentNodes (i.e. type definitions wrapped in gql) and resolvers to make the migration from a single service into a federated service easier for teams previously utilizing this pattern. #​3188

v2.8.2

Compare Source

See complete versioning details.

v2.8.1

Compare Source

See complete versioning details.

  • apollo-engine-reporting: Fix reporting errors which have non-array path fields (eg, non-GraphQLError errors). PR #​3112
  • apollo-engine-reporting: Add missing apollo-server-caching dependency. PR #​3054
  • apollo-server-hapi: Revert switch from accept and boom which took place in v2.8.0. PR #​3089
  • @apollo/gateway: Change the setInterval timer, which is used to continuously check for updates to a federated graph from the Apollo Graph Manager, to be an unref'd timer. Without this change, the server wouldn't terminate properly once polling had started since the event-loop would continue to have unprocessed events on it. PR #​3105
  • Switch to using community @types/graphql-upload types.
  • apollo-server-fastify: Change the typing of the HTTP response from OutgoingMessage to ServerResponse. Commit
  • apollo-server-hapi: Pass the raw request and response objects to graphql-uploads processRequest method to align on the same TypeScript types. Commit

v2.8.0

Compare Source

See complete versioning details.

  • @apollo/federation: Add support for "value types", which are type definitions which live on multiple services' types, inputs, unions or interfaces. These common types must be identical by name, kind and field across all services. PR #​3063
  • apollo-server-express: Use the Express send method, rather than calling net.Socket.prototype.end. PR #​2842
  • apollo-server-hapi: Update internal dependencies to use scoped packages @hapi/accept and @hapi/boom, in place of accept and boom respectively. PR #​3089

v2.7.2

Compare Source

See complete versioning details.

  • apollo-engine-reporting: Fix reporting errors from backend. (The support for federated metrics introduced in v2.7.0 did not properly handle GraphQL errors from the backend; all users of federated metrics should upgrade to this version.) PR #​3056 Issue #​3052
  • apollo-engine-reporting: Clean up SIGINT and SIGTERM handlers when EngineReportingAgent is stopped; fixes 'Possible EventEmitter memory leak detected' log. PR #​3090

v2.7.1

Compare Source

See complete versioning details.

  • apollo-engine-reporting: If an error is thrown by a custom variable transform function passed into the reporting option sendVariableValues: { transform: ... }, all variable values will be replaced with the string [PREDICATE_FUNCTION_ERROR].
  • apollo-server-express: Typing fix for the connection property, which was missing from the ExpressContext interface. PR #​2959
  • @apollo/gateway: Ensure execution of correct document within multi-operation documents by including the operationName in the cache key used when caching query plans used in federated execution. PR #​3084

v2.7.0

Compare Source

See complete versioning details.

  • apollo-engine-reporting: Behavior change: By default, send no GraphQL variable values to Apollo's servers instead of sending all variable values. Adding the new EngineReportingOption sendVariableValues to send some or all variable values, possibly after transforming them. This replaces the privateVariables option, which is now deprecated. PR #​2931

    To maintain the previous behavior of transmitting all GraphQL variable values, unfiltered, to Apollo Engine, configure engine.sendVariableValues as follows:

    engine: {
      sendVariableValues: { all: true }
    }
  • apollo-engine-reporting: Behavior change: By default, send no GraphQL request headers and values to Apollo's servers instead of sending all. Adding the new EngineReportingOption sendHeaders to send some or all header values. This replaces the privateHeaders option, which is now deprecated. PR #​2931

    To maintain the previous behavior of transmitting all GraphQL request headers and values, configure engine.sendHeaders as following:

    engine: {
      sendHeaders: { all: true }
    }
  • apollo-engine-reporting: Behavior change: If the error returned from the engine.rewriteError hook has an extensions property, that property will be used instead of the original error's extensions. Document that changes to most other GraphQLError fields by engine.rewriteError are ignored. PR #​2932

  • apollo-engine-reporting: Behavior change: The engine.maskErrorDetails option, deprecated by engine.rewriteError in v2.5.0, now behaves a bit more like the new option: while all error messages will be redacted, they will still show up on the appropriate nodes in a trace. PR #​2932

  • apollo-server-core, @apollo/gateway: Introduced managed federation support. For more information on managed federation, see the blog post or jump to the documentation for managed federation.

  • @apollo/[email protected]: Don't print a warning about an unspecified "graph variant" (previously, and in many ways still, known as "schema tag") every few seconds. We do highly recommend specifying one when using the Apollo Platform features though! PR #​3043

  • graphql-playground: Update to resolve incorrect background color on tabs when using the light theme. PR #​2989 Issue #​2979

  • graphql-playground: Fix "Query Planner" and "Tracing" panels which were off the edge of the viewport.

  • apollo-server-plugin-base: Fix GraphQLRequestListener type definitions to allow return void. PR #​2368

v2.6.9

Compare Source

v2.6.8

Compare Source

v2.6.7

Compare Source

See complete versioning details.

  • apollo-server-core: Guard against undefined property access in isDirectiveDefined which resulted in "Cannot read property 'some' of undefined" error. PR #​2924 Issue #​2921

v2.6.6

Compare Source

See complete versioning details.

  • apollo-server-core: Avoid duplicate cacheControl directives being added via isDirectiveDefined, re-landing the implementation reverted in v2.6.1 which first surfaced in v2.6.0. PR #​2762 Reversion PR #​2754 Original PR #​2428
  • apollo-server-testing: Add TypeScript types for apollo-server-testing client. PR #​2871
  • apollo-server-plugin-response-cache: Fix undefined property access attempt which occurred when an incomplete operation was received. PR #​2792 Issue #​2745

v2.6.5

Compare Source

See complete versioning details.

  • apollo-engine-reporting: Simplify the technique for capturing operationName. PR #​2899
  • apollo-server-core: Fix regression in 2.6.0 which caused engine: false not to disable Engine when the ENGINE_API_KEY environment variable was set. PR #​2850
  • @apollo/federation: Introduced a README.md. PR #​2883
  • @apollo/gateway: Introduced a README.md. PR #​2883

v2.6.4

Compare Source

See complete versioning details.

  • @apollo/gateway: Pass context through to the graphql command in LocalGraphQLDataSource's process method. PR #​2821
  • @apollo/gateway: Fix gateway not sending needed variables for subqueries not at the root level. PR #​2867
  • @apollo/federation: Allow matching enums/scalars in separate services and validate that enums have matching values. PR #​2829.
  • @apollo/federation: Strip @external fields from interface extensions. PR #​2848
  • @apollo/federation: Add support for list type keys in federation. PR #​2841
  • @apollo/federation: Deduplicate variable definitions for sub-queries. PR #​2840

v2.6.3

Compare Source

See complete versioning details.

  • apollo-engine-reporting: Set forbiddenOperation and registeredOperation later in the request lifecycle. PR #​2828
  • apollo-server-core: Add queryHash to GraphQLExecutor for federation. PR #​2822
  • @apollo/federation: Preserve descriptions from SDL of federated services. PR #​2830

v2.6.2

Compare Source

  • apollo-engine-reporting-protobuf: Update protobuf to include forbiddenOperations and registeredOperations. PR #​2768
  • apollo-server-core: Add forbiddenOperation and registeredOperation to GraphQLRequestMetrics type. PR #​2768
  • apollo-engine-reporting: Set forbiddenOperation and registeredOperation on trace if the field is true on requestContext.metrics. PR #​2768
  • apollo-server-lambda: Remove Object.fromEntries usage. PR #​2787

v2.6.1

Compare Source

  • Revert: Don't add cacheControl directive if one has already been defined. Presently, although the TypeScript don't suggest it, passing a String as typeDefs to ApolloServer is supported and this would be a breaking change for non-TypeScript users. PR #​2428

v2.6.0

Compare Source

  • apollo-server-core: Introduce new didEncounterErrors life-cycle hook which has access to unformatted errors property on the requestContext, which is the first positional parameter that this new request life-cycle receives. PR #​2719
  • apollo-server-core: Allow request pipeline life-cycle hooks (i.e. plugins) to modify the response's http.status code (an integer) in the event of an error. When combined with the new didEncounterErrors life-cycle hook (see above), this will allow modifying the HTTP status code in the event of an error. PR #​2714
  • apollo-server-lambda: Set callbackWaitsForEmptyEventLoop to false for OPTIONS requests to return as soon as the callback is triggered instead of waiting for the event loop to empty. PR #​2638
  • apollo-server: Support onHealthCheck in the ApolloServer constructor in the same way as cors is supported. This contrasts with the -express, -hapi, etc. variations which accept this parameter via their applyMiddleware methods and will remain as-is. PR #​2672
  • core: Expose SHA-512 hex hash digest of the Engine API key to plugins, when available, as engine.apiKeyHash. PR #​2685 PR #​2736
  • apollo-datasource-rest: If another Content-type is already set on the response, don't overwrite it with application/json, allowing the user's initial Content-type to prevail. PR #​2520
  • Don't add cacheControl directive if one has already been defined. PR #​2428
  • apollo-cache-control: Do not respond with Cache-control headers if the HTTP response contains errors. PR #​2715
  • apollo-server-core: Skip loading util.promisify polyfill in Node.js engines >= 8.0 PR #​2278
  • apollo-server-core: Lazy load subscriptions-transport-ws in core PR #​2278
  • apollo-server-cache-redis: BREAKING FOR USERS OF apollo-server-cache-redis (This is a package that must be updated separately but shares the same CHANGELOG.md with Apollo Server itself.) A new major version of this package has been published and updated to support Redis Standalone, Cluster and Sentinel modes. This is a breaking change since it is now based on ioredis instead of node_redis. Although this update is compatible with the most common uses of apollo-server-cache-redis, please check the options supported by ioredis while updating to this version. The constructor options are passed directly from RedisCache to the new Redis adapter. The pre-1.0 versions should continue to work with Apollo Server without modification. PR #​1770

v2.5.1

Compare Source

  • Upgrade GraphQL Playground to the latest upstream release. This release also includes a new "Query Plan" panel for displaying the query planning results when running the Apollo Gateway.

v2.5.0

Compare Source

New
  • New plugin package apollo-server-plugin-response-cache implementing a full query response cache based on apollo-cache-control hints. The implementation added a few hooks and context fields; see the PR for details. There is a slight change to cacheControl object: previously, cacheControl.stripFormattedExtensions defaulted to false if you did not provide a cacheControl option object, but defaulted to true if you provided (eg) cacheControl: {defaultMaxAge: 10}. Now stripFormattedExtensions defaults to false unless explicitly provided as true, or if you use the legacy boolean cacheControl: true. For more information, read the documentation. PR #​2437
  • Add rewriteError option to EngineReportingOptions (i.e. the engine property of the ApolloServer constructor). When defined as a function, it will receive an err property as its first argument which can be used to manipulate (e.g. redaction) an error prior to sending it to Apollo Engine by modifying, e.g., its message property. The error can also be suppressed from reporting entirely by returning an explicit null value. For more information, read the documentation and the EngineReportingOptions API reference. maskErrorDetails is now deprecated. PR #​1639
  • apollo-server-azure-functions: Support @azure/functions to enable Apollo Server Typescript development in Azure Functions. PR #​2487
  • Allow GraphQLRequestListener callbacks in plugins to depend on this. PR #​2470
  • apollo-server-testing: Add variables and operationName to Query and Mutation types. PR #​2307 Issue #​2172
Bug fixes
  • Add cache-control: no-cache header to both PersistedQueryNotSupportedError and PersistedQueryNotFoundError responses as these should never be cached. PR #​2452
  • apollo-datasource-rest: Don't attempt to parse "204 No Content" responses as JSON. PR #​2446
  • apollo-server-express: Fix Playground URL when Apollo Server is mounted inside of another Express app by utilizing req.originalUrl. PR #​2451
  • apollo-datasource-rest: Correctly allow a TTL value of 0 to represent "not-cacheable". PR #​2588
  • apollo-datasource-rest: Fix Invalid argument in IE11, when this.headers is undefined. PR #​2607

v2.4.8

Compare Source

  • No functional changes in this version. The patch version has been bumped to fix the README.md displayed on the npm package for apollo-server as a result of a broken publish. Apologies for the additional noise!

v2.4.7

Compare Source

  • Fix typings which incorrectly included cors as part of the constructor options for apollo-server-express (it should be defined via applyMiddleware) but, conversely, inadvertently omitted the perfectly valid cors option from the apollo-server constructor (where applyMiddleware is not used/available). PR #​2373 Issue #​1882

v2.4.6

Compare Source

v2.4.4

Compare Source

  • Fix typing for ContextFunction incorrectly requiring the context object the function produces to match the parameters of the function PR #​2350

v2.4.3

Compare Source

  • apollo-server-lambda: Fix typings which triggered "Module has no default export" errors. [PR #​2230](https://togithub.com/apol

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.


  • If you want to rebase/retry this PR, check this box

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

@codecov
Copy link

codecov bot commented Jan 17, 2019

Codecov Report

Merging #134 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@          Coverage Diff           @@
##           master    #134   +/-   ##
======================================
  Coverage    81.1%   81.1%           
======================================
  Files          10      10           
  Lines         381     381           
  Branches       60      60           
======================================
  Hits          309     309           
  Misses         64      64           
  Partials        8       8

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 060e739...4b1651d. Read the comment docs.

@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from dc2d55a to dcec664 Compare January 17, 2019 20:21
@renovate renovate bot changed the title Update dependency graphql-tag to v2.10.1 Update Apollo GraphQL packages Jan 17, 2019
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 3 times, most recently from 6cd2738 to 472ec81 Compare January 19, 2019 00:02
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 2 times, most recently from b4274ff to c98fe0a Compare February 1, 2019 19:54
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 2 times, most recently from 6cb181d to 47e237d Compare February 13, 2019 18:34
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 2 times, most recently from b590ce0 to dfb5dd3 Compare February 27, 2019 14:34
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from dfb5dd3 to bd91893 Compare March 5, 2019 23:11
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 2 times, most recently from 4ce3106 to 5918b4d Compare March 14, 2019 11:16
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from 5918b4d to f315666 Compare May 22, 2019 12:55
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from f315666 to 6a77b6f Compare June 19, 2019 10:52
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 2 times, most recently from e7c1c8a to cd94552 Compare August 10, 2019 16:28
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 2 times, most recently from 7ca6329 to 7d937c3 Compare August 23, 2019 15:26
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch 3 times, most recently from b8fe2c4 to aa1cf25 Compare September 1, 2019 21:50
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from aa1cf25 to dc88252 Compare September 6, 2019 16:35
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from dc88252 to 3caf87f Compare September 30, 2019 10:58
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from 3caf87f to aefa167 Compare November 10, 2019 18:59
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from aefa167 to 599885e Compare November 20, 2019 09:59
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from 599885e to d580dbf Compare December 14, 2019 16:58
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from d580dbf to e527c86 Compare December 21, 2019 20:59
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from e527c86 to 4b1651d Compare December 30, 2019 08:58
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from 4b1651d to 81742d8 Compare January 18, 2020 13:54
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from 81742d8 to 54bb50b Compare February 8, 2020 12:58
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from 54bb50b to 6408902 Compare February 16, 2020 06:56
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from 6408902 to de522f4 Compare March 10, 2020 14:58
@renovate renovate bot force-pushed the renovate/apollo-graphql-packages branch from de522f4 to be124db Compare April 26, 2020 09:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant