Skip to content

Update module github.com/tektoncd/pipeline to v1.12.3 (release-v0.7) - #3461

Closed
renovate[bot] wants to merge 1 commit into
release-v0.7from
renovate/release-v0.7-patch-tektoncd-pipelines
Closed

renovate[bot] wants to merge 1 commit into
release-v0.7from
renovate/release-v0.7-patch-tektoncd-pipelines

Conversation

@renovate

@renovate renovate Bot commented Aug 5, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/tektoncd/pipeline v1.12.0 → v1.12.3 age adoption passing confidence

Release Notes

tektoncd/pipeline (github.com/tektoncd/pipeline)

v1.12.3: Tekton Pipeline release v1.12.3 "Exotic Shorthair Elektrobots LTS"

Compare Source

Installation one-liner
kubectl apply -f https://infra.tekton.dev/tekton-releases/pipeline/previous/v1.12.3/release.yaml
Attestation

The Rekor UUID for this release is 108e9186e8c5677ab50b7c76294f1e52835451640e10a8b08939504c87748d0d8ae2c251c3784114

Obtain the attestation:

REKOR_UUID=108e9186e8c5677ab50b7c76294f1e52835451640e10a8b08939504c87748d0d8ae2c251c3784114
rekor-cli get --uuid $REKOR_UUID --format json | jq -r .Attestation | jq .

Verify that all container images in the attestation are in the release file:

RELEASE_FILE=https://infra.tekton.dev/tekton-releases/pipeline/previous/v1.12.3/release.yaml
REKOR_UUID=108e9186e8c5677ab50b7c76294f1e52835451640e10a8b08939504c87748d0d8ae2c251c3784114

# Obtains the list of images with sha from the attestation
REKOR_ATTESTATION_IMAGES=$(rekor-cli get --uuid "$REKOR_UUID" --format json | jq -r .Attestation | jq -r '.subject[]|.name + ":v1.12.3@sha256:" + .digest.sha256')

# Download the release file
curl -L "$RELEASE_FILE" > release.yaml

# For each image in the attestation, match it to the release file
for image in $REKOR_ATTESTATION_IMAGES; do
  printf $image; grep -q $image release.yaml && echo " ===> ok" || echo " ===> no match";
