📚 Sync docs from alaudadevops/tektoncd-operator on aaa0b4b3ec2c815f5559bb1747a6c05e451cf358

Source: docs: adjust release notes and lifecycle policy for v4.1.0 (#209)
Author: l-qing
Ref: refs/heads/release-4.1
Commit: aaa0b4b3ec2c815f5559bb1747a6c05e451cf358

This commit automatically syncs documentation changes from the source-docs repository.

🔗 View source commit: AlaudaDevops/tektoncd-operator@aaa0b4b
🤖 Synced on 2025-07-10 09:54:36 UTC

Author: l-qing

.github/SYNC_INFO.md

@@ -1,10 +1,10 @@
 # Documentation Sync Information
 
-- **Last synced**: 2025-07-07 03:52:51 UTC
+- **Last synced**: 2025-07-10 09:54:35 UTC
 - **Source repository**: alaudadevops/tektoncd-operator
-- **Source commit**: [d9a71adfda077eb458d051aac93f41addfce332e](https://github.com/alaudadevops/tektoncd-operator/commit/d9a71adfda077eb458d051aac93f41addfce332e)
-- **Triggered by**: yuzichen12123
-- **Workflow run**: [#9](https://github.com/alaudadevops/tektoncd-operator/actions/runs/16107170334)
+- **Source commit**: [aaa0b4b3ec2c815f5559bb1747a6c05e451cf358](https://github.com/alaudadevops/tektoncd-operator/commit/aaa0b4b3ec2c815f5559bb1747a6c05e451cf358)
+- **Triggered by**: l-qing
+- **Workflow run**: [#10](https://github.com/alaudadevops/tektoncd-operator/actions/runs/16191945982)
 
 ## Files synced:
 - docs/

docs/en/overview/lifecycle_policy.mdx

@@ -1,5 +1,5 @@
 ---
-weight: 30
+weight: 35
 ---
 
 # Lifecycle Policy
@@ -8,17 +8,24 @@ weight: 30
 
 Below is the lifecycle schedule for released versions of the `Alauda DevOps Pipelines` operator:
 
-| Alauda DevOps Pipelines Version | Tekton Component Versions | Release Date | End of Support  |
-| :----: | ------------------------ | :----------: | :--------------: |
-| v4.1.z | Pipelines: v0.65.z<br />Chains: v0.23.z<br />Pipelines-as-Code: v0.32.z<br />Results: v0.13.z<br />Triggers: v0.30.z<br />Tekton Hub: v1.19.z | 2025-?-? | 2026-?-? |
+| Alauda DevOps Pipelines Version | Release Date | End of Support  |
+| :----: | :----------: | :--------------: |
+| v4.1.x | 2025-07-14 | 2025-11-14 |
+| v4.0.x (LTS) | 2025-04-08 | 2026-04-08 |
+
+> For detailed component versions, see the [Compatibility and support matrix](./release_notes.mdx#compatibility-and-support-matrix)
 
 ## Release Policy
 
-The `Alauda DevOps Pipelines` operator releases a new version every four to six months, updating the operator to the latest or second latest [LTS](https://github.com/tektoncd/community/blob/main/releases.md#support-policy) version officially released by Tekton.
+A new minor version of the `Alauda DevOps Pipelines` operator is released every month.
+
+Within every 4-month period, the last minor version will be selected as a Long Term Support (LTS) version. LTS versions are supported for 12 months, while non-LTS versions are supported four months.
+
+During these four months, we will update to the latest or second [LTS](https://github.com/tektoncd/community/blob/main/releases.md#support-policy) version officially released by Tekton.
 
 ## Maintenance Policy
 
-Alauda provides 12 months of maintenance support for each released version of the Tekton operator.
+Alauda provides maintenance support for 12 months for LTS versions and 4 months for non-LTS versions of the Tekton operator.
 
 During the maintenance period, Alauda will provide the following services to customers:
 

docs/en/overview/release_notes.mdx

@@ -10,28 +10,40 @@ title: Release Notes
 # Release Notes
 
 ::: tip
-The maintenance period for version **v4.1.z** is from ? ?, 2025 to ? ?, 2026.
+The maintenance period for version **v4.1.x** is from July 14, 2025 to Nov 14, 2026.
 :::
 
 ## Compatibility and support matrix
 
 The following table shows the compatibility and support matrix between the `Alauda DevOps Pipelines` operator and ACP versions.
 
-| Alauda DevOps Pipelines Version | Tekton Component Versions |  ACP Version |
-| :------: | ------------------------- | :----------: |
-| v4.1.z  | Pipelines: v0.65.5<br />Chains: v0.23.0<br />Pipelines-as-Code: v0.32.0<br />Results: v0.13.2<br />Triggers: v0.30.1<br />Tekton Hub: v1.19.2 | v4.0, v4.1 |
+| Alauda DevOps Pipelines Version | Component Version | | | | | | ACP Version |
+|:------:|:------:|:------:|:------:|:------:|:------:|:------:|:------:|
+| **Operator** | **Pipelines** | **Triggers** | **CLI** | **Chains** | **Hub** | **Results** | |
+| 4.1.0 | 0.65.7 | 0.30.1 | 0.39.1 | 0.23.1 | 1.19.2 | 0.14.0 | 4.0 |
+| 4.0.x (LTS) | 0.65.x | 0.30.x | 0.39.x | 0.23.x | 1.19.x | 0.13.x | 4.0 |
 
 ## v4.1.0
 
 ### New and Optimized Features
 
-TODO: Add new features and optimizations for v4.1.0
+This release enhances task capabilities, strengthens Pipeline security, introduces standardized Java templates, improves execution efficiency via Trigger configurations, and optimizes end-to-end orchestration experience.
+
+- Expanded Task Capabilities
+  - Support for kubectl Task: Directly operate Kubernetes resources.
+  - Support for git Task: Simplify code repository interaction processes.
+- Enhanced Pipeline Security
+  - Integration of syft Task: Automatically generate image SBOM.
+  - Integration of cosign Task: Implement image signing and verification.
+  - Integration of trivy Task: Conduct vulnerability scanning and dependency security detection.
+- Provide standardized Java Pipeline templates, covering the entire workflow of compilation, scanning, building, and deployment.
+- Pipelines support Trigger Template configuration to improve pipeline execution efficiency.
+- Optimize the end-to-end user experience of orchestrating Pipelines.
 
 ### Fixed Issues
 
-{/* release-notes-for-bugs?template=fixed&project=DEVOPS&version=v4.1 (next) */}
+{/* release-notes-for-bugs?template=fixed&project=DEVOPS&version=v4.1.0 */}
 
 ### Known Issues
 
-{/* release-notes-for-bugs?template=unfixed&project=DEVOPS&version=v4.1 (next) */}
-
+{/* release-notes-for-bugs?template=unfixed&project=DEVOPS&version=v4.1.0 */}

docs/en/upgrade.mdx

@@ -0,0 +1,7 @@
+---
+weight: 245
+---
+
+# Upgrade
+
+<Overview />

docs/en/upgrade/index.mdx

@@ -0,0 +1,141 @@
+---
+weight: 10
+---
+
+# Upgrade `Alauda DevOps Pipelines` Operator
+
+This document provides instructions for upgrading the `Alauda DevOps Pipelines` Operator to a newer version using the `Marketplace`/`OperatorHub` interface in your cluster. The upgrade process is designed to be straightforward while ensuring minimal disruption to existing Tekton resources.
+
+## Upgrade Overview
+
+Upgrading the `Alauda DevOps Pipelines` Operator allows you to access new features, bug fixes, and improvements to the Tekton ecosystem. The `Alauda DevOps Pipelines` Operator handles the upgrade of all Tekton components (Pipelines, Triggers, Hub, etc.) according to your configuration.
+
+## Before You Begin
+
+Before upgrading the `Alauda DevOps Pipelines` Operator, ensure you:
+
+- Have administrative access to your cluster
+- Review the release notes for the new version to understand any breaking changes
+- Verify that your existing Tekton component configurations are compatible with the new version
+- Confirm that all Tekton components are in a ready state
+
+## Upgrade Process
+
+### Using `Marketplace`/`OperatorHub`
+
+1. **Access the `Marketplace`/`OperatorHub`**
+   - Log in to your cluster's management console
+   - Navigate to the `Marketplace` or `OperatorHub` section
+
+2. **Locate the `Alauda DevOps Pipelines` Operator**
+   - Search for `Alauda DevOps Pipelines` in the search bar
+   - Click on the `Alauda DevOps Pipelines` card
+
+3. **View Available Versions**
+   - On the `Alauda DevOps Pipelines` Operator details page, you'll see information about the currently installed version
+   - The interface will indicate if a newer version is available
+   - You can click different `Channels` to view all available versions
+
+4. **Initiate the Upgrade**
+   - If the target version is in a different `Channel`, switch to the corresponding `Channel` in the `Subscription` first
+   - If the current `Channel` has a newer version available, you will see a prompt:
+     - **New Version Detected**
+       - To upgrade only the current Operator, click `Confirm` to upgrade.
+
+5. **Configure Upgrade Settings (if applicable)**
+   - Some upgrades may present configuration options
+   - In most cases, the default settings will preserve your existing configuration
+
+6. **Confirm and Start the Upgrade**
+   - Click `Confirm` to begin the process
+   - Review the upgrade details and confirm your selection
+   - The system will update the `Alauda DevOps Pipelines` Operator while maintaining your custom resources
+
+7. **Monitor the Upgrade**
+   - The upgrade progress will be displayed in the `OperatorHub` interface
+   - You can also check the status in the `tekton-operator` namespace:
+     ```bash
+     $ kubectl get pods -n tekton-operator
+     ```
+     When all pods are in `Running` state, the operator upgrade is complete.
+     The operator will then automatically upgrade components such as `Pipelines`, `Triggers`, `Hub`, `Chains`, etc.
+   - Check the components upgrade status:
+     ```bash
+     $ kubectl get tektoninstallerset -A
+     $ kubectl get pods -n tekton-pipelines
+     ```
+     When all components and pods are in `Ready` state, the components upgrade is complete.
+
+8. **Verify the Upgrade**
+   - Check that the `Alauda DevOps Pipelines` Operator version has been updated:
+     ```bash
+     $ kubectl get csv -n tekton-operator
+
+     NAME                        DISPLAY                   VERSION   REPLACES   PHASE
+     tektoncd-operator.v4.x.x    Alauda DevOps Pipelines   4.x.x     x          Succeeded
+     ```
+     When the `VERSION` matches the new version, the upgrade is complete.
+   - Verify that your Tekton components are functioning correctly
+     - Test that your pipelines can run successfully
+
+## Post-Upgrade Steps
+
+After the upgrade completes successfully:
+
+1. **Verify Component Status**
+   - Check that all Tekton components have been updated:
+     ```bash
+     kubectl get tektonconfig,tektonpipeline,tektontrigger -A
+     kubectl get tektoninstallerset -A
+     ```
+
+2. **Test Functionality**
+   - Run a simple pipeline to verify that the system is working correctly
+   - Ensure that all existing integrations continue to function
+
+3. **Update Custom Resources if Needed**
+   - If the new version introduces changes to CRDs, you may need to update your custom resources
+   - Refer to the release notes for specific migration steps
+
+## Rollback Procedure
+
+If you encounter issues with the new version, you can roll back to the previous version:
+
+1. Return to the `Marketplace`/`OperatorHub` interface
+2. Select the `Alauda DevOps Pipelines` Operator
+3. `Uninstall` the current version
+4. Choose the previous version from the version list
+5. Follow the installation process for that version
+
+:::note
+Downgrading may require additional steps to ensure compatibility of your resources with the older version.
+
+This depends on the differences between the version you upgraded from and the version you upgraded to. If the differences are large, you may need to manually migrate resources.
+:::
+
+## Troubleshooting
+
+If you encounter issues during or after the upgrade:
+
+- Check the `Alauda DevOps Pipelines` Operator pod logs:
+  ```bash
+  $ kubectl logs -l name=tekton-operator -n tekton-operator
+  ```
+
+- Verify the status of your Tekton resources:
+  ```bash
+  $ kubectl get tektonconfig config -o yaml
+  ```
+
+- Ensure that all components have the expected status:
+  ```bash
+  $ kubectl get tektoninstallerset
+  ```
+
+## Next Steps
+
+After successfully upgrading the `Alauda DevOps Pipelines` Operator:
+
+- Explore new features introduced in the latest version
+- Update your CI/CD pipelines to leverage new capabilities
+- Consider enabling additional components that may be available in the new version

docs/en/upgrade/upgrade.mdx

@@ -1,6 +1,6 @@
 {
   "devDependencies": {
-    "@alauda/doom": "^1.7.1",
+    "@alauda/doom": "^1.9.1",
     "typescript": "^5.8.3"
   },
   "scripts": {