What tektoncd/pipeline shipped
Written by FoxPlug from the repository's own releases; not affiliated with Tekton. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/tektoncd/pipeline; Tekton did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.
Get a weekly update like this for your product, free
Week of October 19, 2026
What shipped
- PipelineRuns created inside a parent PipelineRun no longer inherit the auto-cleanup-pvc annotation, so child VolumeClaimTemplate PVCs are no longer deleted on completion. Pull request #9727
- Golang.org/x/crypto was bumped from v0.55.0 to v0.58.0, fixing two denial-of-service issues in ssh where a peer can deadlock a connection by flooding channel requests. Pull request #10910
- The plumbing ko image pinned in tekton/publish.yaml was bumped to a build based on Go 1.27.3, unblocking the patch releases. Pull request #10937
- Go was bumped to 1.27.3 to fix CVE-2026-111943, where crypto/x509 now distrusts chains relying on compromised eMudhra intermediate CA keys. Pull request #10918
- Go was bumped to 1.27.3 for CVE-2026-111943 and the golangci-lint pin was moved from v2.12.2 to v2.15.0. Pull request #10916
- Tekton Pipeline v1.15.4 was released on the LTS line with docs, examples and attestation. Release
- Tekton Pipeline v1.15.5 was released on the LTS line with docs, examples and attestation. Release
- Tekton Pipeline v1.17.1 was released with docs, examples and attestation. Release
- Tekton Pipeline v1.12.3 was released on the LTS line with docs, examples and attestation. Release
- Tekton Pipeline v1.9.9 was released with docs, examples and attestation. Release
Why it matters
This week was mostly about getting patch releases out safely: a Go update for CVE-2026-111943, a ko image bump it required, and a vendor tarball copy fix in the release plumbing landed across the release branches. Releases went out on several maintained lines, including the LTS lines, plus a dependency bump for two ssh denial-of-service issues. For users, the fixes concern certificate chain validation, dependency bumps and one annotation bug that caused child PVCs to be deleted.
Changelog entry
- Stop the auto-cleanup-pvc annotation from propagating from a parent PipelineRun to child PipelineRuns, so child VolumeClaimTemplate PVCs are not auto-deleted on completion. Pull request #9727
- Bump golang.org/x/crypto from v0.55.0 to v0.58.0, fixing CVE-2026-78662 and CVE-2026-56855, denial-of-service issues in ssh channel request handling. Pull request #10910
- Bump the plumbing ko image in tekton/publish.yaml to a Go 1.27.3 build so the release pipeline runs. Pull request #10937
- Cherry-pick the ko image bump to release-v1.6.x. Pull request #10942
- Cherry-pick the ko image bump to release-v1.12.x. Pull request #10940
- Cherry-pick the ko image bump to release-v1.15.x. Pull request #10939
- Cherry-pick the ko image bump to release-v1.17.x. Pull request #10938
- Cherry-pick the ko image bump to release-v1.9.x. Pull request #10941
- Bump Go to 1.27.3 on release-v1.12.x to fix CVE-2026-111943; vendor unchanged and CI golangci-lint pin bumped. Pull request #10918
- Bump Go to 1.27.3 on release-v1.15.x for CVE-2026-111943 and bump the golangci-lint pin from v2.12.2 to v2.15.0. Pull request #10916
- Bump Go to 1.27.3 on release-v1.9.x for CVE-2026-111943 and bump the golangci-lint pin from v2.8.0 to v2.15.0. Pull request #10919
- Bump Go from 1.25.10 to 1.27.3 on release-v1.6.x for CVE-2026-111943. Pull request #10920
Patch releases are out on several lines, including the LTS lines. This week brought a Go 1.27.3 bump for CVE-2026-111943, the release plumbing changes it needed, and a golang.org/x/crypto bump fixing two ssh denial-of-service issues. The auto-cleanup-pvc annotation no longer leak
This week Tekton Pipeline shipped patch releases across several maintained lines, including the LTS lines. The main fixes: Go was bumped to 1.27.3 to address CVE-2026-111943, where crypto/x509 now distrusts certificate chains relying on compromised eMudhra intermediate CA keys; the release plumbing ko image was updated to a Go 1.27.3 build, and a vendor tarball is now copied into kodata instead of symlinked, which unblocked the patch releases. golang.org/x/crypto moved to v0.58.0, fixing two ssh denial-of-service issues where a peer could deadlock a connection by flooding channel requests. Separately, a parent PipelineRun's auto-cleanup-pvc annotation no longer propagates to child PipelineRuns, so child VolumeClaimTemplate PVCs are not deleted on completion.
Week of October 5, 2026
What shipped
- Controller-managed labels tekton.dev/pipeline, tekton.dev/pipelineTask and tekton.dev/pipelineRun are now immutable through the webhook, so the reconciler can keep trusting them. Pull request #10687
- Step onError now accepts continueAndFail, which lets the remaining steps run after a step exits with a non-zero code. Pull request #10536
- OCI bundle tar layers are now read with io.ReadFull, so a short read from the streaming gunzip reader no longer truncates the layer. Pull request #10395
- The docs now explain that the retry-count variable is substituted on the PipelineTask before the TaskRun is created, so with taskRef it must be passed in through PipelineTask params. Pull request #9821
- On release-v1.9.x, golang.org/x/crypto moved from v0.52.0 to v0.55.0 along with its required module and vendored dependencies. Pull request #10862
- On release-v1.12.x, golang.org/x/crypto moved from v0.54.0 to v0.55.0 along with its required vendored dependencies. Pull request #10861
Why it matters
This week fixes behavior people run into in real pipelines: retry-count substitution with taskRef is now documented, OCI bundles read reliably, steps can continue after a failure and the labels the reconciler trusts can no longer be changed by hand. Users who depend on Pipeline-in-Pipeline cycle detection and other label-based logic get a more dependable controller, and both maintained release branches pick up the same crypto dependency update.
Changelog entry
- Controller-managed labels tekton.dev/pipeline, tekton.dev/pipelineTask and tekton.dev/pipelineRun are now immutable via the webhook. Pull request #10687
- Step onError now supports continueAndFail: remaining steps run after a step exits with a non-zero code. Pull request #10536
- OCI bundle tar layers are now read with io.ReadFull to avoid truncated reads from the streaming gunzip reader. Pull request #10395
- Docs clarify that the retry-count variable is substituted on the PipelineTask before the TaskRun is created and must be passed through PipelineTask params when using taskRef. Pull request #9821
- Release-v1.9.x: golang.org/x/crypto updated from v0.52.0 to v0.55.0 with refreshed module and vendored dependencies. Pull request #10862
- Release-v1.12.x: golang.org/x/crypto updated from v0.54.0 to v0.55.0 with refreshed vendored dependencies. Pull request #10861
This week: controller-managed labels are now immutable via webhook, step onError gains continueAndFail, OCI bundle tar layers read reliably, and retry-count substitution with taskRef is documented. The crypto bump also landed on both release branches.
This week in Tekton Pipelines: controller-managed labels (tekton.dev/pipeline, tekton.dev/pipelineTask, tekton.dev/pipelineRun) are now immutable through the webhook, so reconciler logic such as Pipelines-in-Pipelines cycle detection can keep trusting them. Step onError accepts a third value, continueAndFail, which runs the remaining steps after a step exits with a non-zero code. OCI bundle tar layers are read with io.ReadFull, avoiding truncated reads from the streaming gunzip reader. The docs now explain that the retry-count variable is substituted on the PipelineTask before the TaskRun is created, so with taskRef it must be passed through PipelineTask params. The golang.org/x/crypto 0.55.0 update was also backported to release-v1.9.x and release-v1.12.x.
Week of September 28, 2026
What shipped
- Tekton Pipeline v1.17.0 released with improvements to failure clarity and tracing. Release
- Added reconcile.write_intent span attribute to PipelineRun and TaskRun for better tracing. Pull request #10827
- Fixed Windows script placement to use non-expandable here-strings, preventing script content from terminating strings prematurely. Pull request #10690
- Fixed Windows script handling when script body contains sequences like "@ that could terminate PowerShell here-strings. Pull request #10690
- Windows scripts with parameter values containing "@ sequences are now handled correctly. Pull request #10690
- Task resolution failures now include the task name in error messages for better debugging. Pull request #10800
- Pod events are now surfaced when pods are stuck in ContainerCreating state with no clear message. Pull request #10690
- Updated to use the new import path for google/cel-go library at cel.dev/cel-go. Pull request #10689
- Extracted shared cleanup-after-resolve helper to eliminate duplication between pipelineref and taskref reconcilers. Pull request #9813
- Optimized step result name regex compilation by hoisting it to a package variable. Pull request #10401
Why it matters
V1.17.0 delivers clearer failure messages and improved observability through enhanced tracing, along with bug fixes for Windows script handling and better error context for task resolution failures. These changes make it easier for users to diagnose and resolve pipeline issues.
Changelog entry
- V1.17.0 release published as 'Egyptian Mau Robocop' with enhanced tracing and failure clarity Release
- Added reconcile.write_intent span attribute to PipelineRun and TaskRun for better observability Pull request #10827
- Fixed Windows script placement to prevent here-string termination when script contains "@ sequences Pull request #10690
- Task resolution failure messages now include task name for improved debugging Pull request #10800
- Pod events are now surfaced when pods are stuck in ContainerCreating state Pull request #10690
- Updated to google/cel-go v0.32.0 with new import path cel.dev/cel-go Pull request #10689
- Refactored shared cleanup-after-resolve logic into common helper Pull request #9813
- Optimized step result name regex by hoisting to package variable Pull request #10401
- Moved shared resolver types to remoteresolution framework package Pull request #9731
- Fixed broken Logs link in developer local-setup documentation Pull request #10396
- Removed unused namespace retrieval code from feature flags tests Pull request #10802
- V1.16 moved to End of Life in release documentation Pull request #10837
Tekton Pipeline v1.17.0 is out with clearer failure messages, sharper traces, and Windows script fixes. Better debugging, better observability.
Tekton Pipeline v1.17.0 'Egyptian Mau Robocop' is now available. This release brings clearer failure diagnostics with reconcile.write_intent span attributes for improved tracing, fixes for Windows script handling when containing special characters, and task resolution errors now include task names. Pod events surface when containers get stuck, making it easier to diagnose infrastructure issues.
Week of September 14, 2026
What shipped
- Resolvers now enqueue only their own ResolutionRequests instead of all requests during leader promotion, reducing unnecessary reconciliation work. Pull request #10548
- TaskRun ReconcileKind spans are now tagged with reason attributes when cancelled or timed out, matching PipelineRun tracing behavior. Pull request #10664
- Documentation clarified that config-tracing and config-observability are separate tracing paths with different configuration keys. Pull request #10626
- Replaced unmaintained gopkg.in/yaml.v3 library with its maintained fork go.yaml.in/yaml/v3. Pull request #10683
- Sigstore dependency updates are now grouped by dependabot to reduce noise when new releases land. Pull request #10761
- Fixed
release_names.gotool bugs in robot name regex and incorrect results from Wikipedia parsing. Pull request #10508 - Corrected controller startup panic log messages to use proper verb formatting. Pull request #10430
- Fixed kind node image digest for Kubernetes v1.33 to use the correct v1.33.4 digest. Pull request #10390
- Updated dead links in feature versioning guide documentation to point to current file locations. Pull request #10394
Why it matters
This week included resolver efficiency improvements, tracing consistency across TaskRun and PipelineRun, maintenance of unmaintained dependencies, and fixes to testing infrastructure and documentation.
Changelog entry
- Resolvers enqueue only their own ResolutionRequests on leader promotion Pull request #10548
- TaskRun ReconcileKind spans tagged with reason on cancel/timeout Pull request #10664
- Documentation clarifies config-tracing and config-observability are separate paths Pull request #10626
- Replaced gopkg.in/yaml.v3 with maintained go.yaml.in/yaml/v3 fork Pull request #10683
- Sigstore dependency updates grouped in dependabot Pull request #10761
- Fixed
release_names.gorobot name regex and parsing bugs Pull request #10508 - Corrected controller startup panic log formatting Pull request #10430
- Fixed kind node image digest for Kubernetes v1.33 Pull request #10390
- Updated dead links in feature versioning guide Pull request #10394
Tekton Pipeline updates: resolver efficiency gains, TaskRun tracing parity with PipelineRun, unmaintained dependency replacement, and documentation fixes.
Tekton Pipeline shipped improvements this week: resolvers now handle requests more efficiently during leader promotion, TaskRun tracing is consistent with PipelineRun across cancellation and timeout scenarios, we replaced an unmaintained YAML library with its maintained fork, and fixed testing infrastructure and documentation issues.