RATATOSK
← All releases

Tektonv1.12.0

Security 6Breaking changes 5Deprecations 1Dependency updates 9Other changes 14

Get Tekton alerts

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

Security6high1

Git resolver argument injection fixed

high
Affectssetups using the deprecated or current git resolver

In versions 1.10.0 through 1.11.0, the git resolver passed revision directly to git fetch without checking for a leading -, allowing argument injection.

Show release-note lines
* :lock: fix: prevent git argument injection via revision parameter (GHSA-94jr-7pqp-xhcq) (0967cc8e6e9b)
github.com/tektoncd/pipeline/releases/tag/v1.12.0

VolumeMount restriction check now uses normalized paths

Affectssetups with VolumeMount paths checked against /tekton/
Show release-note lines
* :lock: fix: normalize VolumeMount paths before /tekton/ restriction check (c8cc73a2ceca)
github.com/tektoncd/pipeline/releases/tag/v1.12.0

System API tokens rejected with a user-controlled serverURL

Affectssetups using a system API token with a user-controlled serverURL
Show release-note lines
* :lock: Security: reject system API token with user-controlled serverURL (e964bce1a130)
github.com/tektoncd/pipeline/releases/tag/v1.12.0

Resolver prefix stripping and non-capturing pattern anchoring

Affectsresolver setups using prefixes and pattern anchoring(Inferred)
Show release-note lines
* :lock: fix: strip resolver prefixes and use non-capturing group for pattern anchoring (b8905600322a)
github.com/tektoncd/pipeline/releases/tag/v1.12.0

Source URI whitespace trimming before pattern matching

Affectssetups using source-URI pattern matching(Inferred)
Show release-note lines
* :lock: fix: trim whitespace from source URI before pattern matching (37f9657b4bd1)
github.com/tektoncd/pipeline/releases/tag/v1.12.0

Breaking changes5

CustomRun CloudEvents sent by default

AffectsCustomRuns with a CloudEvents sink configured in config-events
Removed innot stated

Previously, CustomRun CloudEvents were not sent unless send-cloudevents-for-runs was set to true. They are now sent when a sink is configured in config-events, unless send-cloudevents-for-runs is set to false.

