Conversation
…elease notes Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
[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 |
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: pingcap/docs/.coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (3)
Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 1 remain after this review. 📝 WalkthroughWalkthroughRelease notes for versions 8.1.0, 8.1.2, and 8.2.0 receive wording revisions and clarifications to selected technical conditions, labels, and attributions. The described features, improvements, and fixes otherwise remain unchanged. ChangesRelease note updates
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Other Merge Risk: ⚪ Minimal · up to The checked release-note corrections preserve the documented behavior and compatibility conditions. No concrete merge-blocking risk remains. Architecture SummaryArchitecture risk: 🔵 Low · up to The change affects 1 system. Changed systems: Architecture concerns Review detailsSystems and components
Before / after behavior
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
What is changed, added or deleted? (Required)
Fixes translation defects in the Japanese release notes for v8.1.0, v8.1.2, and v8.2.0. This is round 2 of the
releases/review; round 1 is #24143. I checked each item against its EN bullet (release-8.5).Meaning fixes
CHECKconstraint vsJSON_SCHEMA_VALID().ANALYZEvsscan.tidb_persist_analyze_options = OFFvstidb_enable_column_tracking.TABLESAMPLEvsplan not supported.tidb_enable_async_merge_global_statsvsDistinct_count.INFORMATION_SCHEMA.PARTITIONS/TABLES/KEY_COLUMN_USAGE.PREDICATE COLUMNS.ADD COLUMN.TABLESAMPLEwith static prune mode.k8s.io/apilibrary version (8.1.2).Literals restored
@[hi-rustin], as in EN.>.Other fixes:
The 発売日 → リリース日 lines are not touched here; they are in #24146. The rendering of "disaggregated storage and compute" as 分散ストレージおよびコンピューティング (39 occurrences across the corpus) is also left for a separate term decision.
EN-side candidate, not changed: 8.1.0 "a union clustered index" probably means "composite clustered index".
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
JSON_SCHEMA_VALID()checks, TiCDC sync points, backup restoration, and configuration limits.