chore(deps): update dependency @urql/core to v3.2.2 (master)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@urql/core (source)	3.1.1 -> 3.2.2

---

Release Notes

urql-graphql/urql

v3.2.2

Compare Source

Patch Changes

• ⚠️ Fix generated empty Variables type as passed to generics, that outputs a type of { [var: string]: never; }.
  A legacy/unsupported version of typescript-urql, which wraps urql's React hooks, generates
  empty variables types as the following code snippet, which is not detected:

  type Exact<T extends { [key: string]: unknown }> = { [K in keyof T]: T[K] };
  type Variables = Exact<{ [key: string]: never }>;

  Submitted by @​kitten (See #​3029)

v3.2.1

Patch Changes

• Bump to @urql/[email protected] due to invalid 3.2.0 release
  Submitted by @​kitten (See a84268db)

v3.2.0

Minor Changes

• Update support for the "Incremental Delivery" payload specification, accepting the new incremental property on execution results, as per the specification. This will expand support for newer APIs implementing the more up-to-date specification
  Submitted by @​kitten (See #​3007)
• Update default Accept header to include multipart/mixed and application/graphql-response+json. The former seems to now be a defactor standard-accepted indication for support of the "Incremental Delivery" GraphQL over HTTP spec addition/RFC, and the latter is an updated form of the older Content-Type of GraphQL responses, so both the old and new one should now be included
  Submitted by @​kitten (See #​3007)

Patch Changes

• Add TSDoc annotations to all external @urql/core APIs
  Submitted by @​kitten (See #​2962)
• ⚠️ Fix subscriptions not being duplicated when hasNext isn't set. The hasNext field is an upcoming "Incremental Delivery" field. When a subscription result doesn't set it we now set it to true manually. This indicates to the dedupExchange that no duplicate subscription operations should be started
  Submitted by @​kitten (See #​3015)
• Expose consistent GraphQLRequestParams utility type from which GraphQLRequests are created in all bindings
  Submitted by @​kitten (See #​3022)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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

[renovate]

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.

---

• Branch has one or more failed status checks

[dargmuesli]

dotansimha/graphql-code-generator-community#297

[dargmuesli]

See #1160.

[maevsi-bot]

🎉 This PR is included in version 1.10.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