[release-v0.78.x] bump github.com/tektoncd/pruner from 0.3.5 to 0.3.6

[dependabot]

Bumps github.com/tektoncd/pruner from 0.3.5 to 0.3.6.

Release notes

Sourced from github.com/tektoncd/pruner's releases.

Tekton Pruner release v0.3.6 "Release v0.3.6"

-Docs @ v0.3.6 -Examples @ v0.3.6

Installation one-liner

kubectl apply -f https://infra.tekton.dev/tekton-releases/pruner/previous/v0.3.6/release.yaml

Attestation

The Rekor UUID for this release is 108e9186e8c5677a21c9dfcf72485192d27192d19fa5ddcee39d178f940b0dfec3dc5965c0afadf4

Obtain the attestation:

REKOR_UUID=108e9186e8c5677a21c9dfcf72485192d27192d19fa5ddcee39d178f940b0dfec3dc5965c0afadf4
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/pruner/previous/v0.3.6/release.yaml
REKOR_UUID=108e9186e8c5677a21c9dfcf72485192d27192d19fa5ddcee39d178f940b0dfec3dc5965c0afadf4
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 + ":v0.3.6@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

... (truncated)

Commits

• 3892309 fix: add e2e build tag to skip e2e tests in release pipeline
• 2b54ebd fix(webhook): allow operator-managed global ConfigMap deletion
• 0715ff1 fix(cve): bump OTel SDK to v1.43.0 to fix GHSA-9h8m-3fm2-qjrq and GHSA-hfvc-g...
• a32f9cb fix(security): patch three OpenTelemetry Go CVEs on release-v0.3.x
• 18903cd (CVE-2026-40938) PR to fix update pipelines to v1.6.2
• 3a1779e chore: fix-cves
• b348adf ci: add unified CI summary job
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[pratap0007]

/lgtm
/approve

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: anithapriyanatarajan, pratap0007

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [anithapriyanatarajan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment