angular-fullstack-graphql icon indicating copy to clipboard operation
angular-fullstack-graphql copied to clipboard

Update Apollo GraphQL packages (major)

Open renovate[bot] opened this issue 7 years ago • 0 comments

This PR contains the following updates:

Package Type Update Change References
apollo-client dependencies major 1.9.3 -> 2.4.7 source
graphql-tag dependencies major 1.3.2 -> 2.10.0 source

Release Notes

apollographql/apollo-client

v2.4.7

Apollo Client (2.4.7)
  • The ApolloClient constructor has been updated to accept name and version params, that can be used to support Apollo Server Client Awareness functionality. These client awareness properties are passed into the defined Apollo Link chain, and are then ultimately sent out as custom headers with outgoing requests.
    @​hwillson in #​4154
Apollo Boost (0.1.22)
  • No changes.
Apollo Cache (1.1.21)
  • No changes.
Apollo Cache In-Memory (1.3.11)
  • No changes.
Apollo Utilities (1.0.26)
  • No changes.
Graphql Anywhere (4.1.23)
  • No changes.

v2.4.6

Apollo Cache In-Memory (1.3.10)
  • Added some returns to prevent errors with noImplicitReturns TypeScript rule. PR #​4137

  • Exclude the src/ directory when publishing apollo-cache-inmemory. Issue #​4083

v2.4.5

Apollo Cache (1.1.20)
Apollo Cache In-Memory (1.3.9)
Apollo Utilities (1.0.25)

v2.4.4

Apollo Utilities (1.0.24)
Apollo Cache In-Memory (1.3.7)

v2.4.3

Apollo Cache In-Memory (1.3.6)
  • Optimize repeated apollo-cache-inmemory reads by caching partial query results, for substantial performance improvements. As a consequence, watched queries will not be rebroadcast unless the data have changed. PR #​3394

  • Include root ID and fragment matcher function in cache keys computed by StoreReader#executeStoreQuery and executeSelectionSet, and work around bugs in the React Native Map and Set polyfills. PR #​3964 React Native PR #​21492 (pending)

  • The apollo-cache-inmemory package now allows graphql@^14.0.0 as a peer dependency. Issue #​3978

  • The apollo-cache-inmemory package now correctly broadcasts changes even when the new data is === to the old data, since the contents of the data object may have changed. Issue #​3992 PR #​4032

Apollo GraphQL Anywhere (4.1.20)
Apollo Utilities (1.0.22)
  • The fclone package has been replaced with a custom cloneDeep implementation that is tolerant of cycles, symbol properties, and non-enumerable properties. PR #​4032
Apollo Boost (0.1.17)
Apollo Cache (1.1.18)
  • No changes.

v2.4.2

Apollo Client (2.4.2)
Apollo Utilities (1.0.21)
Apollo Boost (0.1.16)
  • No changes.
Apollo Cache (1.1.17)
  • No changes.
Apollo Cache In-Memory (1.2.10)
  • No changes.
Apollo GraphQL Anywhere (4.1.19)
  • No changes.

v2.4.1

Apollo Client (2.4.1)
  • mutate's refetchQueries option now allows queries to include a custom context option. This context will be used when refetching the query. For example:

    context = {
      headers: {
        token: 'some auth token',
      },
    };
    client.mutate({
      mutation: UPDATE_CUSTOMER_MUTATION,
      variables: {
        userId: user.id,
        firstName,
        ...
      },
      refetchQueries: [{
        query: CUSTOMER_MESSAGES_QUERY,
        variables: { userId: user.id },
        context,
      }],
      context,
    });
    

    The CUSTOMER_MESSAGES_QUERY above will be refetched using context. Normally queries are refetched using the original context they were first started with, but this provides a way to override the context, if needed.
    @​hwillson in #​3852

  • Documentation updates.
    @​hwillson in #​3841

Apollo Boost (0.1.15)
Apollo Cache (1.1.16)
Apollo Cache In-Memory (1.2.9)
Apollo Utilities (1.0.20)
Apollo GraphQL Anywhere (4.1.18)

v2.4.0

Apollo Client (2.4.0)
Apollo Cache In-Memory (1.2.8)
Apollo Boost (0.1.14)
  • No changes.
Apollo Cache (1.1.15)
  • No changes.
Apollo Utilities (1.0.19)
  • No changes.
Apollo GraphQL Anywhere (4.1.17)
  • No changes.

v2.3.8

Apollo Client (2.3.8)
Apollo Boost (0.1.13)
  • No changes.
Apollo Cache In-Memory (1.2.7)
  • No changes.
Apollo Cache (1.1.14)
  • No changes.
Apollo Utilities (1.0.18)
  • No changes.
Apollo GraphQL Anywhere (4.1.16)
  • No changes.

v2.3.7

Apollo Client (2.3.7)
  • Release 2.3.6 broke Typescript compilation. QueryManager's getQueryWithPreviousResult method included an invalid variables return type in the auto-generated core/QueryManager.d.ts declaration file. The type definition had a locally referenced path, that appears to have been caused by the typescript compiler getting confused at compile/publish time. getQueryWithPreviousResult return types are now excplicity identified, which helps Typescript avoid the local type reference. For more details, see #​3729.
    @​hwillson in #​3731
