RATATOSK
← All releases

Tektonv1.9.0

Security 1Breaking changes 5Important fixes 7Enhancements 2Dependency updates 30Other changes 39

Get Tekton alerts

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

Check before upgrading

Defects found after release1
Sidecar-logs result extraction no longer drops all TaskRun resultsFixed in v1.15.0

Security1

Pipeline parameter defaults resolve references with a 10-level limit

AffectsPipelineRuns with parameter references in defaults

Previously, defaults containing $(params.X) references were copied verbatim, leading to late task pod-creation failures with misleading messages. These references are now resolved, while dependency chains over 10 levels fail with a maximum-recursion-depth error.

Show release-note lines
* :bug: Fix parameter resolution for defaults with  references (#9271)
github.com/tektoncd/pipeline/releases/tag/v1.9.0

Breaking changes5

Duplicate protobuf tag for PriorityClassName fixed

Affectspod.Template protobuf serialization of PriorityClassName(Inferred)

Previously, PriorityClassName shared protobuf tag 7 with Env; it now uses tag 8, leaving Env on tag 7.

Evidence“- Changed `PriorityClassName` protobuf tag from 7 to 8” tektoncd/pipeline/pull/9229 ↗
Show release-note lines
* :bug: Fix duplicated protobuf tag in pod.Template struct (#9229)
github.com/tektoncd/pipeline/releases/tag/v1.9.0

Shortened v1beta1 CRD descriptions fix installation errors

Affectsinstallations applying v1beta1 CRDs

Applying CRDs with verbose embedded descriptions could fail with a metadata.annotations: Too long error. kubectl explain now shows less detail; detailed API field descriptions remain available in the Tekton documentation or in v1 fields.

Evidence“To resolve "metadata.annotations: Too long" errors during installation, the field descriptions embedded in `v1beta1` CRDs (visible via `kubectl explain`) have been significantly shortened. Users should refer to the [Tekton documentation](https://tekton.dev/docs/) for detailed API field descriptions or use descriptions in v1 fields.” tektoncd/pipeline/pull/9252 ↗
Show release-note lines
* :hammer: fix: reduce CRD size by shortening verbose descriptions (#9252)
github.com/tektoncd/pipeline/releases/tag/v1.9.0

Corrected streaming-list handling for PipelineRunList

Affectsthe v1 or v1beta1 PipelineRunList API types

Previously, items could be omitted from the JSON and was not marked required in the generated schema, so Kubernetes API streaming-list handling did not correctly interpret these types. Now items is always serialized and marked required.

Evidence“- Removes ',omitempty' from the 'Items' field in the v1 and v1beta1 PipelineRunList structs.” tektoncd/pipeline/pull/9240 ↗
Show release-note lines
* :hammer: fix(codegen): Correct JSON tags for streaming lists (#9240)
github.com/tektoncd/pipeline/releases/tag/v1.9.0

ListMeta JSON tag gains omitempty in v1beta1 ResolutionRequestList

Affectssetups using the v1beta1 ResolutionRequestList type and its JSON representation(Inferred)

The ListMeta field's JSON tag changes from json:"metadata" to json:"metadata,omitempty".

Evidence“- Adds ',omitempty' to the 'ListMeta' field in the v1beta1 ResolutionRequestList struct.” tektoncd/pipeline/pull/9240 ↗
Show release-note lines
* :hammer: fix(codegen): Correct JSON tags for streaming lists (#9240)
github.com/tektoncd/pipeline/releases/tag/v1.9.0

Custom task API versions now require group/version format

AffectsPipelines using custom tasks with taskRef.apiVersion or taskSpec.apiVersion

Previously, invalid values such as invalid-api-version could leave PipelineRuns creating unhandled CustomRuns that timed out. Now, Pipeline creation fails immediately with a clear error when either value is invalid.

Evidence“add validation to ensure taskRef.apiVersion follows the correct format (group/version) when specified. Previously, invalid apiVersion values like 'invalid-api-version' were accepted, causing PipelineRuns to create unhandled CustomRuns that would timeout. Now Pipeline creation fails immediately with a clear error message when an invalid apiVersion is provided.” tektoncd/pipeline/pull/9045 ↗
Show release-note lines
* :bug: fix: validate taskRef.apiVersion format for custom tasks (#9045)
github.com/tektoncd/pipeline/releases/tag/v1.9.0

Important fixes7

  • Affinity Assistant ServiceAccount inheritance fixed
    AffectsPipelineRuns with Affinity Assistant pods and a taskRunTemplate.serviceAccountName set

    Previously, these pods always used the namespace's default ServiceAccount, which could lack required SCC permissions and cause workspace-coscheduled PipelineRuns to fail in OpenShift. Now they use the PipelineRun's taskRunTemplate.serviceAccountName unless AffinityAssistantTemplate specifies an override; if neither provides a value, they use the namespace's default ServiceAccount.

    * :sparkles: feat: add ServiceAccount inheritance to Affinity Assistants (#9253)
    github.com/tektoncd/pipeline/releases/tag/v1.9.0
  • Redundant PipelineRun status writes fixed
    AffectsPipelineRuns reconciled with child references written to status

    Unordered child-reference arrays caused massive repeated status writes, particularly for PipelineRuns with more than 64 child TaskRuns, and were associated with apiserver memory spikes and high write QPS. Child references are now consistently ordered, mitigating the redundant writes and their associated apiserver load and stability impact.

    * :bug: fix(pipelinerun): fix the issue of massive invalid status updates caused by unordered arrays, which will greatly impact the resource load and stability of the apiserver. (#9295)
    github.com/tektoncd/pipeline/releases/tag/v1.9.0
  • Pipeline parameter defaults now resolve references
    AffectsPipelineSpecs with parameter defaults that reference other parameters

    Previously, the literal reference could reach a task and cause pod creation to fail. Now the task receives the resolved parameter value, allowing the pod to be created successfully.

    * :bug: Fix parameter resolution for defaults with  references (#9271)
    github.com/tektoncd/pipeline/releases/tag/v1.9.0
  • Circular parameter dependencies detected at PipelineRun creation
    AffectsPipelineRuns with circular references between parameter defaults

    These cycles previously surfaced during task pod creation as misleading errors. They now fail validation when the PipelineRun is created, with an error identifying the circular dependency.

    * :bug: Fix parameter resolution for defaults with  references (#9271)
    github.com/tektoncd/pipeline/releases/tag/v1.9.0
  • Undefined PipelineRun parameter references caught during validation
    AffectsPipelineRun parameter defaults

    When a default referenced an undefined parameter, resolution did not catch it, and a misleading error could appear later during task pod creation. Now validation fails with an error identifying the undefined reference.

    * :bug: Fix parameter resolution for defaults with  references (#9271)
    github.com/tektoncd/pipeline/releases/tag/v1.9.0
  • Excessive reconciliation for TaskRuns and PipelineRuns without timeouts fixed
    AffectsTaskRuns and PipelineRuns with no configured timeout: timeout set to 0, or unset while default-timeout-minutes is "0"

    Previously, these runs were requeued immediately, causing excessive reconciliation. With no timeout, reconciliation now relies on watch events; configured task- or finally-specific timeouts still trigger a requeue for their timeout.

    * :bug: fix: Prevent excessive reconciliation when timeout disabled (#9202)
    github.com/tektoncd/pipeline/releases/tag/v1.9.0
  • TaskRun pod container errors now fail fast
    AffectsTaskRuns with pod containers configured to use ConfigMaps or Secrets through valueFrom

    When pod containers had configuration or container-creation errors, including missing ConfigMaps or Secrets referenced through valueFrom, TaskRuns could wait and report only a generic timeout. They now fail as soon as the error is detected, with actionable errors such as CreateContainerConfigError or PodCreationFailed.

    * :bug: fix: Detect pod configuration errors early instead of timeout (#9197)
    github.com/tektoncd/pipeline/releases/tag/v1.9.0

Enhancements2

  • User namespace selection in TaskRun and PipelineRun PodTemplates

    To use The Kubernetes feature gate UserNamespacesSupport must be enabled to use this field.

    * :sparkles: Add hostUsers field support to PodTemplate (#9227)
    github.com/tektoncd/pipeline/releases/tag/v1.9.0
  • HTTP resolver digest verification added

    To use enable-http-resolver feature flag, enabled by default

    * :sparkles: feat: Add digest validation support to HTTP resolver (#9171)
    github.com/tektoncd/pipeline/releases/tag/v1.9.0

Dependency updates30

    30 more, none mentioning security
    • * :hammer: build(deps): bump go.uber.org/zap from 1.27.0 to 1.27.1 (#9333)
    • * :hammer: build(deps): bump github.com/google/cel-go from 0.26.0 to 0.27.0 (#9330)
    • * :hammer: build(deps): bump golang.org/x/sync from 0.18.0 to 0.19.0 (#9293)
    • * :hammer: build(deps): bump github.com/hashicorp/go-version from 1.7.0 to 1.8.0 (#9288)
    • * :hammer: build(deps): bump k8s.io/apiextensions-apiserver from 0.32.8 to 0.32.11 (#9286)
    • * :hammer: build(deps): bump github.com/spiffe/spire-api-sdk from 1.12.4 to 1.14.0 (#9261)
    • * :hammer: build(deps): bump go.opentelemetry.io/otel/sdk from 1.38.0 to 1.39.0 (#9259)
    • * :hammer: build(deps): bump github.com/cloudevents/sdk-go/v2 from 2.16.1 to 2.16.2 (#9258)
    • * :hammer: build(deps): bump k8s.io/client-go from 0.32.8 to 0.32.11 (#9256)
    • * :hammer: build(deps): bump google.golang.org/protobuf from 1.36.10 to 1.36.11 (#9254)
    • * :hammer: build(deps): bump github/codeql-action from 4.31.8 to 4.31.9 (#9247)
    • * :hammer: build(deps): bump the all group in /tekton with 2 updates (#9246)
    • * :hammer: build(deps): bump go.opentelemetry.io/otel/trace from 1.37.0 to 1.39.0 (#9245)
    • * :hammer: build(deps): bump k8s.io/apimachinery from 0.33.3 to 0.33.7 (#9244)
    • * :hammer: build(deps): bump the all group in /tekton with 4 updates (#9236)
    • * :hammer: build(deps): bump step-security/harden-runner from 2.13.3 to 2.14.0 (#9235)
    • * :hammer: build(deps): bump github/codeql-action from 4.31.7 to 4.31.8 (#9234)
    • * :hammer: build(deps): bump actions/cache from 4.3.0 to 5.0.1 (#9233)
    • * :hammer: build(deps): bump tj-actions/changed-files from abdd2f68ea150cee8f236d4a9fb4e0f2491abf1b to e0021407031f5be11a464abee9a0776171c79891 (#9232)
    • * :hammer: build(deps): bump actions/upload-artifact from 5.0.0 to 6.0.0 (#9231)
    • * :hammer: build(deps): bump the all group across 1 directory with 4 updates (#9220)
    • * :hammer: build(deps): bump actions/checkout from 6.0.0 to 6.0.1 (#9219)
    • * :hammer: build(deps): bump golangci/golangci-lint-action from 9.1.0 to 9.2.0 (#9218)
    • * :hammer: build(deps): bump peter-evans/slash-command-dispatch from 4.0.0 to 5.0.1 (#9217)
    • * :hammer: build(deps): bump step-security/harden-runner from 2.13.2 to 2.13.3 (#9216)
    • * :hammer: build(deps): bump github/codeql-action from 4.31.6 to 4.31.7 (#9215)
    • * :hammer: build(deps): bump actions/github-script from 7.0.1 to 8.0.0 (#9195)
    • * :hammer: build(deps): bump github/codeql-action from 4.31.5 to 4.31.6 (#9194)
    • * :hammer: build(deps): bump github.com/jenkins-x/go-scm from 1.15.4 to 1.15.16 (#9183)
    • * :hammer: build(deps): bump google.golang.org/grpc from 1.75.0 to 1.77.0 (#9177)
    Other changes39

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