docs(upgrade): scope upgrade page to v4.4.0 with plugin dependencies and Important Notes#52
docs(upgrade): scope upgrade page to v4.4.0 with plugin dependencies and Important Notes#52SuJinpei wants to merge 8 commits into
Conversation
…nt Notes The operator-level Upgrade page went straight into the MySQL-PXC migration checklist without stating the foundational plugin dependencies, unlike the Kafka upgrade doc. Add a Prerequisites section with a Plugin Dependencies table and Important Notes: - Data Services Essentials (Application Services Core) v4.4.0+ - Data Services RDS Framework v4.3.x - upgrade order: base plugins before the operator - PXC-removal irreversibility and operator no-rollback callouts Point readers to the OperatorHub Upgrade prompt for plugin version deltas (the Release Notes carry no compatibility matrix). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
More reviews will be available in 53 minutes and 5 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughThe installation and upgrade docs now require Essentials for v4.4.0, add v4.4.0 upgrade prerequisites with plugin version ordering, and mark the rollback considerations heading with an explicit anchor. Changesv4.4.0 Documentation Updates
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 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 |
…dencies The query-analytics-operator (slow query logging / query analysis, optional companion to MySQL-MGR) must be upgraded to v4.4.0+ when in use. Add it to the Plugin Dependencies table and Important Notes. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Retitle to "Upgrade to v4.4.0", add a scoping intro that links to the patch-version upgrade guide, and make the Prerequisites and Plugin Dependencies wording v4.4.0-specific. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…ptional Reconcile the Essentials install note with the v4.4.0 plugin dependency: it is a required foundational platform component (also called Application Services Core), v4.4.0+, not an optional web-console-only plugin. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
… optional The RDS Framework is the base operator framework the MySQL operator extends; it is required (v4.3.x), not an optional web-console-only plugin. Mirror the Essentials fix. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…RDS Framework v4.3.x Correct the row-2 base dependency: the MySQL operator extends the rds-operator multi-database base operator, which must be v4.3.0 or higher (was mislabeled as RDS Framework v4.3.x). Update the dependency table, warning, Important Notes, and the installation tip accordingly. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…ange The column header already means "or higher", so the cells now list the bare minimum version (v4.4.0, v4.3.0) instead of "vX or higher". Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
What
The page is now scoped explicitly to the v4.4.0 upgrade (retitled "Upgrade to v4.4.0", with a link to the patch-version upgrade guide for z-stream upgrades).
The operator-level Upgrade page (
docs/en/upgrade.mdx) previously dove straight into the MySQL-PXC migration checklist and never stated the foundational plugin dependencies — unlike the Kafka upgrade doc, which leads with Prerequisites and a plugin/RDS-Framework requirement.This adds a Prerequisites section before the PXC checklist:
query-analytics-operator, optional)Notes
\{#id}anchors (doom 1.22.x auto-slug does not reliably match).🤖 Generated with Claude Code
Summary by CodeRabbit