RATATOSK
← All releases

Tektonv1.6.0

Breaking changes 2Important fixes 4Enhancements 2Dependency updates 7Other changes 32

Get Tekton alerts

Email is sent weekly only when there are changes to check; critical security advisories are sent immediately.

Breaking changes2

Timed-out TaskRun pods retained with keep-pod-on-cancel

AffectsTaskRuns with keep-pod-on-cancel set to true

Previously, pods for timed-out TaskRuns were deleted; pods were retained only when a TaskRun was canceled.

Show release-note lines
* :bug: Pods for timed out TaskRuns should not be deleted when keep-pod-on-cancel feature flag is true (#9075)
If Feature flag "keep-pod-on-cancel" is set to true then pods corresponding  to TaskRun will be not be deleted  when TaskRun Times Out. Earlier pod was retained only if it taskrun was canceled.
github.com/tektoncd/pipeline/releases/tag/v1.6.0

TaskRun.Status.Steps now follows pod container order

AffectsTaskRuns that use StepActions

Previously, status processing could show StepAction steps first and append inline steps last, regardless of their order in the pod.

Evidence“`TaskRun.Status.Steps` now strictly follows the pod’s step container order.” tektoncd/pipeline/pull/9039 ↗
Show release-note lines
* :bug: fix(taskrun): ensure status steps are ordered correctly when using StepAction (#9039)
github.com/tektoncd/pipeline/releases/tag/v1.6.0

Important fixes4

  • Unknown DryRunValidation errors no longer fail reference resolution
    AffectsTaskRef and PipelineRef resolution

    Previously, unknown errors marked retryable during reference resolution could still cause a PipelineRun to fail. Explicit Validation errors still cause the Run to fail.

    * :bug: fix: do not fail PipelineRun when TaskRef reconciles with retryable err (#9099)
    With this change, unknown DryRunValidation errors during TaskRef and PipelineRef resolution no longer cause PipelineRuns and TaskRuns to fail. Explicit Validation errors will still cause the Run to fail.
    github.com/tektoncd/pipeline/releases/tag/v1.6.0
  • SidecarLog results container stays running in Kubernetes-native sidecar mode
    Affectssetups with Kubernetes-native sidecar support enabled via EnableKubernetesSidecar

    In Kubernetes-native sidecar mode, the results container exited after processing results, causing repeated init-container restarts. It now waits after processing results and exits when it receives SIGTERM or SIGINT.

    * :bug: Added signal handling in SidecarLog results to support Kubernetes-native sidecar functionality (#9095)
    Added signal handling to SidecarLog to support Kubernetes-native sidecar functionality, preventing repeated restarts of the init container.
    github.com/tektoncd/pipeline/releases/tag/v1.6.0
  • Late inline-step reshuffling in TaskRun status fixed
    AffectsTasks containing StepActions

    When a Task uses StepActions, inline steps could appear only later during pod-based status processing and reshuffle the status list. They are now included early in TaskRun.Status.Steps with nil provenance, preventing that late appearance.

    * :bug: fix(taskrun): ensure status steps are ordered correctly when using StepAction (#9039)
    github.com/tektoncd/pipeline/releases/tag/v1.6.0
  • Entrypoint ARM64 platform-command lookup fixed
    AffectsARM64 clusters with TaskRuns that omit script and command

    On an ARM64 cluster, a TaskRun without script or an explicit command could not run because the entrypoint could not find its platform command. The entrypoint now handles Linux when detecting the platform CPU variant.

    * :bug: entrypoint: handle linux in pkgs/platforms (#9096)
    github.com/tektoncd/pipeline/releases/tag/v1.6.0

Enhancements2

  • User-facing displayName for Step
    * :sparkles: Issue 9032 - Add support for step display name (#9033)
    add displayName field to Step.
    github.com/tektoncd/pipeline/releases/tag/v1.6.0
  • Embedded Pipelines in tasks create child PipelineRuns
    * :sparkles: Implement Pipelines-in-Pipelines. (#8873 #8878 #8879)
    A Pipeline can now execute embedded Pipelines (Pipelines-in-Pipelines) using the `PipelineSpec` field under `tasks`. Refer to the TEP-0056 for more details.
    github.com/tektoncd/pipeline/releases/tag/v1.6.0

Dependency updates7

    7 more, none mentioning security
    • * :hammer: build(deps): bump k8s.io/code-generator from 0.32.8 to 0.32.9 (#9106)
    • * :hammer: build(deps): bump the all group in /tekton with 4 updates (#9105)
    • * :hammer: build(deps): bump google.golang.org/protobuf from 1.36.8 to 1.36.10 (#9097)
    • * :hammer: build(deps): bump golang.org/x/crypto from 0.41.0 to 0.43.0 (#9085)
    • * :hammer: build(deps): bump the all group in /tekton with 2 updates (#9081)
    • * :hammer: build(deps): bump the all group in /tekton with 3 updates (#8990)
    • * :hammer: build(deps): bump github.com/spiffe/go-spiffe/v2 from 2.5.0 to 2.6.0 (#8988)
    Other changes32

    Summaries are produced by AI, so they can be wrong, and they are provided without warranty.