chore(deps): update dependency @urql/exchange-graphcache to v5.2.0 (master) - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@urql/exchange-graphcache (source)	5.0.9 -> 5.2.0

---

Release Notes

urql-graphql/urql

v5.2.0

Minor Changes

• Add isOfflineError option to the offlineExchange to allow it to be customized to different conditions to determine whether an operation has failed because of a network error
  Submitted by @​robertherber (See #​3020)
• Allow updates config to react to arbitrary type updates other than just Mutation and Subscription fields.
  You’ll now be able to write updaters that react to any entity field being written to the cache,
  which allows for more granular invalidations. Note: If you’ve previously used updates.Mutation
  and updated.Subscription with a custom schema with custom root names, you‘ll get a warning since
  you’ll have to update your updates config to reflect this. This was a prior implementation
  mistake!
  Submitted by @​kitten (See #​2979)

Patch Changes

• ⚠️ Fix regression which caused partial results, whose refetches were blocked by the looping protection, to not have a stale: true flag added to them. This is a regression from https://github.com/urql-graphql/urql/pull/2831 and only applies to cacheExchanges that had the schema option set
  Submitted by @​kitten (See #​2999)
• Add invariant to data layer that prevents cache writes during cache query operations. This prevents cache.writeFragment, cache.updateQuery, and cache.link from being called in resolvers for instance
  Submitted by @​kitten (See #​2978)
• Updated dependencies (See #​3007, #​2962, #​3007, #​3015, and #​3022)
  • @​urql/core@​3.2.0

---

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

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: nuxt/pnpm-lock.yaml

Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit