i18n-zh-release-8.5: translate Cloud doc changes from pingcap/docs release-8.5 on 2026-07-01

[github-actions]

What is changed, added or deleted? (Required)

Translate Cloud documentation changes from pingcap/docs release-8.5 to Chinese via ai-pr-translator commit-diff sync.

English commit diff:

6a3301e...42da425

Which TiDB version(s) do your changes apply to? (Required)

• i18n-zh-release-8.5

What is the related PR or file link(s)?

• Source repo: pingcap/docs
• Source branch: release-8.5
• Cloud TOCs: TOC-tidb-cloud.md,TOC-tidb-cloud-starter.md,TOC-tidb-cloud-essential.md,TOC-tidb-cloud-premium.md,TOC-tidb-cloud-releases.md
• Source files: TOC-tidb-cloud-essential.md,TOC-tidb-cloud-premium.md,TOC-tidb-cloud-starter.md,TOC-tidb-cloud.md,mysql-compatibility.md,pessimistic-transaction.md,sql-statements/sql-statement-add-index.md,sql-statements/sql-statement-create-index.md,sql-statements/sql-statement-create-table.md,sql-statements/sql-statement-flashback-cluster.md,system-variables.md,tidb-cloud/backup-and-restore.md,tidb-cloud/branch-github-integration.md,tidb-cloud/branch-manage.md,tidb-cloud/branch-overview.md,tidb-cloud/connect-via-standard-connection-serverless.md,tidb-cloud/dedicated/_index.md,tidb-cloud/essential-changefeed-overview.md,tidb-cloud/essential-database-audit-logging.md,tidb-cloud/essential/_index.md,tidb-cloud/limited-sql-features-tidb-x.md,tidb-cloud/limited-sql-features.md,tidb-cloud/migrate-from-mysql-using-data-migration.md,tidb-cloud/premium/_index.md,tidb-cloud/premium/connect-to-premium-via-aws-private-endpoint.md,tidb-cloud/releases/tidb-cloud-release-notes.md,tidb-cloud/security-concepts.md,tidb-cloud/serverless-export.md,tidb-cloud/serverless-private-link-connection.md,tidb-cloud/set-up-private-endpoint-connections-serverless.md,tidb-cloud/set-up-private-endpoint-connections.md,tidb-cloud/starter/_index.md,tidb-cloud/tidb-cloud-import-local-files.md
• Sync outcome: failure

Translation failures

The following files were not translated automatically and must be handled manually before merging.

• tidb-cloud/dedicated/_index.md: Could not get target file content for tidb-cloud/dedicated/_index.md
• tidb-cloud/essential/_index.md: Could not get target file content for tidb-cloud/essential/_index.md
• tidb-cloud/premium/_index.md: Could not get target file content for tidb-cloud/premium/_index.md
• tidb-cloud/starter/_index.md: Could not get target file content for tidb-cloud/starter/_index.md

Docs with document structure mismatches after translation

The following files were translated successfully, but their Markdown heading or CustomContent structure does not match the source HEAD file.

• tidb-cloud/branch-overview.md: heading level sequence differs
  • Source: #x1 ##x5
  • Target: #x1 ##x4
  • First difference: heading 6: source ##, target (missing)
• tidb-cloud/set-up-private-endpoint-connections-serverless.md: heading level sequence differs
  • Source: #x1 ##x4 ###x4 ##x1 ###x5 ##x1 ###x1
  • Target: #x1 ##x4 ###x1 ##x1 ###x8 ##x1 ###x1
  • First difference: heading 7: source ###, target ##

Before merging this PR, manually translate the failed files above or rerun this workflow with workflow_dispatch and file_names set to those paths.

Do your changes match any of the following descriptions?

• Delete files
• Change aliases
• Need modification after applied to another branch
• Might cause conflicts after applied to another branch

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign qiancai for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

Hi @github-actions[bot]. Thanks for your PR.

I'm waiting for a pingcap member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.