Skip to content

docs:upgrade site.yaml; upgrade devops v4.2 releasenotes.#105

Merged
tik-seven merged 3 commits intoalauda:mainfrom
tik-seven:docs/update-site-yaml
Jan 23, 2026
Merged

docs:upgrade site.yaml; upgrade devops v4.2 releasenotes.#105
tik-seven merged 3 commits intoalauda:mainfrom
tik-seven:docs/update-site-yaml

Conversation

@tik-seven
Copy link
Copy Markdown
Contributor

@tik-seven tik-seven commented Jan 22, 2026

docs:upgrade site.yaml; upgrade devops v4.2 releasenotes.

Summary by CodeRabbit

  • Documentation

    • Updated compatibility wording and replaced many doc pointers with external documentation links.
    • Expanded Breaking Changes: Pipelines upgrade includes Chains → Cosign v2.6.0 and HS256 deprecation (recommend RS256).
    • Reworked Fixed/Known Issues templates to be version-aware and clarified toolchain entries.
  • Chores

    • Bumped versions: Pipelines v4.7, Connectors v1.7, Harbor v2.14; toolchain entries updated (GitLab v18.5, Nexus/SonarQube noted).

✏️ Tip: You can customize this high-level summary in your review settings.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Jan 22, 2026

Walkthrough

This PR updates release notes and site configuration to bump Alauda DevOps Pipelines to v4.7, Connectors to v1.7, and Harbor build to v2.14; it also converts many textual documentation links to ExternalSiteLink components and refreshes breaking/fixed/known-issue blocks in the release notes.

Changes

Cohort / File(s) Summary
Release Notes Documentation
docs/en/overview/release_notes.mdx
Updated compatibility header and version matrix (Pipelines → v4.7, Connectors → v1.7, Harbor → v2.14). Replaced plain-text documentation pointers with ExternalSiteLink components. Added Pipelines breaking change (Chains → Cosign v2.6.0; HS256 deprecation; recommend RS256). Expanded Connectors notes and updated Fixed/Known Issues templates with version-aware blocks.
Site version mapping
sites.yaml
Bumped version entries: alauda-devops-pipelines v4.6→v4.7, alauda-devops-connectors v1.6→v1.7, alauda-build-of-harbor v2.12→v2.14. No structural changes beyond version updates.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Suggested reviewers

  • yhuan123
  • l-qing
  • danielfbm

Poem

🐇
I bounced through changelogs, bright and quick,
Pipelines climbed to v4.7 — oh what a kick,
Connectors leapt to v1.7 in tune,
Harbor polished up to v2.14 soon,
I nibble doc links, then hug a carrot 🥕

🚥 Pre-merge checks | ✅ 2 | ❌ 1
❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Title check ⚠️ Warning The title mentions upgrading v4.2 release notes, but the actual changes document v4.7 pipelines and v1.7 connectors (upgraded from v4.6 and v1.6 respectively). Update the title to accurately reflect the actual versions being upgraded, such as 'docs: upgrade site.yaml and release notes for Pipelines v4.7 and Connectors v1.7'.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
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.


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

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

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In `@docs/en/overview/release_notes.mdx`:
- Around line 33-51: In the "Pipelines and Connectors Integration" bullet,
replace the redundant phrase "unified UI interface" with "unified UI" so the
line reads "...seamlessly integrating tools into Pipelines via a unified UI.";
update the sentence that references resource definitions for
**GitCodeRepository**, **OCIArtifact**, and **MavenArtifact** in the same bullet
to use the corrected wording.

Comment thread docs/en/overview/release_notes.mdx
Comment thread docs/en/overview/release_notes.mdx Outdated
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In `@docs/en/overview/release_notes.mdx`:
- Around line 40-41: The two release note bullet points are ungrammatical and
inconsistent; update the bullets in release_notes.mdx to use parallel, concise
phrasing: change "Support integration with SonarQube and SonarCloud by using
SonarQube Connector." to "Support integration with SonarQube and SonarCloud via
the SonarQube Connector." and change "Support to deploy the Connectors system in
a high availability (HA) configuration to ensure service continuity and fault
tolerance." to "Support deploying the Connectors system in a high-availability
(HA) configuration to ensure service continuity and fault tolerance." ensuring
both bullets are parallel and use correct hyphenation ("high-availability") and
phrasing.

Comment thread docs/en/overview/release_notes.mdx
@tik-seven tik-seven merged commit 8730963 into alauda:main Jan 23, 2026
3 checks passed
@tik-seven tik-seven deleted the docs/update-site-yaml branch February 14, 2026 03:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants