[upgrade doc]: prerequisite of ACP v4.1

[IceCodeNew]

Summary by CodeRabbit

• Documentation
  • Updated the list of supported platform versions for upgrade, now covering versions from 3.18.0 to 4.0.3.
  • Revised the upgrade package description to reflect the new supported upgrade paths.
  • Removed manual command-line instructions for uninstalling the etcd sync plugin when upgrading from version 3.16 in the global cluster upgrade procedure.

[coderabbitai]

Walkthrough

The documentation for the pre-upgrade process has been updated to reflect new supported upgrade paths. Support for 3.16.x versions was removed, and support for 4.0.2 and 4.0.3 was added. The description of upgrade package usage was also revised to align with the latest supported versions. Additionally, the manual command-line procedure for uninstalling the etcd sync plugin when upgrading from 3.16 was removed from the global cluster upgrade documentation.

Changes

Cohort / File(s)	Change Summary
Pre-upgrade Documentation Update docs/en/upgrade/pre-upgrade.mdx	Updated supported upgrade version list; removed 3.16.x, added 4.0.2 and 4.0.3; revised upgrade package description.
Global Cluster Upgrade Documentation Cleanup docs/en/upgrade/upgrade_global_cluster.mdx	Removed the "Upgrading from 3.16" tab section with manual commands to uninstall the etcd sync plugin; retained "Upgrading from 3.18" instructions.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

A bunny with docs in its paw,
Hopped through versions without a flaw.
Out with old, in with new,
4.0.3 now joins the crew!
The old commands took a leap,
Now cleaner docs help you keep! 🐇✨

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2269e99 and b7e2069.

📒 Files selected for processing (1)

• docs/en/upgrade/upgrade_global_cluster.mdx (0 hunks)

💤 Files with no reviewable changes (1)

• docs/en/upgrade/upgrade_global_cluster.mdx

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch upgrade-doc

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

docs/en/upgrade/pre-upgrade.mdx (1)

40-41: Scope of “same upgrade package” is ambiguous

The sentence now reads “platforms upgrading from version 3.18 to 4.1 use the same upgrade package…”. Operators on 4.0.x—which are listed as supported sources above—may wonder whether this also applies to them.

Consider rephrasing to cover all supported sources explicitly, e.g.:

-For platforms upgrading from version `3.18` to `4.1`, the **upgrade package is the same as the installation package**.
+For all supported source versions (`3.18.x` and `4.0.x`) upgrading to `4.1`, the **upgrade package is identical to the installation package**.

This makes the instruction unambiguous.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3fe11c4 and 2269e99.

📒 Files selected for processing (1)

• docs/en/upgrade/pre-upgrade.mdx (2 hunks)