docs: update pipeline-4.8 site.yaml and releasenote

[tik-seven]

Summary by CodeRabbit

• New Features

  • Extended compatibility for Alauda DevOps Pipelines v4.8 and Connectors v1.8
  • Added GitOps Repo Update pipeline template for automated repository updates
  • Added Helm Chart Build Push Task for packaging and pushing Helm charts to OCI registries
  • Added Tekton metrics collection and display capabilities
  • Promoted Connectors Core Capabilities to Beta maturity

• Documentation

  • Updated compatibility matrix and release documentation with latest versions and fixes

[coderabbitai]

Walkthrough

This PR updates release documentation and configuration to reflect two new software versions: Alauda DevOps Pipelines v4.8 and Alauda DevOps Connectors v1.8. The changes include updating the compatibility matrix, documenting new features, and bumping version references in configuration files.

Changes

Cohort / File(s)	Summary
Release Notes Documentation docs/en/overview/release_notes.mdx	Extended compatibility matrix to include Pipelines v4.8 and Connectors v1.8; added Nexus build entry; documented three new v4.8 features (GitOps Repo Update pipeline, Helm Chart Build Push Task, Tekton metrics); promoted Connectors Core Capabilities to Beta maturity; updated fixed issues and known issues version references.
Configuration sites.yaml	Bumped alauda-devops-pipelines version from v4.7 to v4.8 and alauda-devops-connectors version from v1.7 to v1.8.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• docs:upgrade site.yaml; upgrade devops v4.2 releasenotes. #105: Updates the same documentation and configuration files for pipeline and connector version releases.
• docs: update Compatibility and Support Matrix; synchronize modify rel… #109: Makes overlapping edits to the compatibility matrix and version entries in release notes and sites.yaml.
• Modify the default redirect addresses and release notes for connector… #82: Modifies the same files to document new pipeline/connector versions and update version references.

Suggested reviewers

• yhuan123
• l-qing

Poem

🐰 New versions hop into the fold,
Pipeline v4.8 bold,
Connectors reach Beta with grace,
GitOps and Helm find their place,
Documentation renewed, tales retold! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The PR title 'docs: update pipeline-4.8 site.yaml and releasenote' accurately reflects the main changes: updating documentation files (site.yaml and release notes) to reflect pipeline v4.8 and connector v1.8 updates.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/en/overview/release_notes.mdx`:
- Around line 38-40: The three bullets repeat the prefix and contain minor
grammar/spacing issues; update them to be concise and consistent by: reference
the pipeline template name "GitOps Repo Update" and change its sentence to "In
v4.8, the GitOps Repo Update pipeline template updates files in a GitOps
repository, commits and pushes changes using git-cli, and optionally creates a
merge request (merge-request creation currently supports GitLab only)" ensuring
a space before the parenthesis and lowercase/consistent phrasing; update the
"Helm Chart Build Push" bullet to "In v4.8, a new Helm Chart Build Push Task
packages a Helm chart from a specified directory and pushes it to an OCI
registry using Helm or ORAS"; and fix the Tekton bullet to "In v4.8, adds
support for collecting and displaying Tekton component metrics" or "In v4.8, the
release adds support for collecting and displaying Tekton component metrics" so
the subject is present and grammar is correct; keep identifiers "GitOps Repo
Update", "Helm Chart Build Push", "Tekton", and "v4.8" to locate the lines.

---

ℹ️ Review info

Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 56dd6041-fbed-45f7-83c0-bdece18d0a03

📥 Commits

Reviewing files that changed from the base of the PR and between 5761c24 and 6c59760.

📒 Files selected for processing (2)

• docs/en/overview/release_notes.mdx
• sites.yaml