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

Release 3.4.0 #7399

Merged
merged 454 commits into from Jul 28, 2021
Merged

Release 3.4.0 #7399

merged 454 commits into from Jul 28, 2021

Conversation

benjamn
Copy link
Member

@benjamn benjamn commented Dec 1, 2020

Like the Release 3.3.0 PR, this PR will serve to collect significant new features, deprecation warnings, and minor breaking changes that we intend to release in @apollo/client@3.4.0.

If you want to test these changes, run

npm i @apollo/client@3.4.0-beta.n

in your application, where the n in -beta.n comes from the most recent commit message like

Bump @apollo/client npm version to 3.4.0-beta.n.

Until v3.4.0 is released, we can continue merging smaller changes into main and releasing them, without worrying about larger changes on the release-3.4 branch.

@benjamn

This comment has been minimized.

@abdonrd
Copy link
Contributor

abdonrd commented Mar 22, 2021

@benjamn I get an error when update from v3.4.0-beta.14 to v3.4.0-beta.15:
Screenshot 2021-03-22 at 14 12 57

This file is: https://github.com/graphql/graphql-js/blob/v15.2.0/src/jsutils/instanceOf.js#L14
But that file hasn't changed since January 2020.

All works if I go back to v3.4.0-beta.14.

I'm using the @web/dev-server.

@abdonrd
Copy link
Contributor

abdonrd commented Mar 24, 2021

@benjamn I add the npm dependencies diff about #7399 (comment):

apollo-error

This downgrade makes the project work again.

@benjamn
Copy link
Member Author

benjamn commented Mar 25, 2021

@abdonrd Thanks for the heads up! Just linking to my comment on your issue for others' benefit: #7895 (comment)

@benjamn
Copy link
Member Author

benjamn commented May 11, 2021

@StephenBarlow Looking at the client.watchQuery options, I noticed we only display the options that are not in the client.query options (below), even though WatchQueryOptions inherits from QueryOptions (and adds/redefines a few new options, like fetchPolicy). Is there anything we can do about that? Not urgent, just curious.

@StephenBarlow
Copy link
Contributor

@benjamn You mean in the autogenerated reference, yes? I fear I know very little about its internal workings, and it predates me. My guess would be that doing something about this would require an amount of work similar to either:

  • Moving Apollo Client off of autogenerated references entirely
  • Revamping the autogeneration process entirely

Both of which feel preferable to tacking features onto our existing solution, which as I understand it is creaky

Previously, removing an optimistic EntityStore layer with
removeOptimistic would dirty all fields of any StoreObjects contained by
the removed layer, ignoring the possibility that some of those field
values might have been inherited as-is from the parent layer.

With this commit, we dirty only those fields whose values will be
observably changed by removing the layer, which requires comparing field
values between the layer-to-be-removed and its parent layer.
Copy link
Member

@hwillson hwillson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

WOOHOO!!! 🎉 🎉 🎉

@benjamn benjamn merged commit b0da267 into main Jul 28, 2021
@benjamn benjamn deleted the release-3.4 branch July 28, 2021 17:12
@benjamn
Copy link
Member Author

benjamn commented Jul 28, 2021

@abdonrd You have uncanny timing! The final @apollo/client@3.4.0 has now been published to npm, though it's tagged as next rather than latest for the meantime. Let us know if you have any problems with it, and thanks again for all your help with this release!

@benjamn benjamn restored the release-3.4 branch July 28, 2021 17:17
@benjamn benjamn mentioned this pull request Jul 28, 2021
@hwillson hwillson moved this from In progress to Done in Release 3.4 Jul 29, 2021
@hwillson hwillson removed this from the MM-2021-07 milestone Jul 29, 2021
@brainkim brainkim deleted the release-3.4 branch August 13, 2021 14:34
@brainkim brainkim restored the release-3.4 branch August 13, 2021 14:34
@StephenBarlow StephenBarlow deleted the release-3.4 branch October 4, 2021 19:10
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 15, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
No open projects
Development

Successfully merging this pull request may close these issues.

None yet