Apollo Boost (0.1.12)
  • No changes.

v2.3.6

Apollo Client (2.3.6)
Apollo Boost (0.1.11)
Apollo Cache (1.1.13)
  • No changes.
Apollo Cache In-Memory (1.2.6)
  • Add __typename and id properties to dataIdFromObject parameter (typescript)
    @​jfurler in #​3641
  • Fixed an issue caused by dataIdFromObject considering returned 0 values to be falsy, instead of being a valid ID, which lead to the store not being updated properly in some cases.
    @​hwillson in #​3711
Apollo Utilities (1.0.17)
  • No changes.
Apollo GraphQL Anywhere (4.1.15)

v2.3.5

Apollo Client (2.3.5)
Apollo Boost (0.1.10)
  • No changes.
Apollo Cache (1.1.12)
  • No changes.
Apollo Cache In-Memory (1.2.5)
  • No changes.
Apollo Utilities (1.0.16)
Apollo GraphQL Anywhere (4.1.14)
  • No changes.

v2.3.4

Apollo Client (2.3.4)
  • Export the QueryOptions interface, to make sure it can be used by other projects (like apollo-angular).
  • Fixed an issue caused by typescript changes to the constructor defaultOptions param, that prevented query defaults from passing type checks. (@​hwillson in #​3585)
Apollo Boost (0.1.9)
  • No changes
Apollo Cache (1.1.11)
  • No changes
Apollo Cache In-Memory (1.2.4)
  • No changes
Apollo Utilities (1.0.15)
  • No changes
Apollo GraphQL Anywhere (4.1.13)
  • No changes

v2.3.3

Apollo Client (2.3.3)
  • Typescript improvements. Made observable query parameterized on data and variables: ObservableQuery<TData, TVariables> (@​excitement-engineer in #​3140)
  • Added optional generics to cache manipulation methods (typescript). (@​mvestergaard in #​3541)
  • Typescript improvements. Created a new QueryOptions interface that is now used by ApolloClient.query options, instead of the previous WatchQueryOptions interface. This helps reduce confusion (especially in the docs) that made it look like ApolloClient.query accepted ApolloClient.watchQuery only options, like pollingInterval. (@​hwillson in #​3569)
Apollo Boost (0.1.8)
Apollo Cache (1.1.10)
Apollo Cache In-Memory (1.2.3)
Apollo Utilities (1.0.14)
  • Store key names generated by getStoreKeyName now leverage a more deterministic approach to handling JSON based strings. This prevents store key names from differing when using args like { prop1: 'value1', prop2: 'value2' } and { prop2: 'value2', prop1: 'value1' }. (@​gdi2290 in #​2869)
  • Avoid needless hasOwnProperty check in deepFreeze. (@​benjamn in #​3545)
Apollo GraphQL Anywhere (4.1.12)
  • No new changes.

v2.3.2

Apollo Client (2.3.2)
  • Fix SSR and cache-and-network fetch policy (@​dastoori in #​3372)
  • Fixed an issue where the updateQuery method passed to ObservableQuery.fetchMore was receiving the original query variables, instead of the new variables that it used to fetch more data. (@​abhiaiyer91 in #​3500)
  • Fixed an issue involving Object.setPrototypeOf() not working on JSC (Android), by instead setting the prototype of this manually. (@​seklyza in #​3306)
  • Added safeguards to make sure QueryStore.initQuery and QueryStore.markQueryResult don't try to set the network status of a fetchMoreForQueryId query, if it does not exist in the store. This was happening when a query component was unmounted while a fetchMore was still in flight. (@​conrad-vanl in #​3367, @​doomsower in #​3469)
Apollo Boost (0.1.7)
  • Various internal code cleanup, tooling and dependency changes.
Apollo Cache (1.1.9)
  • Various internal code cleanup, tooling and dependency changes.
Apollo Cache In-Memory (1.2.2)
Apollo Utilities (1.0.13)
  • Make maybeDeepFreeze a little more defensive, by always using Object.prototype.hasOwnProperty (to avoid cases where the object being frozen doesn't have its own hasOwnProperty). (@​jorisroling in #​3418)
  • Remove certain small internal caches to prevent memory leaks when using SSR. (@​brunorzn in #​3444)
Apollo GraphQL Anywhere (4.1.11)
apollostack/graphql-tag

v2.10.0

Compare Source

v2.9.2

Compare Source

v2.9.1

Compare Source

v2.9.0

Compare Source

v2.8.0

Compare Source

v2.7.3

Compare Source

v2.7.1

Compare Source

v2.7.0

Compare Source

v2.6.1

Compare Source

v2.6.0

Compare Source

v2.5.0

Compare Source

v2.4.2

Compare Source

v2.4.1

Compare Source

v2.4.0

Compare Source

v2.3.0

Compare Source

v2.2.2

Compare Source

v2.2.1

Compare Source

v2.2.0

Compare Source

v2.1.0

Compare Source

v2.0.0

Compare Source

Restore dependence on graphql module abhiaiyer91 in PR #​46 addressing #​6


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 if you modify the PR title to begin with "rebase!".

: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 has been generated by Renovate Bot. View repository job log here.

renovate[bot] avatar Oct 05 '18 13:10 renovate[bot]