done
Changes
Features
Fixes
  • 🐛 [release-v1.12.x] fix(release): copy vendor tarball into kodata instead of symlink (#​10943)
  • 🐛 [release-v1.12.x] fix: bump plumbing ko image to Go 1.27.3 (#​10940)
Misc
  • 🔨 [release-v1.12.x] build(deps): bump golang.org/x/crypto to 0.55.0 (#​10861)

Update Go security dependencies.

  • 🔨 [release-v1.12.x] bump chainguard-dev/actions/setup-kind from 1.6.40 to 1.6.41 (#​10927)
  • 🔨 [release-v1.12.x] bump chainguard-dev/actions/kind-diag from 1.6.40 to 1.6.41 (#​10925)
  • 🔨 [release-v1.12.x] bump the all group in /tekton with 4 updates (#​10924)
  • 🔨 [release-v1.12.x] bump chainguard-dev/actions/kind-diag from 1.6.39 to 1.6.40 (#​10899)
  • 🔨 [release-v1.12.x] bump actions/upload-artifact from 7.0.1 to 7.0.2 (#​10897)
  • 🔨 [release-v1.12.x] bump the all group in /tekton with 4 updates (#​10894)
  • 🔨 [release-v1.12.x] bump chainguard-dev/actions/kind-diag from 1.6.37 to 1.6.39 (#​10873)
  • 🔨 [release-v1.12.x] bump the all group in /tekton with 4 updates (#​10872)
  • 🔨 [release-v1.12.x] bump chainguard-dev/actions/setup-kind from 1.6.37 to 1.6.40 (#​10871)
  • 🔨 [release-v1.12.x] bump chainguard-dev/actions/setup-kind from 1.6.36 to 1.6.37 (#​10851)
  • 🔨 [release-v1.12.x] bump agilepathway/label-checker from 1.6.98 to 1.6.115 (#​10850)
  • 🔨 [release-v1.12.x] bump chainguard-dev/actions/kind-diag from 1.6.36 to 1.6.37 (#​10849)
  • 🔨 [release-v1.12.x] bump the all group in /tekton with 4 updates (#​10847)
  • 🔨 [release-v1.12.x] bump the kubernetes group with 4 updates (#​10831)
  • 🔨 [release-v1.12.x] bump the kubernetes group in /test/custom-task-ctrls/wait-task-beta with 2 updates (#​10830)
  • 🔨 [release-v1.12.x] bump chainguard-dev/actions/kind-diag from 1.6.35 to 1.6.36 (#​10814)
  • 🔨 [release-v1.12.x] bump chainguard-dev/actions/setup-kind from 1.6.35 to 1.6.36 (#​10812)
  • 🔨 [release-v1.12.x] bump agilepathway/label-checker from 1.6.66 to 1.6.98 (#​10811)
  • 🔨 [release-v1.12.x] bump k8s.io/apimachinery from 0.35.8 to 0.35.9 in the kubernetes group (#​10809)
  • 🔨 [release-v1.12.x] bump k8s.io/apimachinery from 0.35.8 to 0.35.9 in /test/custom-task-ctrls/wait-task-beta in the kubernetes group across 1 directory (#​10806)
  • 🔨 [release-v1.12.x] bump the all group across 1 directory with 4 updates (#​10804)
  • 🔨 [release-v1.12.x] bump the all group in /tekton with 4 updates (#​10784)
  • 🔨 [release-v1.12.x] bump chainguard-dev/actions/setup-kind from 1.6.34 to 1.6.35 (#​10774)
  • 🔨 [release-v1.12.x] bump chainguard-dev/actions/kind-diag from 1.6.34 to 1.6.35 (#​10773)
  • 🔨 [release-v1.12.x] bump agilepathway/label-checker from 1.6.65 to 1.6.66 (#​10770)
  • 🔨 [release-v1.12.x] bump the all group in /tekton with 6 updates (#​10768)
  • 🔨 [release-v1.12.x] bump chainguard-dev/actions/setup-kind from 1.6.32 to 1.6.34 (#​10727)
  • 🔨 [release-v1.12.x] bump chainguard-dev/actions/kind-diag from 1.6.32 to 1.6.34 (#​10726)
  • 🔨 [release-v1.12.x] bump the all group across 1 directory with 4 updates (#​10703)
  • 🔨 [release-v1.12.x] bump google.golang.org/grpc from 1.82.1 to 1.82.2 (#​10675)
  • 🔨 [release-v1.12.x] bump chainguard-dev/actions/kind-diag from 1.6.31 to 1.6.33 (#​10668)
  • 🔨 [release-v1.12.x] bump chainguard-dev/actions/setup-kind from 1.6.31 to 1.6.32 (#​10667)
  • 🔨 [release-v1.12.x] bump the kubernetes group across 1 directory with 4 updates (#​10655)
  • 🔨 [release-v1.12.x] bump the kubernetes group in /test/custom-task-ctrls/wait-task-beta with 2 updates (#​10651)
  • 🔨 [release-v1.12.x] bump k8s.io/apimachinery from 0.35.7 to 0.35.8 in the kubernetes group (#​10648)
  • 🔨 [release-v1.12.x] bump k8s.io/apimachinery from 0.35.7 to 0.35.8 in /test/custom-task-ctrls/wait-task-beta in the kubernetes group (#​10647)
  • 🔨 [release-v1.12.x] bump google.golang.org/protobuf from 1.36.12-0.20260120151049-f2248ac996af to 1.36.12 (#​10623)
  • 🔨 [release-v1.12.x] bump chainguard-dev/actions/kind-diag from 1.6.30 to 1.6.31 (#​10613)
  • 🔨 [release-v1.12.x] bump chainguard-dev/actions/setup-kind from 1.6.30 to 1.6.31 (#​10612)
  • 🔨 [release-v1.12.x] bump chainguard-dev/actions/setup-kind from 1.6.28 to 1.6.30 (#​10580)
  • 🔨 [release-v1.12.x] bump chainguard-dev/actions/kind-diag from 1.6.29 to 1.6.30 (#​10578)
  • 🔨 [release-v1.12.x] bump github.com/google/go-containerregistry from 0.21.8 to 0.21.9 (#​10575)
  • 🔨 [release-v1.12.x] fix: update gRPC dependencies (#​10556)
  • 🔨 [release-v1.12.x] bump github.com/sigstore/sigstore/pkg/signature/kms/azure from 1.10.8 to 1.10.9 (#​10534)
  • 🔨 [release-v1.12.x] bump github.com/sigstore/sigstore/pkg/signature/kms/aws from 1.10.8 to 1.10.9 (#​10533)
  • 🔨 [release-v1.12.x] bump github.com/sigstore/sigstore/pkg/signature/kms/hashivault from 1.10.8 to 1.10.9 (#​10525)
  • 🔨 [release-v1.12.x] bump github.com/sigstore/sigstore from 1.10.8 to 1.10.9 (#​10521)
  • 🔨 [release-v1.12.x] bump github.com/google/go-containerregistry from 0.21.7 to 0.21.8 (#​10520)
Docs
Thanks

Thanks to these contributors who contributed to v1.12.3!

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
kubectl apply -f https://infra.tekton.dev/tekton-releases/pipeline/previous/v1.12.2/release.yaml
Attestation

The Rekor UUID for this release is cb0a4d44223cf8dd164d8eec84c25d204f7a37a023c2d28f1f8dcde79ca3c187

Obtain the attestation:

REKOR_UUID=cb0a4d44223cf8dd164d8eec84c25d204f7a37a023c2d28f1f8dcde79ca3c187
rekor-cli get --uuid $REKOR_UUID --format json | jq -r .Attestation | jq .

Verify that all container images in the attestation are in the release file:

RELEASE_FILE=https://infra.tekton.dev/tekton-releases/pipeline/previous/v1.12.2/release.yaml
REKOR_UUID=cb0a4d44223cf8dd164d8eec84c25d204f7a37a023c2d28f1f8dcde79ca3c187

# Obtains the list of images with sha from the attestation
REKOR_ATTESTATION_IMAGES=$(rekor-cli get --uuid "$REKOR_UUID" --format json | jq -r .Attestation | jq -r '.subject[]|.name + ":v1.12.2@sha256:" + .digest.sha256')

# Download the release file
curl -L "$RELEASE_FILE" > release.yaml

# For each image in the attestation, match it to the release file
for image in $REKOR_ATTESTATION_IMAGES; do
  printf $image; grep -q $image release.yaml && echo " ===> ok" || echo " ===> no match";
done
Changes
Features
Fixes
Misc
  • 🔨 build(deps): bump k8s.io/client-go from 0.35.5 to 0.35.6 (#​10289)
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
kubectl apply -f https://infra.tekton.dev/tekton-releases/pipeline/previous/v1.12.1/release.yaml
Attestation

The Rekor UUID for this release is 108e9186e8c5677a9cfc575e256441da4223e4767ebb840a62e4b5ad18ed6219842a81686a4a8586

Obtain the attestation:

REKOR_UUID=108e9186e8c5677a9cfc575e256441da4223e4767ebb840a62e4b5ad18ed6219842a81686a4a8586
rekor-cli get --uuid $REKOR_UUID --format json | jq -r .Attestation | jq .

Verify that all container images in the attestation are in the release file:

RELEASE_FILE=https://infra.tekton.dev/tekton-releases/pipeline/previous/v1.12.1/release.yaml
REKOR_UUID=108e9186e8c5677a9cfc575e256441da4223e4767ebb840a62e4b5ad18ed6219842a81686a4a8586

# Obtains the list of images with sha from the attestation
REKOR_ATTESTATION_IMAGES=$(rekor-cli get --uuid "$REKOR_UUID" --format json | jq -r .Attestation | jq -r '.subject[]|.name + ":v1.12.1@sha256:" + .digest.sha256')

# Download the release file
curl -L "$RELEASE_FILE" > release.yaml

# For each image in the attestation, match it to the release file
for image in $REKOR_ATTESTATION_IMAGES; do
  printf $image; grep -q $image release.yaml && echo " ===> ok" || echo " ===> no match";
done
Changes
Features
Fixes
  • 🐛 [cherry-pick: release-v1.12.x] fix(resolvers): Allow ResolutionRequests to resolve all Tekton kinds (#​10252)

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.

  • 🐛 [cherry-pick: release-v1.12.x] fix: TaskRun stuck in Running when init container is OOMKilled with enableKubernetesSidecar (#​10186)

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.

  • 🐛 [cherry-pick: release-v1.12.x] Fix cross-arch platform command lookup in entrypoint (#​10164)

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.

  • 🐛 [cherry-pick: release-v1.12.x] fix: truncate affinity assistant volume names to 63 characters (#​10137)

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.

  • 🐛 [cherry-pick: release-v1.12.x] fix(pipelinerun): use generateName for anonymous pipeline label (#​10079)

Previously, TaskRuns' tekton.dev/pipeline label for anonymous Pipelines would use their PipelineRun's name in their tekton.dev/pipeline label and pipeline metrics tag. After this change, TaskRun and PipelineRun which are created from anonymous Pipelines now reference a sanitized metadata.generateName, when present, for the label tekton.dev/pipeline. Similarly, these TaskRruns and PipelineRuns will populate their respective metrics' pipeline tag with the sanitized generateName instead of using anonymous.

  • 🐛 [release-v1.12.x] Fix gen-crd-api-reference-docs require to use fetchable version (#​10001)

ix gen-crd-api-reference-docs go.mod require to use a fetchable upstream version, fixing module resolution failures for downstream consumers.

  • 🐛 [cherry-pick: release-v1.12.x] fix(resolvers): validate data is Tekton object in resolver framework (#​9963)

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.

  • 🐛 [release-v1.12.x] fix: replace symlinks with subpath params and fix Rekor UUID in release pipeline (#​10216)
  • 🐛 [cherry-pick: release-v1.12.x] Fix PipelineRun premature failure when TaskRun recovers after pod eviction (#​10161)
Misc
  • 🔨 build(deps): bump the all group in /tekton with 4 updates (#​10265)
  • 🔨 build(deps): bump the all group in /tekton with 4 updates (#​10234)
  • 🔨 build(deps): bump chainguard-dev/actions from 1.6.21 to 1.6.22 (#​10229)
  • 🔨 build(deps): bump actions/checkout from 6.0.2 to 6.0.3 (#​10200)
  • 🔨 build(deps): bump chainguard-dev/actions from 1.6.19 to 1.6.21 (#​10199)
  • 🔨 build(deps): bump the all group in /tekton with 4 updates (#​10194)
  • 🔨 build(deps): bump github.com/sigstore/sigstore from 1.10.6 to 1.10.8 (#​10168)
  • 🔨 build(deps): bump github.com/sigstore/sigstore/pkg/signature/kms/azure from 1.10.6 to 1.10.8 (#​10150)
  • 🔨 build(deps): bump github.com/sigstore/sigstore/pkg/signature/kms/hashivault from 1.10.6 to 1.10.8 (#​10149)
  • 🔨 build(deps): bump github.com/spiffe/spire-api-sdk from 1.14.6 to 1.14.7 (#​10148)
  • 🔨 build(deps): bump github.com/sigstore/sigstore/pkg/signature/kms/gcp from 1.10.6 to 1.10.8 (#​10147)
  • 🔨 build(deps): bump github.com/sigstore/sigstore/pkg/signature/kms/aws from 1.10.6 to 1.10.8 (#​10146)
  • 🔨 build(deps): bump the all group in /tekton with 4 updates (#​10130)
  • 🔨 build(deps): bump golangci/golangci-lint-action from 9.2.0 to 9.2.1 (#​10129)
  • 🔨 build(deps): bump the all group across 1 directory with 4 updates (#​10094)
  • 🔨 build(deps): bump step-security/harden-runner from 2.19.2 to 2.19.4 (#​10093)
  • 🔨 build(deps): bump zizmorcore/zizmor-action from 0.5.3 to 0.5.6 (#​10092)
  • 🔨 build(deps): bump github/codeql-action from 4.35.4 to 4.35.5 (#​10091)
  • 🔨 build(deps): bump github.com/google/go-containerregistry from 0.21.5 to 0.21.6 (#​10070)
  • 🔨 build(deps): bump github.com/sigstore/sigstore/pkg/signature/kms/gcp from 1.10.5 to 1.10.6 (#​10065)
  • 🔨 build(deps): bump github.com/sigstore/sigstore/pkg/signature/kms/azure from 1.10.5 to 1.10.6 (#​10064)
  • 🔨 build(deps): bump github.com/sigstore/sigstore from 1.10.5 to 1.10.6 (#​10063)
  • 🔨 build(deps): bump github.com/sigstore/sigstore/pkg/signature/kms/hashivault from 1.10.5 to 1.10.6 (#​10062)
  • 🔨 build(deps): bump github.com/sigstore/sigstore/pkg/signature/kms/aws from 1.10.5 to 1.10.6 (#​10061)
  • 🔨 build(deps): bump step-security/harden-runner from 2.19.1 to 2.19.2 (#​10046)
  • 🔨 build(deps): bump the all group in /tekton with 4 updates (#​10041)
  • 🔨 build(deps): bump k8s.io/apiextensions-apiserver from 0.35.4 to 0.35.5 (#​10034)
  • 🔨 build(deps): bump k8s.io/client-go from 0.35.4 to 0.35.5 in /test/custom-task-ctrls/wait-task-beta (#​10023)
  • 🔨 build(deps): bump github.com/jenkins-x/go-scm from 1.15.21 to 1.15.22 (#​10018)
  • 🔨 build(deps): bump github.com/google/cel-go from 0.28.0 to 0.28.1 (#​10017)
  • 🔨 build(deps): bump github/codeql-action from 4.35.2 to 4.35.4 (#​9994)
  • 🔨 build(deps): bump chainguard/go from 7ec9277 to a4477c3 in /tekton in the all group (#​9993)
  • 🔨 build(deps): bump chainguard-dev/actions from 1.6.17 to 1.6.19 (#​9983)
  • 🔨 build(deps): bump step-security/harden-runner from 2.19.0 to 2.19.1 (#​9981)
  • 🔨 build(deps): bump the all group in /tekton with 4 updates (#​9976)
Docs
Thanks

Thanks to these contributors who contributed to v1.12.1!

Extra shout-out for awesome release notes:


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM (* 0-3 * * *)
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate

renovate Bot commented Aug 5, 2026 •

Copy link
Copy Markdown
Contributor Author

ℹ️ Artifact update notice

File name: acceptance/go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 5 additional dependencies were updated
  • The go directive was updated for compatibility reasons

Due to Go's usage of Minimal Version Selection (MVS), these packages have been updated to the minimum version available, so will still abide by minimumReleaseAge=5 days

Details:

Package Change
go 1.26.7 -> 1.27.3
github.com/google/go-containerregistry v0.21.7 -> v0.21.9
github.com/sigstore/sigstore v1.10.8 -> v1.10.9
github.com/coreos/go-oidc/v3 v3.19.0 -> v3.20.0
github.com/google/cel-go v0.28.0 -> v0.28.1
k8s.io/apiextensions-apiserver v0.35.4 -> v0.35.9
File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 6 additional dependencies were updated
  • The go directive was updated for compatibility reasons

Due to Go's usage of Minimal Version Selection (MVS), these packages have been updated to the minimum version available, so will still abide by minimumReleaseAge=5 days

Details:

Package Change
go 1.26.7 -> 1.27.3
github.com/google/go-containerregistry v0.21.7 -> v0.21.9
github.com/sigstore/sigstore v1.10.8 -> v1.10.9
k8s.io/apiextensions-apiserver v0.35.4 -> v0.35.9
github.com/coreos/go-oidc/v3 v3.19.0 -> v3.20.0
github.com/golang/snappy v0.0.4 -> v1.0.0
github.com/google/cel-go v0.28.0 -> v0.28.1

@fullsend-ai-review

fullsend-ai-review Bot commented Aug 5, 2026 •

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 2:24 AM UTC · Completed 2:29 AM UTC
Commit: 87c4a29 · View workflow run →

@fullsend-ai-review

fullsend-ai-review Bot commented Aug 5, 2026 •

Copy link
Copy Markdown

Looks good to me

Previous run

<!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJhY3Rpb24iOiJhcHByb3ZlIiwiZmluZGluZ3MiOltdfQ== -->

Looks good to me

Previous run (2)

<!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJhY3Rpb24iOiJhcHByb3ZlIiwiZmluZGluZ3MiOltdfQ== -->

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)

Looks good to me

Previous run (7)

Review

Renovate patch bump for github.com/tektoncd/pipeline v1.12.0 -> v1.12.2 on the release-v0.7 branch, with same-graph transitive updates to google/cel-go (v0.28.0 -> v0.28.1), k8s.io/apiextensions-apiserver and k8s.io/apiserver (both v0.35.4 -> v0.35.5). Diff is limited to the four dependency manifests (go.mod / go.sum in the root and acceptance/ modules); no source, test, workflow, or governance files touched. Risk assessment: moderate (2/5).

Findings

Info

  • [scope-authorization-implicit] N/A — Authorization inferred from the mechanical nature of the change (value-only / patch-level dependency bump generated by Renovate). No architectural review required.
  • [provenance-warning] N/A — Prior review context was discarded: the prior review comment failed provenance validation (PRIOR_REVIEW_PROVENANCE=unverifiable-wrong-app). This run treats all findings as first-time assessments; severity anchoring was skipped.
Previous run (8)

Review

Findings

Info

  • [scope-authorization-implicit] — Authorization inferred from mechanical nature of change (value-only Renovate patch dependency bump of github.com/tektoncd/pipeline v1.12.0 → v1.12.2 on release-v0.7, with transitive bumps to google/cel-go, k8s.io/apiextensions-apiserver, and k8s.io/apiserver). No architectural review required.
  • [provenance-warning] — Prior review context discarded: provenance validation failed (unverifiable-wrong-app). This review treats all findings as first-time assessments; severity anchoring was skipped for this run.
Previous run (9)

Looks good to me

Previous run (10)

Looks good to me

Previous run (11)

Looks good to me

Previous run (12)

Looks good to me

Previous run (13)

Looks good to me


Labels: Dependency version bump in Go module files

fullsend-ai-review[bot]

This comment was marked as outdated.

@fullsend-ai-review fullsend-ai-review Bot added ready-for-merge All reviewers approved — ready to merge dependencies Pull requests that update a dependency file labels Aug 5, 2026
@codecov

codecov Bot commented Aug 5, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

Flag Coverage Δ
generative 69.55% <ø> (ø)
integration 69.55% <ø> (ø)
unit 69.55% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@renovate
renovate Bot force-pushed the renovate/release-v0.7-patch-tektoncd-pipelines branch from 398b81a to ce8c9d2 Compare August 10, 2026 15:21
@fullsend-ai-review

fullsend-ai-review Bot commented Aug 10, 2026 •

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 3:23 PM UTC · Completed 3:29 PM UTC

Commit: 87c4a29 · View workflow run →

fullsend-ai-review[bot]

This comment was marked as outdated.

@renovate
renovate Bot force-pushed the renovate/release-v0.7-patch-tektoncd-pipelines branch from ce8c9d2 to efa5626 Compare August 10, 2026 17:04
@fullsend-ai-review

fullsend-ai-review Bot commented Aug 10, 2026 •

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 5:05 PM UTC · Completed 5:10 PM UTC

Commit: 87c4a29 · View workflow run →

fullsend-ai-review[bot]

This comment was marked as outdated.

@renovate
renovate Bot force-pushed the renovate/release-v0.7-patch-tektoncd-pipelines branch from efa5626 to 4ad15d0 Compare August 14, 2026 16:32
@fullsend-ai-review

fullsend-ai-review Bot commented Aug 14, 2026 •

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 4:33 PM UTC · Completed 4:38 PM UTC

Commit: 87c4a29 · View workflow run →

fullsend-ai-review[bot]

This comment was marked as outdated.

@fullsend-ai-review

fullsend-ai-review Bot commented Aug 18, 2026 •

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 6:39 PM UTC · Completed 6:45 PM UTC

Commit: 87c4a29 · View workflow run →

fullsend-ai-review[bot]

This comment was marked as outdated.

@renovate
renovate Bot force-pushed the renovate/release-v0.7-patch-tektoncd-pipelines branch 3 times, most recently from fb437fa to 8b60bf8 Compare September 10, 2026 02:03
@coderabbitai

coderabbitai Bot commented Sep 10, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Enterprise
  • Run ID: 2f802a1e-9793-423d-9b5b-bedd31a6938b

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Comment @coderabbitai help to get the list of available commands.

@github-actions github-actions Bot removed the size: M label Sep 10, 2026
fullsend-ai-review[bot]

This comment was marked as outdated.

@fullsend-ai-review
fullsend-ai-review Bot dismissed their stale review October 26, 2026 09:51

Superseded by updated review

@fullsend-ai-review fullsend-ai-review Bot added the ready-for-merge All reviewers approved — ready to merge label Oct 26, 2026
@renovate
renovate Bot force-pushed the renovate/release-v0.7-patch-tektoncd-pipelines branch from 8108e8e to bdbeb30 Compare October 28, 2026 18:23
@renovate renovate Bot changed the title Update module github.com/tektoncd/pipeline to v1.12.2 (release-v0.7) Update module github.com/tektoncd/pipeline to v1.12.3 (release-v0.7) Oct 28, 2026
@github-actions github-actions Bot added size: L and removed size: S labels Oct 28, 2026
@fullsend-ai-review

fullsend-ai-review Bot commented Oct 28, 2026 •

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 6:25 PM UTC · Completed 6:37 PM UTC

Commit: bdbeb30 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $2.79

@fullsend-ai-review fullsend-ai-review Bot removed the ready-for-merge All reviewers approved — ready to merge label Oct 28, 2026
fullsend-ai-review[bot]

This comment was marked as outdated.

@fullsend-ai-review
fullsend-ai-review Bot dismissed their stale review October 28, 2026 18:37

Superseded by updated review

@fullsend-ai-review fullsend-ai-review Bot added the ready-for-merge All reviewers approved — ready to merge label Oct 28, 2026
@renovate
renovate Bot force-pushed the renovate/release-v0.7-patch-tektoncd-pipelines branch from bdbeb30 to 4f1c0b7 Compare October 28, 2026 21:09
@fullsend-ai-review

fullsend-ai-review Bot commented Oct 28, 2026 •

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 9:11 PM UTC · Completed 9:20 PM UTC

Commit: 4f1c0b7 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $1.95

@fullsend-ai-review fullsend-ai-review Bot removed the ready-for-merge All reviewers approved — ready to merge label Oct 28, 2026
@fullsend-ai-review
fullsend-ai-review Bot dismissed their stale review October 28, 2026 21:20

Superseded by updated review

@fullsend-ai-review fullsend-ai-review Bot added the ready-for-merge All reviewers approved — ready to merge label Oct 28, 2026
auto-merge was automatically disabled October 29, 2026 11:59

Pull request was closed

@dheerajodha dheerajodha reopened this Oct 29, 2026
@fullsend-ai-retro

fullsend-ai-retro Bot commented Oct 29, 2026 •

Copy link
Copy Markdown

🤖 Finished Retro · ✅ Success · Started 12:01 PM UTC · Completed 12:12 PM UTC

Commit: 4f1c0b7 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $3.76

@dheerajodha

Copy link
Copy Markdown
Contributor

As I said to my ex "See you never".
Because we're decommissioning the v0.7 release branch btw (ref: EC-2344)

@fullsend-ai-retro

Copy link
Copy Markdown

Retro: PR #3461 — Renovate dependency bump with 14 redundant review runs

PR #3461 is a Renovate bot dependency bump (github.com/tektoncd/pipeline v1.12.0 → v1.12.3) on the release-v0.7 branch. It has been open for ~3 months (since Aug 5) and has never received a human review or comment.

What happened

The review agent ran 14 times between Aug 5 and Oct 28, each time approving with zero findings. Every run took 5–12 minutes and cost $1.55–$4.10, totaling an estimated ~$20 in review agent compute. Key waste patterns:

  • Same-commit re-reviews: Commit 87c4a29 was reviewed 5 separate times (Aug 5–18) and cd01138 was reviewed 3 times (Sep 10–11), each producing the identical verdict.
  • Rebase-triggered re-reviews: Renovate rebased the branch 6 times, each force-push triggering a pull_request_target: synchronize event that dispatched a full new review. The effective diff against the base branch was semantically unchanged across all rebases.
  • No circuit breaker: After 14 approvals with no findings and no human engagement, the system continued dispatching full-cost reviews on every push.

Systemic pattern

This is not a one-off. Other long-lived Renovate PRs in this repo show the same pattern:

  • PR #3605 (containerd update, open since Oct 13): 13 reviews with 13 force pushes
  • PR #3607 (cel-go update, open since Oct 13): 6 reviews with 3 force pushes

Short-lived PRs that merge quickly (e.g., #3651, merged in 2.5 hrs) get only 1–3 reviews. The waste scales with how long a Renovate PR stays open — and release-branch PRs tend to stay open longer.

This retro run itself is evidence of the waste: running a full retro analysis on a trivial dependency bump PR with no meaningful code changes adds cost without value (covered by fullsend-ai/fullsend#4006 and related issues).

No new proposals — existing issues cover this comprehensively

This is a well-documented systemic problem. The searches found 15+ open issues across fullsend-ai/fullsend and fullsend-ai/agents covering every angle of this PR's waste:

This PR provides additional evidence for those issues: 14 reviews and ~$20 in cost on a single trivial dependency bump, with the same commit reviewed up to 5 times. The fullsend-ai/agents#323 and fullsend-ai/fullsend#4401 issues remain the highest-impact fixes — implementing either would have eliminated most of the waste observed here.

@renovate

renovate Bot commented Oct 29, 2026

Copy link
Copy Markdown
Contributor Author

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (v1.12.3). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate
renovate Bot deleted the renovate/release-v0.7-patch-tektoncd-pipelines branch October 29, 2026 12:13
@fullsend-ai-retro

fullsend-ai-retro Bot commented Oct 29, 2026 •

Copy link
Copy Markdown

🤖 Finished Retro · ✅ Success · Started 12:14 PM UTC · Completed 12:21 PM UTC

Commit: 4f1c0b7 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $2.92

@fullsend-ai-retro

Copy link
Copy Markdown

Retro: PR #3461 — Duplicate retro on already-analyzed Renovate dependency bump

PR #3461 is a Renovate bot dependency bump (github.com/tektoncd/pipeline to v1.12.3) on the now-decommissioned release-v0.7 branch. It was open for ~3 months (Aug 5 – Oct 29), received 14 review agent runs (all approvals, zero findings, ~$20 total cost), and was closed without merging.

A previous retro (workflow run 40869661102) already ran on this PR and comprehensively identified all waste patterns: same-commit re-reviews, rebase-triggered re-reviews, and the absence of a circuit breaker. It found 15+ existing open issues across fullsend-ai/fullsend and fullsend-ai/agents covering every dimension and correctly filed zero new proposals.

This second retro (run 40871279120) was dispatched ~12 minutes after the first completed — itself an instance of the duplicate retro dispatch pattern.

New evidence for existing issues

  • fullsend-ai/fullsend#2401 (Deduplicate retro runs): Two retro dispatches within 12 minutes on the same closed PR with no intervening changes. The second run is pure waste ($4).
  • fullsend-ai/fullsend#7835 (Retro concurrency group): A concurrency group keyed on PR number would have cancelled this second dispatch.
  • fullsend-ai/fullsend#4006 (Skip retro for automated dependency PRs): This Renovate PR with only go.mod/go.sum changes generated two retro runs finding nothing actionable either time.
  • fullsend-ai/fullsend#2587 (Review dispatch cap): 14 review runs on a single dependency bump PR with no human engagement demonstrates the need for a hard cap.
  • fullsend-ai/fullsend#4401 (Rebase-only skip): Multiple re-reviews triggered by Renovate rebases with no effective diff change.
  • fullsend-ai/agents#323 (Same-commit dedup): Same commit SHA reviewed up to 5 times.

No new proposals

All improvement opportunities are covered by existing open issues. The previous retro's analysis was thorough and correct. Filing additional proposals would create duplicates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file ready-for-merge All reviewers approved — ready to merge release-v0.7 renovate risk/moderate PR risk: moderate size: L

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant