RATATOSK
← All releases

Tektonv1.10.0

Breaking changes 4Deprecations 1Important fixes 3Enhancements 1Dependency updates 23Other changes 37

Get Tekton alerts

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

Check before upgrading

Prerequisites1
Observability metrics destination setting updated

The config-observability ConfigMap should use metrics-protocol set to prometheus, grpc, or http instead of metrics.backend-destination. No change is needed if Prometheus was already in use.

  Upgrade actions:
  1. **Update Config**: Ensure your `config-observability` ConfigMap uses `metrics-protocol: prometheus` (or `grpc`/`http`) instead of the old `metrics.backend-destination`. If prometheus was already being used, no changes are needed.
github.com/tektoncd/pipeline/releases/tag/v1.10.0
Upgrade guide1
Full metrics migration table
  See the [full migration table in PR #9043](https://github.com/tektoncd/pipeline/pull/9043) for complete details.
github.com/tektoncd/pipeline/releases/tag/v1.10.0

Breaking changes4

Tekton infrastructure metrics renamed

Affectssetups that collect or query Tekton infrastructure metrics, including Go runtime, Workqueue, or Kubernetes client metrics
Action requiredUpdate config-observability to use metrics-protocol: prometheus (or grpc/http) instead of metrics.backend-destination, unless Prometheus was already in use; update dashboard queries to the new metric names and check pipelinerun_duration_seconds aggregations for the added reason label.

These metrics previously used the tekton_pipelines_controller_ prefix, such as tekton_pipelines_controller_workqueue_adds_total; they are now emitted under names such as kn_workqueue_adds_total, http_client_request_duration_seconds, and go_*.

Show release-note lines
* :rotating_light: **Metrics migration from OpenCensus to OpenTelemetry** (#9043)
  **ACTION REQUIRED**: Infrastructure metrics (Go runtime, Workqueue, K8s Client) have been renamed from the `tekton_pipelines_controller_` prefix to standard OpenTelemetry/Knative namespaces. The `reason` label has been added to duration metrics (`pipelinerun_duration_seconds`, `taskrun_duration_seconds`). The `reconcile_count` and `reconcile_latency` metrics have been removed.
github.com/tektoncd/pipeline/releases/tag/v1.10.0

Tekton controller reconcile metrics removed

Affectscontroller-performance monitoring using either custom reconcile metric

The pull request points to kn_workqueue_process_duration_seconds and kn_workqueue_adds_total for controller-performance monitoring.

Evidence“3. Removed Metrics * `tekton_pipelines_controller_reconcile_count` and `tekton_pipelines_controller_reconcile_latency`: These custom reconcile metrics are no longer emitted. Users should rely on kn_workqueue_process_duration_seconds and kn_workqueue_adds_total to monitor controller performance.” tektoncd/pipeline/pull/9043 ↗
Show release-note lines
  **ACTION REQUIRED**: Infrastructure metrics (Go runtime, Workqueue, K8s Client) have been renamed from the `tekton_pipelines_controller_` prefix to standard OpenTelemetry/Knative namespaces. The `reason` label has been added to duration metrics (`pipelinerun_duration_seconds`, `taskrun_duration_seconds`). The `reconcile_count` and `reconcile_latency` metrics have been removed.
github.com/tektoncd/pipeline/releases/tag/v1.10.0

PipelineRun and TaskRun metrics migrate to OpenTelemetry

Affectssetups collecting or querying PipelineRun, TaskRun, or infrastructure metrics(Inferred)
Action requiredThe config-observability ConfigMap uses metrics-protocol: prometheus (or grpc/http) instead of metrics.backend-destination, unless Prometheus was already in use; dashboards use kn_workqueue_* and go_* in place of the old names, and duration aggregations account for the reason label.

Previously, infrastructure metrics used the tekton_pipelines_controller_ prefix, duration metrics lacked the reason label, and the two custom reconcile metrics were emitted. Infrastructure metrics now use standard OpenTelemetry and Knative names, including kn_workqueue_* and go_*; duration metrics gain the reason label, and the custom reconcile metrics are no longer emitted.

Evidence“* `tekton_pipelines_controller_reconcile_count` and `tekton_pipelines_controller_reconcile_latency`: These custom reconcile metrics are no longer emitted. Users should rely on” tektoncd/pipeline/pull/9043 ↗
Show release-note lines
* :sparkles: feat(metrics): Migrate from OpenCensus to OpenTelemetry (#9043)
  Migrated PipelineRun and TaskRun metrics to OpenTelemetry instruments (histograms, counters, gauges). Updated Knative to 1.19. See [Upgrade Notices](#upgrade-notices) for breaking changes and required actions.
github.com/tektoncd/pipeline/releases/tag/v1.10.0

Metrics configuration switches to metrics-protocol

Affectsmetrics settings in the config-observability ConfigMap

The prior metrics.backend-destination setting is replaced by metrics-protocol with prometheus, grpc, or http; installations already using Prometheus need no configuration change. Infrastructure metrics now use standard OpenTelemetry/Knative namespaces instead of the tekton_pipelines_controller_ prefix, and reconcile_count and reconcile_latency are removed.

Evidence“1. **Update Config**: Ensure your `config-observability` ConfigMap uses `metrics-protocol: prometheus` (or `grpc`/`http`) instead of the old `metrics.backend-destination`. If prometheus was already being used, no changes are needed.” tektoncd/pipeline/releases/tag/v1.10.0 ↗
Show release-note lines
  Migrated PipelineRun and TaskRun metrics to OpenTelemetry instruments (histograms, counters, gauges). Updated Knative to 1.19. See [Upgrade Notices](#upgrade-notices) for breaking changes and required actions.
github.com/tektoncd/pipeline/releases/tag/v1.10.0

Deprecations1

Unused featureFlags.EnableTektonOCIBundles field accepted for compatibility

AffectsPipelineRun and TaskRun resources containing featureFlags.EnableTektonOCIBundles(Inferred)
Removed innot stated

Previously, EnableTektonOCIBundles was treated as an unknown field. It is now accepted but has no effect, and is retained to allow deletion of PipelineRuns created before v0.62.x.

Show release-note lines
* :bug: accept featureFlags.EnableTektonOCIBundles to fix unknown field error (#8996)
github.com/tektoncd/pipeline/releases/tag/v1.10.0

Important fixes3

  • Redundant ResolutionRequest short names removed
    Affectsinstallations using the ResolutionRequest CRD on Kubernetes 1.33+

    On Kubernetes 1.33+, the redundant short names caused a ShortNamesConflict condition on the CRD.

    * :bug: fix: Remove redundant shortNames from ResolutionRequest CRD (#9398)
      Remove redundant shortNames from ResolutionRequest CRD that caused ShortNamesConflict on Kubernetes 1.33+
    github.com/tektoncd/pipeline/releases/tag/v1.10.0
  • PipelineRun validation accepts non-parameter variables in defaults
    AffectsPipelineRuns with non-parameter variables in pipeline parameter defaults

    Previously, validation failed when a pipeline parameter default referenced a value such as $(context.pipelineRun.name). Such defaults now validate without that failure.

    * :bug: fix(pipelines): allow pipeline param defaults to use non-param variables (#9386)
      Fixed a bug which caused PipelineRun validation to fail when a pipeline parameter's default value referenced a non-parameter variable (e.g. `$(context.pipelineRun.name)`)
    github.com/tektoncd/pipeline/releases/tag/v1.10.0
  • Pipeline-level results include outputs from unsuccessful tasks
    AffectsPipelineRuns with pipeline-level results referencing outputs from failed, cancelled, or timed-out tasks

    Previously, these references could remain unresolved variable strings. Results from completed failed, cancelled, or timed-out tasks are now included in pipeline-level results.

    * :bug: fix: pipeline-level results not recorded from failed tasks (#9367)
      Pipeline-level results now include results from failed, cancelled, and timed-out tasks, fixing cases where results referencing non-successful task outputs were left as unresolved variable strings.
    github.com/tektoncd/pipeline/releases/tag/v1.10.0

Enhancements1

  • Git resolver recognizes SHA-256 commit hashes
    * :sparkles: feat: Add SHA-256 support for Git resolver revision validation (#9278)
      Git resolver now supports SHA-256 commit hashes for revision validation.
    github.com/tektoncd/pipeline/releases/tag/v1.10.0

Dependency updates23

    23 more, none mentioning security
    • Migrated PipelineRun and TaskRun metrics to OpenTelemetry instruments (histograms, counters, gauges). Updated Knative to 1.19. See [Upgrade Notices](#upgrade-notices) for breaking changes and required actions.
    • * :hammer: build(deps): bump golang.org/x/crypto from 0.36.0 to 0.45.0 in /test/resolver-with-timeout (#9426)
    • * :hammer: build(deps): bump opentelemetry exporter packages to v1.39.0 (#9332)
    • * :hammer: build(deps): bump github.com/google/go-containerregistry from 0.21.0 to 0.21.1 (#9433)
    • * :hammer: build(deps): bump github.com/google/go-containerregistry from 0.20.7 to 0.21.0 (#9418)
    • * :hammer: build(deps): bump google.golang.org/grpc from 1.79.0 to 1.79.1 (#9392)
    • * :hammer: build(deps): bump github.com/jenkins-x/go-scm from 1.15.16 to 1.15.17 (#9391)
    • * :hammer: build(deps): bump google.golang.org/grpc from 1.78.0 to 1.79.0 (#9389)
    • * :hammer: build(deps): bump k8s.io/code-generator from 0.32.11 to 0.32.12 (#9388)
    • * :hammer: build(deps): bump k8s.io/apiextensions-apiserver from 0.32.11 to 0.32.12 (#9385)
    • * :hammer: build(deps): bump k8s.io/apimachinery from 0.33.7 to 0.33.8 (#9384)
    • * :hammer: build(deps): bump k8s.io/client-go from 0.32.11 to 0.32.12 (#9383)
    • * :hammer: build(deps): bump github/codeql-action from 4.32.1 to 4.32.2 (#9374)
    • * :hammer: build(deps): bump the all group in /tekton with 4 updates (#9373)
    • * :hammer: build(deps): bump step-security/harden-runner from 2.14.1 to 2.14.2 (#9372)
    • * :hammer: build(deps): bump tj-actions/changed-files from 47.0.1 to 47.0.2 (#9371)
    • * :hammer: build(deps): bump chainguard-dev/actions from 1.5.14 to 1.5.16 (#9370)
    • * :hammer: build(deps): bump golang.org/x/crypto from 0.47.0 to 0.48.0 (#9369)
    • * :hammer: build(deps): bump go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp from 1.39.0 to 1.40.0 (#9363)
    • * :hammer: build(deps): bump go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp from 1.37.0 to 1.40.0 (#9345)
    • * :hammer: build(deps): bump google.golang.org/grpc from 1.77.0 to 1.78.0 (#9337)
    • * :hammer: build(deps): bump github.com/spiffe/spire-api-sdk from 1.14.0 to 1.14.1 (#9336)
    • * :hammer: build(deps): bump sigstore/sigstore from 1.9.5 to 1.10.4 (#9331)
    Other changes37

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