#Release Notes

#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	Component Version						ACP Version
Operator	Pipelines	Triggers	CLI	Chains	Hub	Results
4.3.x	1.0.x	0.32.x	0.41.x	0.25.x	1.22.x	0.15.x	4.0, 4.1
4.2.x (LTS)	1.0.x	0.32.x	0.41.x	0.25.x	1.22.x	0.15.x	4.0, 4.1
4.1.x	0.65.x	0.30.x	0.39.x	0.23.x	1.19.x	0.14.x	4.0, 4.1
4.0.x (LTS)	0.65.x	0.30.x	0.39.x	0.23.x	1.19.x	0.13.x	4.0, 4.1

#v4.3.0

#New and Optimized Features

Pipeline

• With this update, Helm application management capabilities are integrated, including:
  • Package or Push a Helm Chart to an OCI Registry.
  • Deploy or Upgrade from an OCI-hosted Helm Chart.
  • Deploy or Upgrade from Helm Charts in Git Repo.
• With this update, when creating a PipelineRun on the UI, preview of Pipeline resources is supported.

Trigger

• With this update, TriggerTemplate supports selecting Pipeline from Hub as the triggering resource.
• With this update, TriggerTemplate that specifies PipelineRun as the resource supports direct execution.

Hub

• With this update, it is supported to customize the Catalog in the Hub and allow registration of custom Pipeline or Task in the Hub.

#Breaking Changes

No breaking changes in this release.

#Fixed Issues

• Before this update, when users configured the tekton-hub-api-ssh-crds Secret for Tekton Hub to clone private repositories using SSH keys, the configuration was not properly applied and code repositories could not be cloned successfully even after restarting the pods. With this update, the tekton-hub-api-ssh-crds Secret configuration is correctly processed and applied, allowing Tekton Hub to successfully clone code from private repositories using SSH authentication.
• Before this update, when executing Tekton Pipeline workflows, users occasionally encountered random test case failures due to Out Of Memory (OOM) errors in init containers, which terminated with exit code 137 and caused pipeline execution failures. With this update, init container memory allocation has been optimized to prevent OOM errors, ensuring stable and reliable pipeline execution during frequent e2e testing scenarios.

#Known Issues

• If Pipelines with resolver Tasks encounter webhook validation timeouts during Task retrieval, the pipeline may fail intermittently without automatic retry. To resolve this issue, manually restart the failed pipeline run as the system does not currently implement retry logic for retryable webhook validation errors.