Update module github.com/tektoncd/pipeline to v1.14.1 (main)#3432
Open
renovate[bot] wants to merge 1 commit into
Open
Update module github.com/tektoncd/pipeline to v1.14.1 (main)#3432renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
Contributor
Author
ℹ️ Artifact update noticeFile name: acceptance/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
File name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
|
🤖 Finished Review · ✅ Success · Started 2:02 AM UTC · Completed 2:10 AM UTC |
|
Looks good to me Labels: PR is a Go dependency update (go.mod/go.sum only) |
![fullsend-ai-review[bot]](https://avatars.githubusercontent.com/in/3478501?s=60&v=4){kind=small}
fullsend-ai-review
Bot
added
ready-for-merge
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.12.0→v1.14.1Release Notes
tektoncd/pipeline (github.com/tektoncd/pipeline)
v1.14.1: Tekton Pipeline release v1.14.1 "Chartreux Cait Sith"Compare Source
Tekton Pipeline release v1.14.1 ""Chartreux Cait Sith""
-Docs @ v1.14.1
-Examples @ v1.14.1
Installation one-liner
Attestation
The Rekor UUID for this release is
108e9186e8c5677a5b65d09f2d5a25a1c1cc499f6dd152f80348422ff8fbe46a84ad47c0eba03a8aObtain the attestation:
Verify that all container images in the attestation are in the release file:
Changes
Features
Fixes
Fix pipeline validation rejecting $(results.*) variable references in pipeline task parameters
Misc
Docs
Thanks
Thanks to these contributors who contributed to v1.14.1!
Extra shout-out for awesome release notes:
v1.14.0: Tekton Pipeline release v1.14.0 "Chartreux Cait Sith"Compare Source
🎉 🐱 Pipelines in Pipelines by ref, leaner controllers & sturdier reconcilers 🤖 🎉
Installation one-liner
Attestation
The Rekor UUID for this release is
108e9186e8c5677aa9d0ba4d268af76a6ffef1ad43d8ad6966ceef7663859284b3163eddafaa94abObtain the attestation:
Verify that all container images in the attestation are in the release file:
Changes
Features
Errors creating a Pod or updating a TaskRun are now recorded on the TaskRun reconciler trace spans, so failures are visible in distributed traces.
Errors creating a child TaskRun or CustomRun are now recorded on the PipelineRun reconciler trace spans, so failures are visible in distributed traces.
Add tracing spans to the PipelineRun cancel and timeout code paths, so cancellation and timeout of a run and its children are visible in distributed traces.
Inject traceID and spanID into structured log output for TaskRun and PipelineRun reconcilers when tracing is enabled, enabling log-to-trace correlation in observability platforms.
[ENHANCEMENT] notifications: add OTel tracing spans to CustomRun reconciler (ReconcileKind, ReconcileRunObject, EmitCloudEvents)
Fixes
Bump Go to 1.26.4 for CVE remediation.
Fixed a controller crash ("concurrent map writes") that could occur while resolving multiple StepAction references when the Task uses an object parameter with both a default and a TaskRun-provided value.
Fix Rekor EntryID extraction in release pipeline to publish correct 80-char EntryIDs instead of truncated 64-char hashes.
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.
Fix entrypoint command lookup when controller and worker nodes run on different CPU architectures (e.g., ARM controller with AMD64 workloads). The controller's CPU variant was leaking into TEKTON_PLATFORM_COMMANDS keys via platforms.NewPlatform(), causing "could not find command for platform" errors on worker nodes of a different architecture.
Pipeline validation now rejects invalid variable references like
$(new_image)in task parameters with a clear error message, instead of silently accepting them or crashing the webhook. Users who accidentally use$()(Tekton variable syntax) instead of${}(shell variable syntax) in Pipeline param values will now receive a helpful validation error indicating the valid prefixes (params, tasks, finally, context, workspaces).Fix validation error when a Task uses both spec.results and spec.steps[].results in the same step script
Fix incorrect OCI image labels (title, url, description) inherited from base image in published pipeline images
Misc
Docs
Thanks
Thanks to these contributors who contributed to v1.14.0!
Extra shout-out for awesome release notes:
v1.13.1: Tekton Pipeline release v1.13.1 "Pixie-bob Project 2501"Compare Source
-Docs @ v1.13.1
-Examples @ v1.13.1
Installation one-liner
Attestation
The Rekor UUID for this release is
7e8b48508ad51cc71249bf7da0e6fbd511ef626cbbd1ced5beb74f2cbc3750d6Obtain the attestation:
Verify that all container images in the attestation are in the release file:
Changes
Features
Fixes
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.
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.
Fixed spurious step log warnings about parsing existing termination messages when termination message compression is disabled.
Action required: Tekton no longer applies default resource requests or limits to internal containers (
prepare,place-scripts,working-dir-initializer, andsidecar-tekton-log-results) whendefault-container-resource-requirementsis unset. Clusters that rely on these defaults for ResourceQuota compatibility must configure explicit internal container resources in theconfig-defaultsConfigMap.Misc
Docs
Thanks
Thanks to these contributors who contributed to v1.13.1!
Extra shout-out for awesome release notes:
v1.13.0: Tekton Pipeline release v1.13.0 "Pixie-bob Project 2501"Compare Source
🎉 Squeezing more out of every pipeline: compressed results & timeout fixes 🎉
Installation one-liner
Attestation
The Rekor UUID for this release is
108e9186e8c5677accee6fa1065e378221444c30175152ffea8d8c6f5c0d7d5890d31edeaa3ac031Obtain the attestation:
Verify that all container images in the attestation are in the release file:
Upgrade Notices
Tekton Resolvers are now only permitted to resolve StepActions, Tasks, and Pipelines. Custom resolvers or ResolutionRequests which use the Resolver API for other object types will no longer function.
Changes
Features
Added OpenTelemetry tracing to the TaskRun notification reconciliation path.
Spans now cover ReconcileKind, ReconcileRunObject, and EmitCloudEvents,
enabling operators to trace CloudEvent delivery latency end-to-end.
The formats field in config-events is now active. The default value is
tektonv1, which preserves existing behaviour. Setting an invalid or
unrecognised format value logs a warning and suppresses event emission
for that format.
Added optional termination message compression (alpha feature flag
enable-termination-message-compression) that uses flate compression to fit
approximately 5.7x more results in the 4KB Kubernetes termination message limit.
The parser auto-detects compressed messages for full backward compatibility.
Zero new dependencies — uses Go stdlib only.
Fixes
Reduced default log verbosity in the TaskRun notification path introduced
by #9912. Identifier logs (TaskRun name/namespace) are now emitted at debug
level only. Added documentation warning that exported traces may include
Kubernetes resource identifiers and that trace backends should be treated
as trusted observability systems.
Skip re-resolution of ResolutionRequests when Status.Data is already present, preventing hundreds of redundant reconciliations under load.
Preserve previous TaskRun condition context (reason + message) when a TaskRun is cancelled or times out due to a PipelineRun timeout, so diagnostic information like ExceededResourceQuota is no longer lost.
ix gen-crd-api-reference-docs go.mod require to use a fetchable upstream version (v0.3.0), fixing module resolution failures for downstream consumers.
Previously, TaskRuns'
tekton.dev/pipelinelabel for anonymous Pipelines would use their PipelineRun's name in theirtekton.dev/pipelinelabel andpipelinemetrics tag. After this change, TaskRun and PipelineRun which are created from anonymous Pipelines now reference a sanitizedmetadata.generateName, when present, for the labeltekton.dev/pipeline. Similarly, these TaskRruns and PipelineRuns will populate their respective metrics'pipelinetag with the sanitized generateName instead of usinganonymous.Affinity assistant StatefulSet no longer fails when workspace volumeClaimTemplate names exceed 63 characters. Long volume names are now automatically truncated with a hash suffix to stay within the Kubernetes limit.
Fix a bug where finally tasks were not executed when the tasks timeout
(either explicit via
timeouts.tasksor calculated astimeouts.pipeline - timeouts.finally) was exceeded. The PipelineRun was immediately marked asFailed without giving finally tasks a chance to run. Now the pipeline
continues running with reason
PipelineRunTimeoutRunningFinallyuntilfinally tasks complete.
Resolver cache now respects per-resolver TTL values set in individual
resolver ConfigMaps (e.g., bundleresolver-config, git-resolver-config),
instead of always using the global resolver-cache-config TTL.
Fixes a bug which lets Tekton Resolvers resolve non-tekton objects and arbitrary data. After this change, resolving a non-tekton object causes the ResolutionRequest to fail.
Action Required: Tekton Resolvers are now only permitted to resolve StepActions, Tasks, and Pipelines. Custom resolvers or ResolutionRequest which use the Resolver API for other object types will no longer function.
Misc
7ec9277toa4477c3in /tekton in the all group (#9991)Docs
Thanks
Thanks to these contributors who contributed to v1.13.0!
Extra shout-out for awesome release notes:
v1.12.2: Tekton Pipeline release v1.12.2 "Exotic Shorthair Elektrobots LTS"Compare Source
-Docs @ v1.12.2
-Examples @ v1.12.2
Installation one-liner
Attestation
The Rekor UUID for this release is
cb0a4d44223cf8dd164d8eec84c25d204f7a37a023c2d28f1f8dcde79ca3c187Obtain the attestation:
Verify that all container images in the attestation are in the release file:
Changes
Features
Fixes
Misc
Docs
Thanks
Thanks to these contributors who contributed to v1.12.2!
Extra shout-out for awesome release notes:
v1.12.1: Tekton Pipeline release v1.12.1 "Exotic Shorthair Elektrobots LTS"Compare Source
-Docs @ v1.12.1
-Examples @ v1.12.1
Installation one-liner
Attestation
The Rekor UUID for this release is
108e9186e8c5677a9cfc575e256441da4223e4767ebb840a62e4b5ad18ed6219842a81686a4a8586Obtain the attestation:
Verify that all container images in the attestation are in the release file:
Changes
Features
Fixes
efore this change, ResolutionRequests could only resolve Pipelines, Tasks, and StepActions. After this change, ResolutionRequests can resolve PipelineRuns, Pipelines, TaskRuns, Tasks, Runs, CustomRuns, and StepActions.
ix: 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.
ix entrypoint command lookup when controller and worker nodes run on different CPU architectures (e.g., ARM controller with AMD64 workloads). The controller's CPU variant was leaking into TEKTON_PLATFORM_COMMANDS keys via platforms.NewPlatform(), causing "could not find command for platform" errors on worker nodes of a different architecture.
ffinity assistant StatefulSet no longer fails when workspace volumeClaimTemplate names exceed 63 characters. Long volume names are now automatically truncated with a hash suffix to stay within the Kubernetes limit.
Previously, TaskRuns'
tekton.dev/pipelinelabel for anonymous Pipelines would use their PipelineRun's name in theirtekton.dev/pipelinelabel andpipelinemetrics tag. After this change, TaskRun and PipelineRun which are created from anonymous Pipelines now reference a sanitizedmetadata.generateName, when present, for the labeltekton.dev/pipeline. Similarly, these TaskRruns and PipelineRuns will populate their respective metrics'pipelinetag with the sanitized generateName instead of usinganonymous.ix gen-crd-api-reference-docs go.mod require to use a fetchable upstream version, fixing module resolution failures for downstream consumers.
Fixes a bug which lets Tekton Resolvers resolve non-tekton objects and arbitrary data. After this change, resolving a non-tekton object causes the ResolutionRequest to fail.
Action Required: Tekton Resolvers are now only permitted to resolve StepActions, Tasks, and Pipelines. Custom resolvers or ResolutionRequest which use the Resolver API for other object types will no longer function.
Misc
Configuration
📅 Schedule: (UTC)
* 0-3 * * *)🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.