Update tektoncd pipelines to v1.12.2 (main) - autoclosed#3351
Update tektoncd pipelines to v1.12.2 (main) - autoclosed#3351red-hat-konflux[bot] wants to merge 1 commit into
Conversation
|
637429b to
5954a2f
Compare
|
🤖 Finished Review · ✅ Success · Started 3:01 AM UTC · Completed 3:06 AM UTC |
|
Looks good to me Previous runLooks good to me Labels: Dependency update PR modifying Go module files, matching repo convention for Renovate PRs. Previous run (2)Looks good to me Previous run (3)Looks good to me Previous run (4)Looks good to me Previous run (5)Looks good to me Previous run (6)ReviewFindingsMedium
Low
Info
Previous run (7)Looks good to me |
5954a2f to
8ac3e42
Compare
|
🤖 Finished Review · ✅ Success · Started 3:18 AM UTC · Completed 3:25 AM UTC |
Pull request was closed
|
🤖 Finished Retro · ✅ Success · Started 3:00 PM UTC · Completed 3:08 PM UTC |
Retro: PR #3351 — Automated dependency update with review agent issuesWhat happened: PR #3351 was an automated Konflux/MintMaker dependency update bumping The review agent exhibited several known issues on this PR:
No new proposals. All identified improvements are already covered by existing open issues in fullsend-ai/fullsend. This PR serves as additional evidence for the priority of those issues, particularly #1271 (self-triggering), #1453 (medium-severity approval threshold), and #369 (CI-aware review verdicts). |
8ac3e42 to
967763d
Compare
|
🤖 Finished Review · ✅ Success · Started 2:54 AM UTC · Completed 3:00 AM UTC |
ℹ️ 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:
File name: tools/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
|
🤖 Finished Review · ✅ Success · Started 2:08 AM UTC · Completed 2:15 AM UTC |
|
🤖 Finished Retro · ✅ Success · Started 1:46 PM UTC · Completed 1:51 PM UTC |
Retro: PR #3351 — All findings already trackedThis is the 4th retro run on PR #3351, a bot-authored dependency bump ( What happened
Token waste estimateAt least 5 of 6 review runs and 3 of 4 retro runs were redundant. The previous retro (Run 3) estimated ~50% token waste across the workflow. All findings map to existing open issuesPrevious retro runs (Runs 1–3) already identified every actionable improvement and mapped them to existing issues in
No new proposals. This retro run itself is an example of the problem described in #2401 and #2461 — the retro agent should not have been dispatched a 4th time on an autoclosed bot PR where 3 prior retros already completed. |
85e7b79 to
39e13c3
Compare
|
🤖 Review · |
Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
85e7b79 to
72dd83d
Compare
|
🤖 Finished Review · ✅ Success · Started 1:54 AM UTC · Completed 2:00 AM UTC |
|
🤖 Finished Retro · ✅ Success · Started 8:49 PM UTC · Completed 8:54 PM UTC |
Retro: PR #3351 — Bot dependency bump (tektoncd/pipeline v1.12.0→v1.12.2)This was a bot-authored dependency update PR that was closed without merging after 8 days. It had zero human interaction — all 21 comments were from bots. The PR exhibited several known pipeline issues, all of which are already tracked: Problems observed
Estimated waste
ConclusionNo new proposals. All improvement opportunities are covered by existing open issues. The highest-impact fixes would be #1271 (stop review self-triggering), #369 (check CI before approving), and #2461 (skip retro for autoclosed bot PRs). Resolving these three alone would have prevented most of the token waste on this PR. |
This PR contains the following updates:
v1.12.0→v1.12.2Warning
Some dependencies could not be looked up. Check the warning logs for more information.
Release Notes
tektoncd/pipeline (github.com/tektoncd/pipeline)
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
7ec9277toa4477c3in /tekton in the all group (#9993)Docs
Thanks
Thanks to these contributors who contributed to v1.12.1!
Extra shout-out for awesome release notes:
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 these updates again.
To execute skipped test pipelines write comment
/ok-to-test.Documentation
Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.