Tekton
v1.13.1CI/CD & App DeliveryJun 15, 2026
This release includes defect corrections and a behavior change in Tekton's handling of internal-container resources. Operators relying on implicit resource requests or limits are affected when `default-container-resource-requirements` is unset.
Check if affected (1)
breakingDefault resource requirements for internal containers, removed
Applies if
default-container-resource-requirementsis unset and you rely on implicit resource requests or limits for internal containers.Tekton v1.13.1 no longer applies default resource requests or limits to the internal containers
prepare,place-scripts,working-dir-initializer, andsidecar-tekton-log-resultswhendefault-container-resource-requirementsis unset.
All 3 other recorded changesfixes 3
fixes (3)
- * :bug: [cherry-pick: release-v1.13.x] fix(resolvers): Allow ResolutionRequests to resolve all Tekton kinds (#10251) Before this change, ResolutionRequests could only resolve Pipelines, Tasks, and StepActions. After this change, ResolutionRequests can resolve PipelineRuns, Pipelines, TaskRuns, Tasks, Runs, CustomRuns, and StepActions.
- * :bug: [cherry-pick: release-v1.13.x] fix: TaskRun stuck in Running when init container is OOMKilled with enableKubernetesSidecar (#10183) Fix: TaskRun no longer gets stuck in Running when an init container (e.g. prepare) is OOMKilled while enableKubernetesSidecar is enabled. The TaskRun is now correctly marked as Failed immediately.
- * :bug: [cherry-pick: release-v1.13.x] fix: avoid spurious termination parse warning (#10182) Fixed spurious step log warnings about parsing existing termination messages when termination message compression is disabled.
Add Tekton to your stack
A weekly email arrives when a release needs action. Like the breaking changes in this release.