Revert "chore: add v3 plugin release notes"

[danielfbm]

Reverts #47

Summary by CodeRabbit

• Documentation
  • Removed legacy English documentation pages for Jenkins v3, Katanomi (DevOps v3), and Knative (Eventing v3), including their index pages, lifecycle policies, and release notes. Associated version timelines, compatibility matrices, and feature/issue sections were removed with these pages.
  • Updated the v3-to-v4 upgrade guide to use the new operator names Katanomi and Knative (replacing Alauda Devops v3 and Alauda Devops Eventing v3) and adjusted UI upgrade instructions accordingly. The compatibility matrix now reflects the updated naming.

[coderabbitai]

Walkthrough

Removes English documentation pages for Jenkins, Katanomi, and Knative (index, lifecycle_policy, release_notes). Updates the v3→v4 upgrade guide to rename operators from “Alauda Devops v3 / Eventing v3” to “Katanomi / Knative,” keeping version placeholders unchanged. No code or APIs affected.

Changes

Cohort / File(s)	Summary of modifications
Remove Jenkins docs docs/en/jenkins/index.mdx, docs/en/jenkins/lifecycle_policy.mdx, docs/en/jenkins/release_notes.mdx	Deleted Jenkins v3 index, lifecycle policy, and release notes pages.
Remove Katanomi (DevOps v3) docs docs/en/katanomi/index.mdx, docs/en/katanomi/lifecycle_policy.mdx, docs/en/katanomi/release_notes.mdx	Deleted Katanomi (formerly DevOps v3) index, lifecycle policy, and release notes pages.
Remove Knative (Eventing v3) docs docs/en/knative/index.mdx, docs/en/knative/lifecycle_policy.mdx, docs/en/knative/release_notes.mdx	Deleted Knative (Eventing v3) index, lifecycle policy, and release notes pages.
Update upgrade guide naming docs/en/upgrade/upgrading-devops-v3-to-v4.mdx	Renamed operators in compatibility matrix and instructions: “Alauda Devops v3” → “Katanomi”; “Alauda Devops Eventing v3” → “Knative”.

Sequence Diagram(s)

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• chore: add v3 plugin release notes #47 — Touches the same MDX docs (indexes, lifecycle, release notes) with opposing operations, directly overlapping.
• feat: add a new lifecycle policy document and update the release note… #36 — Modifies lifecycle and release notes for v3; related to the removal of those pages here.
• Upgrading Alauda DevOps from ACP 3.18 to 4.1. #40 — Edits the same upgrade guide; related to the operator naming updates in this PR.

Suggested reviewers

• lentil1016
• l-qing

Poem

A nibble of docs, a hop through time,
I tidied the trails, made labels align.
Jenkins, Katanomi, Knative—goodbye old signs,
Upgrade paths polished, concise by design.
With whiskers twitching, I ship this fine. 🐇✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch revert-47-chore/v3-release-note-main

---

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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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: 0

🧹 Nitpick comments (2)

docs/en/upgrade/upgrading-devops-v3-to-v4.mdx (2)

16-17: Renamed operators to Katanomi/Knative — confirm mapping and version semantics

Looks good, but please verify that:

• Katanomi maps to the previously documented “Alauda DevOps v3” operator, and Knative maps to “Alauda DevOps Eventing v3”.
• v3.20.z is still the correct minimal/required version for both in this upgrade path.

Optionally, add a short note for readers migrating from older docs to reduce confusion.

Here’s a small note you could add under the compatibility table (optional):
"Note: Katanomi and Knative were previously referred to as Alauda DevOps v3 and Alauda DevOps Eventing v3, respectively."

---

56-56: UI section: include former names for discoverability (optional)

If the UI or customer vocabulary still includes the former names, consider mentioning them inline to help readers find the right operators.

-For `Katanomi`, `Knative`, and `Alauda DevOps Jenkins v3` Operators, complete the upgrade through the UI after the `ACP` upgrade:
+For `Katanomi` (formerly "Alauda DevOps v3"), `Knative` (formerly "Alauda DevOps Eventing v3"), and `Alauda DevOps Jenkins v3` Operators, complete the upgrade through the UI after the `ACP` upgrade:

📜 Review details

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

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between d1d7b75 and a3faac0.

📒 Files selected for processing (10)

• docs/en/jenkins/index.mdx (0 hunks)
• docs/en/jenkins/lifecycle_policy.mdx (0 hunks)
• docs/en/jenkins/release_notes.mdx (0 hunks)
• docs/en/katanomi/index.mdx (0 hunks)
• docs/en/katanomi/lifecycle_policy.mdx (0 hunks)
• docs/en/katanomi/release_notes.mdx (0 hunks)
• docs/en/knative/index.mdx (0 hunks)
• docs/en/knative/lifecycle_policy.mdx (0 hunks)
• docs/en/knative/release_notes.mdx (0 hunks)
• docs/en/upgrade/upgrading-devops-v3-to-v4.mdx (2 hunks)

💤 Files with no reviewable changes (9)

• docs/en/katanomi/index.mdx
• docs/en/knative/index.mdx
• docs/en/knative/lifecycle_policy.mdx
• docs/en/katanomi/lifecycle_policy.mdx
• docs/en/knative/release_notes.mdx
• docs/en/jenkins/index.mdx
• docs/en/katanomi/release_notes.mdx
• docs/en/jenkins/release_notes.mdx
• docs/en/jenkins/lifecycle_policy.mdx

🧰 Additional context used

🪛 LanguageTool

docs/en/upgrade/upgrading-devops-v3-to-v4.mdx

[grammar] ~16-~16: There might be a mistake here.
Context: ... Katanomi | v3.20.z | | Knative | v3.20.z ...

(QB_NEW_EN)

---

[grammar] ~17-~17: There might be a mistake here.
Context: ... Knative | v3.20.z | | Alauda DevOps Jenkins v3 | v3.20.z ...

(QB_NEW_EN)