Evidence“The feature flag send-cloudevents-for-runs is deprecated and will be removed in a future release. Its default has changed from false to true: CloudEvents for CustomRuns are now sent by default whenever a sink is configured in config-events.” tektoncd/pipeline/pull/9774 ↗
Show release-note lines
* :sparkles: [TEP-0137] Deprecate send-cloudevents-for-runs feature flag (#9774)
The feature flag default changed from `false` to `true`. CloudEvents for CustomRuns are now sent by default.
* :rotating_light: [TEP-0137] The `send-cloudevents-for-runs` feature flag is deprecated and will be removed in a future release. Its default has changed from `false` to `true` (#9774).
github.com/tektoncd/pipeline/releases/tag/v1.12.0

Specific failure reasons for pod-level TaskRun failures

AffectsTaskRun Succeeded conditions

Previously, all pod-level TaskRun failures used the generic Failed reason. Now, the reason identifies pod eviction (PodEvicted), init-container OOM or failure (InitContainerOOM, InitContainerFailed), step OOM or failure (StepOOM, StepFailed), or sidecar OOM or failure (SidecarOOM, SidecarFailed). Unknown failures still use Failed; when multiple failures occur, the reason follows this priority: pod eviction, init-container failures, sidecar OOM, step OOM, sidecar failure, then step failure.

Evidence“When multiple containers fail, the reason is chosen by priority: 1. Pod eviction (pod-level, authoritative) 2. Init container failures (run first, block everything) 3. Sidecar OOM → Step OOM (OOM is likely root cause) 4. Sidecar failed → Step failed (non-OOM failures)” tektoncd/pipeline/pull/9368 ↗
Show release-note lines
* :sparkles: fix: surface specific TaskRun failure reasons when pod fails (#9368)
TaskRun failure reasons now distinguish between different pod-level failure types: PodEvicted, InitContainerOOM, InitContainerFailed, StepOOM, StepFailed, SidecarOOM, and SidecarFailed, replacing the generic "Failed" reason.
github.com/tektoncd/pipeline/releases/tag/v1.12.0

Duplicate CloudEvents suppressed for run objects

AffectsCloudEvents sinks configured for run objects
Action requiredController concurrency set to 1 so reconcile cycles for the same resource do not run concurrently.

Before this release, PipelineRun and TaskRun events bypassed the event cache. Repeated condition snapshots are now skipped, and a previously sent event type stays suppressed even after condition changes; .unknown. events can still be sent on condition changes, including message-only changes.

Evidence“// A cache miss requires a new object or change in the condition (including message-only changes)” tektoncd/pipeline/pull/6914 ↗
Show release-note lines
* :bug: Rework the events controller cache (#6914)
github.com/tektoncd/pipeline/releases/tag/v1.12.0

CloudEvents delivery moved to a dedicated controller

Affectssetups using CloudEvents for PipelineRuns or TaskRuns
Action requiredthe tekton-events-controller Deployment must be running

Previously, the PipelineRun and TaskRun controllers sent these CloudEvents; now the dedicated controller sends them, and two queued event types are available. kubectl describe pipelinerun/taskrun shows delivery status through CloudEventSent and CloudEventFailed Kubernetes Events.

Show release-note lines
### :rotating_light: TEP-0137: CloudEvents now sent by dedicated events controller (ACTION REQUIRED)
CloudEvents for **PipelineRuns** and **TaskRuns** are now sent by the dedicated `tekton-events-controller` and **no longer by the PipelineRun/TaskRun controllers**. Operators must ensure the `tekton-events-controller` Deployment is running.
New events added:
- `dev.tekton.event.pipelinerun.queued.v1` — sent when a PipelineRun is created but not yet processed
- `dev.tekton.event.taskrun.queued.v1` — sent when a TaskRun is created but not yet processed
CloudEvent delivery visibility is available via `kubectl describe pipelinerun/taskrun` (CloudEventSent/CloudEventFailed k8s Events).
github.com/tektoncd/pipeline/releases/tag/v1.12.0

PipelineRun missing-result messages identify the task and result

AffectsPipelineRuns with downstream tasks that consume task results

When a completed successful task omits a result referenced by a downstream task, the old message reported only a count; it now names the task, missing result, and downstream task, with details capped at 1024 characters. If the referenced task failed rather than succeeded, its original error message remains unchanged.

Evidence“If a referenced result is missing from a completed (successful) task, the error message now states which task completed without emitting which result and which downstream task references it. The details are included in the PipelineRun status condition message (capped at 1024 characters). When the referenced task failed (rather than succeeded), the original error message is preserved unchanged.” tektoncd/pipeline/pull/9529 ↗
Show release-note lines
* :sparkles: fix: surface clear errors when completed tasks miss referenced results (#9529)
github.com/tektoncd/pipeline/releases/tag/v1.12.0

Deprecations1

send-cloudevents-for-runs flag deprecated

AffectsCustomRuns with a sink configured in config-events
Removed innot stated

Previously, CloudEvents for CustomRuns were not sent by default because the flag defaulted to false. With no setting change, they are now sent whenever a sink is configured in config-events.

Show release-note lines
### :rotating_light: TEP-0137: `send-cloudevents-for-runs` feature flag deprecated
The `send-cloudevents-for-runs` feature flag is deprecated and will be removed in a future release. Its default has changed from `false` to `true`: CloudEvents for CustomRuns are now sent by default whenever a sink is configured in `config-events`.
Users relying on the flag set to `false` to skip events for CustomRuns should be aware of this change.
github.com/tektoncd/pipeline/releases/tag/v1.12.0

Dependency updates9

    9 more, none mentioning security
    • * :hammer: Remove aws-sdk-go-v2 ECR replace directives (#9773)
    • * :hammer: build(deps): bump k8s.io dependencies from 0.35.2 to 0.35.4 (#9848)
    • * :hammer: build(deps): bump github.com/google/cel-go from 0.27.0 to 0.28.0 (#9824)
    • * :hammer: build(deps): bump google.golang.org/grpc from 1.79.3 to 1.80.0 (#9715)
    • * :hammer: build(deps): bump go.uber.org/zap from 1.27.1 to 1.28.0 (#9926)
    • * :hammer: build(deps): bump go.opentelemetry.io/otel/sdk from 1.42.0 to 1.43.0 (#9757)
    • * :hammer: build(deps): bump github.com/go-jose/go-jose/v3 from 3.0.4 to 3.0.5 (#9722)
    • * :hammer: build(deps): bump github.com/go-jose/go-jose/v4 from 4.1.3 to 4.1.4 (#9721)
    • * :hammer: build(deps): bump github.com/sigstore/sigstore from 1.10.4 to 1.10.5 (#9711)
    Other changes14

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