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

Bump @apollo/client from 3.1.5 to 3.3.11 #89

Closed

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Feb 18, 2021

Bumps @apollo/client from 3.1.5 to 3.3.11.

Release notes

Sourced from @apollo/client's releases.

3.3.0

Apollo Client 3.3.0

Bug Fixes

  • Update @wry/equality to consider undefined properties equivalent to missing properties. @benjamn in #7108

  • Prevent memory leaks involving unused onBroadcast function closure created in ApolloClient constructor. @kamilkisiela in #7161

  • Provide default empty cache object for root IDs like ROOT_QUERY, to avoid differences in behavior before/after ROOT_QUERY data has been written into InMemoryCache. @benjamn in #7100

  • Cancel queryInfo.notifyTimeout in QueryInfo#markResult to prevent unnecessary network requests when using a FetchPolicy of cache-and-network or network-only in a React component with multiple useQuery calls. @benjamn in #7347

Potentially breaking changes

  • Ensure cache.readQuery and cache.readFragment always return TData | null, instead of throwing MissingFieldError exceptions when missing fields are encountered. @benjamn in #7098

    Since this change converts prior exceptions to null returns, and since null was already a possible return value according to the TData | null return type, we are confident this change will be backwards compatible (as long as null was properly handled before).

  • HttpLink will now automatically strip any unused variables before sending queries to the GraphQL server, since those queries are very likely to fail validation, according to the All Variables Used rule in the GraphQL specification. If you depend on the preservation of unused variables, you can restore the previous behavior by passing includeUnusedVariables: true to the HttpLink constructor (which is typically passed as options.link to the ApolloClient constructor). @benjamn in #7127

  • Ensure MockLink (used by MockedProvider) returns mock configuration errors (e.g. No more mocked responses for the query ...) through the Link's Observable, instead of throwing them. These errors are now available through the error property of a result. @hwillson in #7110

    Returning mock configuration errors through the Link's Observable was the default behavior in Apollo Client 2.x. We changed it for 3, but the change has been problematic for those looking to migrate from 2.x to 3. We've decided to change this back with the understanding that not many people want or are relying on MockLink's throwing exception approach. If you want to change this functionality, you can define custom error handling through MockLink.setOnError.

  • Unsubscribing the last observer from an ObservableQuery will once again unsubscribe from the underlying network Observable in all cases, as in Apollo Client 2.x, allowing network requests to be cancelled by unsubscribing. @javier-garcia-meteologica in #7165 and #7170.

  • The independent QueryBaseOptions and ModifiableWatchQueryOptions interface supertypes have been eliminated, and their fields are now defined by QueryOptions. @DCtheTall in #7136

  • Internally, Apollo Client now avoids nested imports from the graphql package, importing everything from the top-level package instead. For example,

    import { visit } from "graphql/language/visitor"

    is now just

    import { visit } from "graphql"

    Since the graphql package uses .mjs modules, your bundler may need to be configured to recognize .mjs files as ECMAScript modules rather than CommonJS modules. @benjamn in #7185

Improvements

  • Support inheritance of type and field policies, according to possibleTypes.

... (truncated)

Changelog

Sourced from @apollo/client's changelog.

Apollo Client 3.3.11

Bug fixes

  • Fix useLazyQuery forceUpdate loop regression introduced by #7655 in version 3.3.10. @benjamn in #7715

Apollo Client 3.3.10

Bug fixes

  • Revert PR #7276, but test that garbage collection reclaims torn-down ObservableQuery objects. @benjamn in #7695

  • Reset QueryInfo.diff and QueryInfo.dirty after canceling notify timeout in QueryInfo.markResult and QueryInfo.markError. @jcreighton in #7696

Improvements

  • Avoid calling forceUpdate when component is unmounted. @DylanVann in #7655

  • The codemods/ top-level directory has been moved into the scripts/ directory. @benjamn in #7675

Apollo Client 3.3.9

Bug Fixes

  • Prevent reactive variables from retaining otherwise unreachable InMemoryCache objects. @benjamn in #7661

Improvements

  • The graphql-tag dependency has been updated to version 2.12.0, after converting its repository to use TypeScript and ECMAScript module syntax. There should be no visible changes in behavior, though the internal changes seemed significant enough to mention here. @abdonrd in graphql-tag#273 and @PowerKiKi in graphql-tag#325

Apollo Client 3.3.8

Bug Fixes

  • Catch updates in useReactiveVar with an additional check. @jcreighton in #7652

  • Reactivate forgotten reactive variables whenever InMemoryCache acquires its first watcher. @benjamn in #7657

  • Backport Symbol.species fix for Concast and ObservableQuery from release-3.4, fixing subscriptions in React Native Android when the Hermes JavaScript engine is enabled (among other benefits). @benjamn in #7403 and #7660

... (truncated)

Commits
  • 07778db Bump @apollo/client npm version to 3.3.11.
  • d36595b Fix useLazyQuery forceUpdate loop regression. (#7715)
  • 2b1f1f4 Bump @apollo/client npm version to 3.3.10.
  • 3d6f54c Mention PR #7696 in CHANGELOG.md.
  • 911a19a Reset QueryInfo.{diff,dirty} after canceling notify timeout in mark{Result,Er...
  • 7b9bf8b chore(deps): update dependency graphql to v15.5.0
  • bcb2631 chore(deps): update dependency @types/react to v17.0.2
  • ce4d053 chore(deps): update dependency @types/lodash to v4.14.168
  • 7b821c7 chore(deps): update dependency @types/react-dom to v17.0.1
  • dfb4cb4 chore(deps): update dependency @rollup/plugin-node-resolve to v11.1.1
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Mar 16, 2021

Superseded by #105.

@dependabot dependabot bot closed this Mar 16, 2021
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/apollo/client-3.3.11 branch March 16, 2021 06:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants