# Tekton v1.0.0

2025-05-01 · [Original release notes](https://github.com/tektoncd/pipeline/releases/tag/v1.0.0) · [Full summary](https://ratatosk.io/en/releases/tekton/v1.0.0)

Breaking changes 4 · Deprecations 1 · Important fixes 3 · Enhancements 3 · Dependency updates 21 · Other changes 5

## Check before upgrading

### Defects found after release

- Git resolver system-token leak fixed · Fixed in v1.0.2
- HTTP resolver response-body limit prevents memory exhaustion · Fixed in v1.0.2

## Breaking changes (4)

### `disable-affinity-assistant` removed in favor of `coschedule`

- Affects: Tekton configurations using `disable-affinity-assistant` (Inferred)
- Action required: Use `coschedule` instead; set it to `disabled` to maintain the previous default behavior.

The field was retained for client-code compatibility after its deprecation in v0.51. This release's webhook rejects it, and the rest of the code ignores it.

Evidence: “Action Required: The feature flag `disable-affinity-assistant` has been removed. Please use `coschedule` as a replacement. It was marked as deprecated in version v0.51 and has been completely removed in the current version. If you need to maintain the previous default behavior, set feature flag `coschedule` to `disabled`.” https://github.com/tektoncd/pipeline/pull/8603

> * :hammer: cleanup: [TEP-0135] remove deprecated disable-affinity-assistant feature flag (#8603)

### Tekton makes `keep-pod-on-cancel` beta and enables it by default

- Affects: Tekton Pipelines installations using `keep-pod-on-cancel` (Inferred)

Previously, the flag was alpha and used `DefaultAlphaFeatureEnabled` as its default.

> * :hammer: misc: promote  to beta (#8343)
> `keep-pod-on-cancel` feature flag will be enabled in default

### Git Resolver switches to shallow cloning and fetching with `git`

- Affects: RemoteResolutions using the Git Resolver
- Action required: `uploadpack.allowReachableSHA1InWant` enabled on the Git server for SHA revisions not at a ref head or tag

Previously, resolving files—especially through anonymous Git clone—could consume excessive time and memory, and `WithTimeout` could not bound that work; shallow cloning and fetching reduce both. On some providers, including Gitea, fetching a SHA revision not reachable via a ref may still fail.

> * :sparkles: fix: resolve Git Anonymous Resolver excessive memory usage (#8677)
> RemoteResolutions using the Git Resolver now use the `git` binary instead of  the Golang library `go-git` to shallow-clone, shallow-fetch, then checkout the provided repository at the given revision. This reduces resolution time and memory significantly. Some git providers such as Gitea may not support fetching revisions if the revision is a SHA which is not reachable via a ref or is not at a ref/head. In general, no user action is required.
> See also: https://git-scm.com/docs/protocol-capabilities#_allow_reachable_sha1_in_want
> Resolves https://github.com/tektoncd/pipeline/issues/8652

### `ClusterTask` support and CRD removed

- Affects: setups using `ClusterTask` resources or support (Inferred)

> * :hammer: cleanup: remove clustertask support (#8601)
> Remove ClusterTask support completely

## Deprecations (1)

### StepActions reach GA and `enable-step-actions` becomes a no-op

- Affects: Setups using StepActions or configuring `enable-step-actions` (Inferred)
- Removed in: a later release

Previously, StepActions were beta, and specifying a `StepAction` in a `Step` required `enable-step-actions` to be set to `"true"`. StepActions are now available by default, so the flag no longer determines whether a `Step` can specify a `StepAction`.

> * :sparkles: feat: promote StepActions to GA (#8546)
> StepActions promoted to GA and is available by default. The enable-step-actions feature flag exists as a no-op flag to ensure that existing user workflows which might rely on this flag are not disabled. This flag will be removed completely in a later release.

## Important fixes (3)

### Configurable retry backoff for bundle image requests

- Affects: setups using the bundle resolver

During transient network issues while retrieving bundle images, requests previously had no configured retry backoff and could be affected by network flakes. They now use configured backoff values or defaults of 2 seconds, factor 2.0, jitter 0.1, 2 steps, and a 10-second cap.

> * :sparkles: Add configuration for custom bundle resolver backoff (#8574)
> Enables the configuration of backoffs for a bundle resolver requests.

### Matrix tasks resolve with empty result arrays

- Affects: matrix parameters populated from prior task results (Inferred)

When the result reference was used while the parameter's `ArrayVal` was empty, the combination count became zero, leaving the task unresolved and causing validation to fail with an invalid result reference.

> * :bug: fix: avoid fan out matrix task failed due to result ref (#8487)
> fix: avoid fan out matrix task failed due to result ref

### Transient subPath directory creation failures no longer fail TaskRuns immediately

- Affects: TaskRuns using subPath directories

Previously, a TaskRun was failed immediately when a container was waiting with a `CreateContainerConfigError` message containing “failed to create subPath directory.” It now stays running with `ReasonPodPending` while waiting for recovery.

> * :bug: fix: handle subPath directory creation errors gracefully (#8683)

## Enhancements (3)

- PipelineRun `onError` parameter substitution
- Git resolver go-git cloning supports token authentication (To use: `gitToken` configured with a secret name; `gitTokenKey` optionally selects its key and defaults to `token`.)
- Hub resolver accepts `stepaction` as a kind

## Dependency updates (21)

21 more, none mentioning security

- `* :hammer: Bump go.mod and tools/go.mod to go 1.23 (#8482) Updating go to 1.23`
- `* :hammer: build(deps): bump github/codeql-action from 3.28.15 to 3.28.16 (#8729)`
- `* :hammer: build(deps): bump step-security/harden-runner from 2.11.1 to 2.12.0 (#8728)`
- `* :hammer: build(deps): bump the all group in /tekton with 4 updates (#8727)`
- `* :hammer: build(deps): bump github.com/sigstore/sigstore from 1.8.15 to 1.9.4 (#8724)`
- `* :hammer: build(deps): bump k8s.io/apimachinery from 0.32.2 to 0.32.4 (#8723)`
- `* :hammer: build(deps): bump the all group in /tekton with 2 updates (#8722)`
- `* :hammer: build(deps): bump tj-actions/changed-files from be393a90381e27c9fec2c8c2e02b00f005710145 to c34c1c13a740b06851baff92ab9a653d93ad6ce7 (#8721)`
- `* :hammer: build(deps): bump github/codeql-action from 3.28.14 to 3.28.15 (#8705)`
- `* :hammer: build(deps): bump tj-actions/changed-files from 6abeaa506a419f85fa9e681260b443adbeebb3d4 to be393a90381e27c9fec2c8c2e02b00f005710145 (#8704)`
- `* :hammer: build(deps): bump ko-build/setup-ko from 0.8 to 0.9 (#8703)`
- `* :hammer: build(deps): bump the all group in /tekton with 4 updates (#8702)`
- `* :hammer: build(deps): bump github/codeql-action from 3.28.13 to 3.28.14 (#8690)`
- `* :hammer: build(deps): bump tj-actions/changed-files from 27ae6b33eaed7bf87272fdeb9f1c54f9facc9d99 to 6abeaa506a419f85fa9e681260b443adbeebb3d4 (#8689)`
- `* :hammer: build(deps): bump actions/dependency-review-action from 4.5.0 to 4.6.0 (#8688)`
- `* :hammer: build(deps): bump step-security/harden-runner from 2.11.0 to 2.11.1 (#8687)`
- `* :hammer: build(deps): bump the all group in /tekton with 2 updates (#8686)`
- `* :hammer: build(deps): bump github.com/go-jose/go-jose/v4 from 4.0.4 to 4.0.5 (#8680)`
- `* :hammer: build(deps): bump github.com/golang-jwt/jwt/v5 from 5.2.1 to 5.2.2 (#8678)`
- `* :hammer: build(deps): bump go.opentelemetry.io/otel from 1.34.0 to 1.35.0 (#8676)`
- `* :hammer: build(deps): bump k8s.io/code-generator from 0.31.6 to 0.31.7 (#8645)`

## Other changes (5)

- Release pipeline now gets `ko` and task-bundle images from GHCR
- Releases document adds v0.70 and corrects dates for v0.64 and v0.69
- Step-guard documentation for `when` expressions moved to Tasks
- TaskRun docs updated for resource request overrides and API v1 terms
- Enum parameter usage added to the `StepAction` `TaskRun` example

---

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