#Release Notes

#Compatibility and support matrix

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

The following table shows the recommended version mapping between Alauda DevOps Pipelines and Alauda DevOps Connectors.

#Channel mapping

For details about channel behavior and upgrade targeting, see Upgrade Path and Lifecycle Policy.

#v4.15.0

#New and Optimized Features

Operator

• With this update, the operator and the component images it ships are rebuilt with refreshed dependencies and base images that carry the latest security fixes. The Tekton component baseline is unchanged from v4.14.0; see the Compatibility and support matrix for the full mapping.

Web Console

• With this update, the run configuration templates that the console previously listed as plain TriggerTemplate resources are presented as Run Template, with their own entry in the Pipeline navigation. A TriggerTemplate carrying the triggertemplate.triggers.tekton.dev/usage: runtime-config label is shown as a Run Template; every other TriggerTemplate stays a native resource on the Triggers page. For details about the label conventions, see Runtime Configuration Templates.
• With this update, a Run Template has a detail page that shows the Pipeline it runs — the Pipeline name links to the Pipeline itself and the topology is rendered inline — together with params, workspaces, results, YAML, and the PipelineRuns started from that template.
• With this update, a Run Template declares its runtime inputs per parameter instead of per Integration. Params, workspaces, and Integration parameters that are not marked Set as Runtime are hidden and filtered out when the template is executed, so a template can expose only the inputs its consumers are meant to fill in.
• With this update, saving the configuration of a run can update an existing Run Template instead of only creating a new one. The save dialog offers the two modes explicitly and preselects the template that the run dialog has already applied; an existing Run Template can also be duplicated into a new one.
• With this update, the PipelineRuns produced by a Run Template are matched back to their source through the triggertemplate.triggers.tekton.dev/name label, so the execution records listed on a template contain only its own runs, and re-running a PipelineRun preserves that source label.
• With this update, a Task can be executed directly from the Task context instead of going through the TaskRun list first. The execution form is prefilled from the selected Task and covers the params and workspaces the TaskRun needs; creating a TaskRun from the TaskRun list is unaffected.
• With this update, a TaskRun can be re-run from the TaskRun list or its detail page. The new TaskRun reuses the original spec and Integration configuration, can be adjusted before submission, and records its origin in the tekton.dev/re-run-of annotation, which the detail page renders as a link back to the source run.
• With this update, the Task detail page aggregates the TaskRun execution records of that Task — status, name, creation time, and completion time — with direct entry points into the TaskRun detail and its logs.
• With this update, the fan-out produced by a matrix PipelineTask is visible in the PipelineRun and TaskRun views. Configuring a matrix from the console is not part of this release, and runs without a matrix are displayed exactly as before.
• With this update, several console details are refined, including refitting the task log terminal after a tab resize, tolerating dotted resource names in catalog detail deep links, and aligning the navigation of pipelines that belong to a plugin.

#Breaking Changes

• Starting from this release, the console lists run configuration templates and native trigger templates separately. A TriggerTemplate labeled triggertemplate.triggers.tekton.dev/usage: runtime-config is presented as a Run Template under the Pipeline navigation, where it can be run directly and lists the PipelineRuns it produced. Every other TriggerTemplate is listed on the Triggers page under a TriggerTemplates tab, which keeps the native create, update, delete, and YAML operations but intentionally offers no direct execution, no execution records, and no detail page.

  • No Kubernetes resource is created, renamed, migrated, or relabeled by this change: both entries operate on the same TriggerTemplate API, with unchanged API semantics.
  • Saved links to the previous list may no longer resolve to the expected view. Use the Run Template entry in the Pipeline navigation for run configuration templates, and the TriggerTemplates tab on the Triggers page for native trigger templates.

#Upgrade Notes

Web Console

• Nothing is relabeled automatically by the upgrade, so a template created before this release keeps whatever entry its current label implies.
• Execution records on a Run Template are matched by the triggertemplate.triggers.tekton.dev/name source label. PipelineRuns created before this release do not carry it and are therefore not listed retroactively; no backfill is performed.
• Existing Run Templates have no per-parameter runtime descriptors yet. Until such a template is edited and saved again, every declaration it exposes is treated as visible at execution time; Set as Runtime filtering takes effect from the next save onwards.

#Fixed Issues

• Before this update, when viewing PipelineRun or TaskRun logs in environments without hardware acceleration or WebGL, a white rectangle could cover part of the log area and make log content unreadable; in addition, the Advanced/Basic switch could be misplaced or obscured with some form widths. With this update, task logs remain complete and stable when WebGL or hardware acceleration is unavailable, without the white rectangle obstruction; the Advanced/Basic switch stays correctly positioned across form widths, remains fully visible, and can be switched normally.
• Before this update, when configuring a Pipeline Result on the Pipeline editing page, valid finally task result references were rejected by frontend validation, and the result guidance and variable autocomplete were incomplete; in addition, copying a result from a finally task drawer generated the wrong reference prefix and provided unclear copy guidance. With this update, Pipeline Results accept valid task and finally task result references, including array and object result selectors, with consistent validation guidance and variable autocomplete; the finally task result copy action generates the correct reference and clearly shows the value to be copied.

#Known Issues

No issues in this release.