chore(deps): bump react-relay from 10.1.3 to 11.0.0 in /accounter/web

[dependabot]

Bumps react-relay from 10.1.3 to 11.0.0.

Release notes

Sourced from react-relay's releases.

v11.0.0

For our announcement on Relay Hooks, check out our blog posts on relay.dev and Facebook Open Source. For docs, see our updated docs website at relay.dev/docs, and for an update on our upcoming releases, see this issue.

Breaking

• New version of fetchQuery:
  • New: New version of fetchQuery now returns a lazy Observable which you can subscribe to. It will perform in-flight request de-duping of identical requests. Ignores any Network Layercaching by default, but supports a [fetchPolicy](https://relay.dev/docs/en/experimental/a-guided-tour-of-relay#fetch-policies) to check data cached in the Relay Store.
  • Deprecated: Previous version of fetchQuery renamed to **** fetchQuery_DEPRECATED. Previous behavior returns a Promise (can’t be observed). No request de-duping.
  • Changes in Exports:
    • react-relay: fetchQuery exported from react-relay now has updated behavior and function signature. To access previous version of fetchQuery, import fetchQuery_DEPRECATED from react-relay or react-relay/legacy.
    • relay-runtime: fetchQuery exported from relay-runtime now has updated behavior and function signature. To access previous version of fetchQuery, import fetchQuery_DEPRECATED from relay-runtime.
• getDataID was renamed from UNSTABLE_DO_NOT_USE_getDataID. This config option is now stable. It can be passed to the Relay Environment and Relay Store as an option that will be used to compute the Data ID for the given record.
• Default value for gcReleaseBufferSize is now 10 (previously 0).
  • When a query is manually released, for example when a query component unmounts (QueryRenderer or useLazyLoadQuery), Relay will temporarily retain the query in the “release buffer” until the buffer is full. With a buffer size of 0, released queries would not go into the buffer and would be immediately removed from the store cache.
  • With a default buffer size of 10, this means that queries will remained cached in the store for a longer period of time after they unmount, which allows fetch policies like store-or-network. to actually reuse cached data when navigating back to previously visited views.

If upgrading from experimental release

• The default UNSTABLE_renderPolicy is now always “partial”. We don’t expect this to produce any issues, and will only affect you if you are upgrading from an experimental release. This option can still be configured, but we will completely remove it in the upcoming releases.

Added

Relay Hooks

• New Relay Hooks APIs added to react-relay and react-relay/hooks. See this issue for more details.
  • relay-experimental has been removed from the source code, and no new experimental builds will be published to npm.
  • We will share more external communications with the community as well as publish our updated docs once a stable release is published.
• New version of fetchQuery added. See description in Breaking Changes.

General

• Added ConnectionHandler.getConnectionID to make it easier to get a connection ID for usage in updaters or declarative connection mutations (@​kyarik: facebook/relay#3332)

Improvements

If upgrading from experimental release

• Hooks are now resilient to React effects being re-invoked (e.g. during Fast Refresh).
• Un-actionable warning that fired when fragment data was missing without being fetched has been removed.
• loadQuery accepts a fetchPolicy of 'store-only'
• loadQuery now warns, instead of throwing, if called during the render phase.

General

• getDataID is now a stable config option. See description in Breaking Changes.
• Default value for gcReleaseBufferSize is now 10. See description in Breaking Changes.

... (truncated)

Commits

• f448670 v11.0.0
• 432f11b Remove duplicated docs
• e1cc36b Small copy updates in blog post
• bf38b85 Remove docusaurus.yml to turn off legacy deploy process
• 885d7d3 Add v11.0.0 version
• 4925dee Move docs to docs/current
• 2590c24 Add missing link in Suspense compatibility
• 0459eae Relay blog post should use useBaseUrl
• ae82bb3 Consolidate updating connections guides
• 7fa7c60 Consolidate compiler / workflow guides
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[MoSattler]

@dependabot rebase

[MoSattler]

@dependabot rebase

[MoSattler]

@dependabot rebase

[MoSattler]

@dependabot rebase

[dependabot]

Looks like this PR is already up-to-date with master! If you'd still like to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.

[github-actions]

Terraform Plan 📖

Show Provider Plan

digitalocean_container_registry.accounter: Refreshing state... [id=accounter]
digitalocean_database_cluster.database: Refreshing state... [id=455151ed-8a33-4a2b-bf3c-56c189779760]
digitalocean_kubernetes_cluster.accounter: Refreshing state... [id=d285b7e9-271a-49da-b0a8-21b81f05cd20]
digitalocean_database_firewall.database-fw: Refreshing state... [id=455151ed-8a33-4a2b-bf3c-56c189779760-20210204084818819800000001]

No changes. Infrastructure is up-to-date.

This means that Terraform did not detect any differences between your
configuration and real physical resources that exist. As a result, no
actions need to be performed.

Show Cluster Plan

module.loadbalancer.helm_release.ingress-nginx: Refreshing state... [id=ingress-nginx]
digitalocean_spaces_bucket.assets: Refreshing state... [id=accounter-assets-bucket]
module.server.kubernetes_secret.secret-key: Refreshing state... [id=default/secret-key]
module.connector.kubernetes_secret.zoom-workspace-credentials: Refreshing state... [id=default/zoom-workspace-credentials]
module.connector.kubernetes_secret.token-encryption: Refreshing state... [id=default/token-encryption]
module.connector.kubernetes_secret.slack-credentials: Refreshing state... [id=default/slack-credentials]
module.server.kubernetes_service.server: Refreshing state... [id=default/server]
module.connector.kubernetes_service.connector: Refreshing state... [id=default/connector]
module.server.kubernetes_secret.sendgrid-api-key: Refreshing state... [id=default/sendgrid-api-key]
module.loadbalancer.kubernetes_service.loadbalancer: Refreshing state... [id=default/loadbalancer]
module.connector.kubernetes_secret.google-workspace-credentials: Refreshing state... [id=default/google-workspace-credentials]
module.web.kubernetes_service.web: Refreshing state... [id=default/web]
module.connector.kubernetes_secret.github-credentials: Refreshing state... [id=default/github-credentials]
module.loadbalancer.kubernetes_namespace.cert-manager: Refreshing state... [id=cert-manager]
digitalocean_container_registry_docker_credentials.registry: Refreshing state... [id=accounter]
module.server.kubernetes_secret.database-credentials: Refreshing state... [id=default/database-credentials]
module.server.kubernetes_secret.s3-credentials: Refreshing state... [id=default/s3-credentials]
module.loadbalancer.helm_release.cert-manager: Refreshing state... [id=cert-manager]
kubernetes_secret.registry-accounter: Refreshing state... [id=default/registry-accounter]
module.loadbalancer.kubernetes_deployment.loadbalancer: Refreshing state... [id=default/loadbalancer]
module.connector.kubernetes_deployment.connector: Refreshing state... [id=default/connector]
module.server.kubernetes_deployment.server: Refreshing state... [id=default/server]
module.web.kubernetes_deployment.web: Refreshing state... [id=default/web]
module.loadbalancer.kubernetes_manifest.cert-issuer: Refreshing state...
module.loadbalancer.kubernetes_ingress.loadbalancer: Refreshing state... [id=default/loadbalancer]

No changes. Infrastructure is up-to-date.

This means that Terraform did not detect any differences between your
configuration and real physical resources that exist. As a result, no
actions need to be performed.

[github-actions]

🎉 This PR is included in version 1.76.0 🎉

The release is available on:

• GitHub release
• v1.76.0

Your semantic-release bot 📦🚀