#Release Notes

#Compatibility and support matrix

The following table shows the compatibility and support matrix between the Alauda Container Platform Pipelines operator and ACP versions.

#Channel mapping

See also Lifecycle Policy and Install for Subscription examples.

#v4.6.4

#New and Optimized Features

Tekton Hub

• Fresh installations no longer deploy the in-cluster Tekton Hub by default; the Hub capability is provided through the ArtifactHub shim. When upgrading from an earlier v4.6.x release that had Tekton Hub deployed, the existing Tekton Hub component and its catalog artifacts are now preserved and remain usable, so existing Task and Pipeline references continue to resolve. Both the fresh-install and upgrade paths work in air-gapped environments. During an upgrade the operator records the catalog image already running in your environment and pins it, and it retains the existing catalog ConfigMaps so they are not garbage-collected.
• A new operator-level environment variable AUTOINSTALL_TEKTONHUB (set on the operator Deployment) controls Tekton Hub management with three values: preserve (default — keep an existing Hub, and do not deploy one on a fresh install), true (explicitly deploy and keep the Hub, for the all profile), and false (explicitly remove any existing Hub — destructive, opt-in only). Any unset or unrecognized value is treated as preserve.

#Breaking Changes

Fresh installations no longer deploy the in-cluster Tekton Hub by default (earlier v4.6.0 – v4.6.3 releases deployed it automatically); the Hub capability is now served through the ArtifactHub shim. Existing environments are not affected: an upgrade retains its existing Tekton Hub and catalog instead of removing them, so existing Task and Pipeline references continue to resolve.

#Fixed Issues

• Before this update, if a stale .git/index.lock file was left behind in the local git clone used for Tekton Hub catalog synchronization, the catalog sync kept failing every refresh cycle when running git reset --hard because the lock file already existed, so the Hub could not refresh its resource index; pipelines that referenced catalog resources (such as clone-image-build-test-scan) then repeatedly failed with "fail to fetch Tekton Hub resource ... not found on hub" and could not retrieve those resources. With this update, Tekton Hub automatically detects and removes stale .git lock files before reusing the catalog clone, so synchronization self-heals on the following cycles, the affected catalog resources can be fetched again, and pipelines no longer fail with this error.

#Known Issues

No issues in this release.

#v4.6.3

#New and Optimized Features

• Subscription channel layout aligned with the LTS channel policy. The bundle is now published to stable, latest, and pipelines-4.6, with stable as the new default. Existing Subscriptions on latest are not impacted; explicitly keep channel: latest if you want to pin to the previous default.

#Breaking Changes

No breaking changes in this release.

#Fixed Issues

No issues in this release.

#Known Issues

No issues in this release.

#v4.6.2

#New and Optimized Features

With this update, some vulnerabilities and security issues have been fixed, ensuring the stability and security of the system.

#Breaking Changes

No breaking changes in this release.

#Fixed Issues

No issues in this release.

#Known Issues

No issues in this release.

#v4.6.1

#New and Optimized Features

With this update, some vulnerabilities and security issues have been fixed, ensuring the stability and security of the system.

#Breaking Changes

No breaking changes in this release.

#Fixed Issues

• Before this update, in MicroOS environments with strict SELinux enforcement, Tekton tasks that depend on Java-based tools (such as Maven and SonarQube) failed to start with the error “Error occurred during initialization of VM - Failed to mark memory page as executable”. With this update, the issue is resolved, and Java-based Tekton tasks now run normally in MicroOS environments.

#Known Issues

No issues in this release.

#v4.6.0

#New and Optimized Features

Pipeline

• With this update, Pipeline execution now supports manual approval functionality, allowing users to set approval checkpoints during pipeline execution.
• With this update, Pipelines support custom execution output, enabling users to customize Task execution output to PipelineRun/TaskRun details. Additionally, built-in execution information output is now available for SonarQube/Pytest/Buildah Tasks in the execution details.
• With this update, dynamic form configuration is now supported, allowing users to declaratively configure interactive forms for Pipeline and Task resources, providing a user-friendly parameter configuration experience without writing frontend code.
• With this update, Task image addresses support dynamic selection, enabling users to flexibly select or configure tool images used by tasks as needed.
• With this update, Cosign, Syft, and Trivy tasks now support processing multiple images simultaneously.
• With this update, the Maven Task supports appending custom CA certificates to the JDK default truststore (rather than overwriting), and provides flexible configuration parameters such as certificate path and keystore password, ensuring compatibility between private repository and public resource access.

Trigger

• With this update, ScheduledTriggers are now supported, allowing users to configure pipelines to execute automatically at regular intervals based on Cron expressions.
• With this update, image trigger functionality is now supported, such as automatically triggering pipeline execution when container images are pushed to the registry.
• With this update, EventListener supports automatic generation of WebHook listener domains, simplifying the Webhook configuration process.

Pipelines as Code

• With this update, Pipelines-as-Code now supports integration with GitLab, allowing users to implement pipeline-as-code using GitLab repositories.

Pipeline Integration with Connector

• With this update, Pipeline and Task support integration with Connector for resource browsing and selection. You can now integrate connectors to browse and select resources from external systems during pipeline configuration, eliminating manual URL entry and reducing configuration errors.
  • Supports browsing and selecting Git Revision of Git repositories through git connectors.
  • Supports browsing and selecting Git Repository and Git Revision through gitlab connectors.
  • Supports browsing and selecting OCI Artifact Tags through OCI connectors.
  • Supports browsing and selecting OCI Repository and Artifact Tags through Harbor connectors.
  • More about it, see Pipeline Integration with Connector
  • This feature depends on Plugin of Alauda Container Platform Tenant Management
    • >= v4.1.15 is required for v4.1.x (ACP >= v4.1.3)

#Breaking Changes

No breaking changes in this release.

#Fixed Issues

No issues in this release.

#Known Issues

• When the current version of tektoncd-operator is deployed to ACP 4.0.6 and earlier, or to ACP 4.1.3 and earlier, users with Developers role (namespace developer role) are expected to have permission to create EventListener and Interceptor resources under the triggers.tekton.dev group, but in practice they will not have permission to create them. This issue can be bypassed by temporarily granting permissions to these two resource types separately, or resolved by updating the ACP platform version.