Update Apollo GraphQL packages #248
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
renovate
bot
force-pushed
the
renovate/apollo-graphql-packages
branch
from
fdb3a36 to
33fbe53
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/apollo-graphql-packages
branch
from
33fbe53 to
c88a2ba
Compare
renovate
bot
force-pushed
the
renovate/apollo-graphql-packages
branch
2 times, most recently
from
661df03 to
5b8b131
Compare
renovate
bot
force-pushed
the
renovate/apollo-graphql-packages
branch
2 times, most recently
from
ebafdb1 to
f2e1921
Compare
renovate
bot
force-pushed
the
renovate/apollo-graphql-packages
branch
from
f2e1921 to
8499e2d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^3.12.2->^3.12.8^3.12.2->^3.12.8^3.12.2->^3.12.8^3.13.0->^4.0.0^3.13.0->^4.0.0This is a special PR that replaces
apollo-server-corewith the community suggested minimal stable replacement version.This is a special PR that replaces
apollo-server-expresswith the community suggested minimal stable replacement version.Release Notes
apollographql/apollo-client (@apollo/client)
v3.12.8Compare Source
Patch Changes
#12292
3abd944Thanks @phryneas! - Remove unused dependencyresponse-iterator#12287
bf313a3Thanks @phryneas! - Fixes an issue whereclient.watchFragment/useFragmentwith@includescrashes when a separate cache update writes to the conditionally included fields.v3.12.7Compare Source
Patch Changes
#12281
d638ec3Thanks @jerelmiller! - Make fatal tranport-level errors from multipart subscriptions available to the error link with theprotocolErrorsproperty.#12281
d638ec3Thanks @jerelmiller! - Fix the array type for theerrorsfield on theApolloPayloadResulttype. This type was always in the shape of the GraphQL error format, per the multipart subscriptions protocol and never a plain string or a JavaScript error object.v3.12.6Compare Source
Patch Changes
#12267
d57429dThanks @jerelmiller! - Maintain theTDatatype when used withUnmaskedwhenTDatais not a masked type generated from GraphQL Codegen.#12270
3601246Thanks @jerelmiller! - Fix handling of tagged/branded primitive types when used as scalar values withUnmasked.v3.12.5Compare Source
Patch Changes
#12252
cb9cd4eThanks @jerelmiller! - Changes the default behavior of theMaybeMaskedtype to preserve types unless otherwise specified. This change makes it easier to upgrade from older versions of the client where types could have unexpectedly changed in the application due to the default of trying to unwrap types into unmasked types. This change also fixes the compilation performance regression experienced when simply upgrading the client since types are now preserved by default.A new
modeoption has now been introduced to allow for the old behavior. See the next section on migrating if you wish to maintain the old default behavior after upgrading to this version.Migrating from <= v3.12.4
If you've adopted data masking and have opted in to using masked types by setting the
enabledproperty totrue, you can remove this configuration entirely:If you prefer to specify the behavior explicitly, change the property from
enabled: true, tomode: "preserveTypes":declare module "@​apollo/client" { interface DataMasking { - enabled: true + mode: "preserveTypes" } }If you rely on the default behavior in 3.12.4 or below and would like to continue to use unmasked types by default, set the
modetounmask:v3.12.4Compare Source
Patch Changes
4334d30Thanks @charpeni! - Fix an issue withrefetchQuerieswhere comparingDocumentNodes internally by references could lead to an unknown query, even though theDocumentNodewas indeed an active query—with a different reference.v3.12.3Compare Source
Patch Changes
#12214
8bfee88Thanks @phryneas! - Data masking: prevent infinite recursion ofContainsFragmentsRefstype#12204
851deb0Thanks @jerelmiller! - FixUnmaskedunwrapping tuple types into an array of their subtypes.#12204
851deb0Thanks @jerelmiller! - EnsureMaybeMaskeddoes not try and unwrap types that contain index signatures.#12204
851deb0Thanks @jerelmiller! - EnsureMaybeMaskeddoes not try to unwrap the type asUnmaskedif the type containsany.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - 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 was generated by Mend Renovate. View the repository job log.