Update dependency @urql/core to v4.3.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@urql/core (source)	4.0.10 → 4.3.0

---

Release Notes

urql-graphql/urql (@​urql/core)

v4.3.0

Compare Source

Minor Changes

• Support Apollo Federation's format for subscription results in multipart/mixed responses (result properties essentially are namespaced on a payload key)
  Submitted by @​JoviDeCroock (See #​3499)
• Add support for sending persisted documents. Any DocumentNode with no/empty definitions and a documentId property is considered a persisted document. When this is detected a documentId parameter rather than a query string is sent to the GraphQL API, similar to Automatic Persisted Queries (APQs). However, APQs are only supported via @urql/exchange-persisted, while support for documentId is now built-in
  Submitted by @​kitten (See #​3515)

Patch Changes

• Allow url to be a plain, non-URL pathname (i.e. /api/graphql) to be used with preferGetMethod
  Submitted by @​akrantz01 (See #​3514)
• Correctly support the Headers class being used in fetchOptions
  Submitted by @​JoviDeCroock (See #​3505)

v4.2.3

Compare Source

Patch Changes

• Add back our cache-outcome on the document-cache, this was behind a development flag however in our normalized cache we always add it already
  Submitted by @​JoviDeCroock (See #​3464)

v4.2.2

Compare Source

Patch Changes

• ⚠️ Fix the default cacheExchange crashing on cache-only request policies with cache misses due to undefined results
  Submitted by @​JoviDeCroock (See #​3459)

v4.2.1

Compare Source

Patch Changes

• ⚠️ Fix incorrect JSON stringification of objects from different JS contexts. This could lead to invalid variables being generated in the Vercel Edge runtime specifically
  Submitted by @​SoraKumo001 (See #​3453)

v4.2.0

Compare Source

Minor Changes

• Try to parse text/plain content-type as JSON before bailing out with an error
  Submitted by @​JoviDeCroock (See #​3430)

v4.1.4

Compare Source

Patch Changes

• Implement new @defer / @stream transport protocol spec changes
  Submitted by @​JoviDeCroock (See #​3389)
• Support non spec-compliant error bodies, i.e. the Shopify API does return errors but as an object. Adding
  a check whether we are really dealing with an Array of errors enables this
  Submitted by @​JoviDeCroock (See #​3395)
• ⚠️ Fix preferGetMethod: 'force' | 'within-url-limit' not being applied correctly by the Client
  Submitted by @​Burbenog (See #​3403)

v4.1.3

Compare Source

Patch Changes

• ⚠️ Fix missing teardown operation handling in the ssrExchange. This could lead to duplicate network operations being executed
  Submitted by @​kitten (See #​3386)

v4.1.2

Compare Source

Patch Changes

• Explicitly unblock client.reexecuteOperation calls to allow stalled operations from continuing and re-executing. Previously, this could cause @urql/exchange-graphcache to stall if an optimistic mutation led to a cache miss
  Submitted by @​kitten (See #​3363)

v4.1.1

Compare Source

Patch Changes

• Add case for subscriptionExchange to handle GraphQLError[] received in the error observer callback.
  Note: This doesn't strictly check for the GraphQLError shape and only checks for arrays and receiving errors in the ExecutionResult on the next observer callback is preferred and recommended for transports
  Submitted by @​kitten (See #​3346)

v4.1.0

Compare Source

Minor Changes

• Update formatDocument to output FormattedNode type mapping. The formatter will now annotate added __typename fields with _generated: true, place selection nodes' directives onto a _directives dictionary, and will filter directives to not include "_" underscore prefixed directives in the final query. This prepares us for a feature that allows enhanced client-side directives in Graphcache
  Submitted by @​kitten (See #​3317)

Patch Changes

• Add OperationContext.optimistic flag as an internal indication on whether a mutation triggered an optimistic update in @urql/exchange-graphcache's cacheExchange
  Submitted by @​kitten (See #​3308)

v4.0.11

Compare Source

Patch Changes

• Re-order maskTypename to apply masking earlier in the chain
  Submitted by @​kitten (See #​3298)
• ⚠️ Fix ssrExchange not formatting query documents using formatDocument. Without this call we'd run the risk of not having __typename available on the client-side when rehydrating
  Submitted by @​kitten (See #​3288)
• Add deprecation notice for maskTypename option.
  Masking typenames in a result is no longer recommended. It’s only
  useful when multiple pre-conditions are applied and inferior to
  mapping to an input object manually
  Submitted by @​kitten (See #​3299)

---

Configuration

📅 Schedule: (UTC)

• 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.