Repository navigation
Conversation
|
Skipping CI for Draft Pull Request. |
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
Walkthrough
Merge Risk:
|
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
There was a problem hiding this comment.
Actionable comments posted: 1
🔇 Additional comments: 2
tidb-cloud/releases/release-notes-2022.md-72-72: 1
72-72:Minor · Maintainability & Code Quality · Quick win
⚠️ Unverified finding
Verification ran but could not confirm this finding. It is shown for review, not as a verified issue.Clarify the changefeed sentence.
The nested
のphrases make the relationship between Dedicated Tier data and Changefeed difficult to parse. State directly that users can use Changefeed to stream Dedicated Tier data.As per path instructions, the exact replacement is included as a committable suggestion because the fix is contiguous and deterministic.
Committable suggestion
-- Dedicated Tierのデータのストリーミングに[チェンジフィード](/tidb-cloud/changefeed-overview.md)の使用をサポートします。 +- Dedicated Tierのデータをストリーミングするために、[チェンジフィード](/tidb-cloud/changefeed-overview.md)を使用できます。Source: Path instructions
tidb-cloud/releases/release-notes-2025.md-199-199: 1
199-199:Minor · Maintainability & Code Quality · Quick win
⚠️ Unverified finding
Verification ran but could not confirm this finding. It is shown for review, not as a verified issue.Use a concise Japanese construction.
ことができますis redundant in this release-note sentence. Apply the exact replacement below.- [TiDB Cloud Starter](/tidb-cloud/select-cluster-tier.md#starter)ではインプレースリストア機能が削除され、バックアップを同じクラスタに直接リストアできなくなります。この変更は、アクティブな本番データの誤った上書きや潜在的なデータ損失の防止に役立ちます。LanguageTool flags this construction as potentially redundant. As per path instructions, the exact replacement is provided as a committable suggestion.
Sources: Path instructions, Linters/SAST tools

Review info
-
Run configuration-
- Source mode: Auto
- Repository: pingcap/docs
- Branch: i18n-ja-release-8.5
- File: .coderabbit.yaml
- Commit: 1ab23c8
- Layers: Repository YAML
- Review profile: ASSERTIVE
- Plan: Advanced
- Run ID:
4aec5325-a601-401c-9696-0f6c9ec0ccad
Files selected for processing: 15-
tidb-cloud/releases/_index.mdtidb-cloud/releases/notification-2023-08-31-console-maintenance.mdtidb-cloud/releases/notification-2024-04-09-monitoring-features-maintenance.mdtidb-cloud/releases/notification-2024-04-16-monitoring-features-maintenance.mdtidb-cloud/releases/notification-2024-04-18-dm-feature-maintenance.mdtidb-cloud/releases/notification-2024-09-15-console-maintenance.mdtidb-cloud/releases/release-notes-2020.mdtidb-cloud/releases/release-notes-2021.mdtidb-cloud/releases/release-notes-2022.mdtidb-cloud/releases/release-notes-2023.mdtidb-cloud/releases/release-notes-2024.mdtidb-cloud/releases/release-notes-2025.mdtidb-cloud/releases/tidb-cloud-kernel-versioning.mdtidb-cloud/releases/tidb-cloud-release-notes.mdtidb-cloud/releases/tidb-x-cloud.202510.1.md
Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 2 remain after this review.
-
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ase notes Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ase notes Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
a90be1c to
6dcc21f
Compare
There was a problem hiding this comment.
Actionable comments posted: 1

Review info
-
Run configuration-
- Source mode: Auto
- Repository: pingcap/docs
- Branch: i18n-ja-release-8.5
- File: .coderabbit.yaml
- Commit: 5192bed
- Layers: Repository YAML
- Review profile: ASSERTIVE
- Plan: Advanced
- Run ID:
cfbcc96e-3b12-452a-80d1-7a7089920675
Files selected for processing: 3-
tidb-cloud/releases/release-notes-2023.mdtidb-cloud/releases/release-notes-2024.mdtidb-cloud/releases/tidb-cloud-release-notes.md
Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 3 remain after this review.
-
…ease notes Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
What is changed, added or deleted? (Required)
This PR fixes the Japanese TiDB Cloud release notes under
tidb-cloud/releases/after a second line-by-line review against the English source (release-8.5at 6fa2484). The review covered all 19 files intidb-cloud/releases/; 15 needed changes. Link targets and anchors are unchanged except for one broken anchor (see "Sync lag").Changelog entries that were translated as requests (「〜してください」) now state what changed (「〜しました」), for example "Upgrade the default TiDB version" and "Add Billing Profile".
Mistranslations:
Dropped particles after links (「〜)ご覧ください」 → 「〜)をご覧ください」, 「〜)導入します」 → 「〜)を導入します」, and は/では after product links) and duplicated fragments (「システム[システムステータス]」, 「タイム[タイムゾーン]」) are fixed.
Bold UI labels and product names that had been translated are restored to English, for example Select Region, Summary By Service, Connect to TiDB, Clusters, Integrations, Postman, Chat2Query API, AWS PrivateLink, Private Service Connect, and Amazon MSK Provisioned.
Link texts:
[バージョンX.Y.Z]→[vX.Y.Z]as in the English, and English link texts are translated to the Japanese titles of their target pages.Sync lag: the restore link in
release-notes-2025.mdpointed to an anchor that no longer exists (#perform-the-restore→#restore-to-a-new-instance), and one changefeed note still had the old wording.One rendering per term: クラシックTiDB for "classic TiDB", 販売代理店 for "reseller", キャパシティ for compute capacity, リージョン for region, and 全文検索.
Zonal and regional high availability are now ゾーン高可用性 and リージョン高可用性 in
tidb-cloud-release-notes.md, as defined inserverless-high-availability.md(was Regional High Availability left in English, リージョンごとの高可用性, and リージョンの高可用性). In the same entry, the regional and zonal RCU prices are now リージョン RCU, ゾーン RCU, and リージョン価格.Lines that the next weekly sync will rewrite (the Chat2Query removal in tidb-cloud: remove Chat2Query documentation #24549 and one line added after the last sync) are left unchanged to avoid conflicts.
Redundant can-form: 「〜することができます」 → 「〜できます」 (for example 設定することができます → 設定できます, 有効にすることができます → 有効にできます). Other conjugations are changed the same way (することができ、 → でき、, することができません → できません, することができました → できました, and so on). 「〜することもできます」 and 「〜することはできません」 are kept. Text inside code is not changed.
"maintenance window" now uses one term, メンテナンスウィンドウ (was also メンテナンス期間, メンテナンス時間, and メンテナンス時間帯). This includes three maintenance notifications that this PR did not edit before.
Spaces between katakana words, left over from machine translation, are removed outside code (for example パフォーマンス テスト → パフォーマンステスト, アクセス リスト → アクセスリスト). Spaces between Latin and Japanese text are not changed.
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions.
What is the related PR or file link(s)?
AI agent involvement
Do your changes match any of the following descriptions?
🤖 Generated with Claude Code
Summary by CodeRabbit