chore(deps): bump github.com/tektoncd/pipeline from 1.12.0 to 1.13.1

[dependabot]

Bumps github.com/tektoncd/pipeline from 1.12.0 to 1.13.1.

Release notes

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

Tekton Pipeline release v1.13.1 "Pixie-bob Project 2501"

-Docs @ v1.13.1 -Examples @ v1.13.1

Installation one-liner

kubectl apply -f https://infra.tekton.dev/tekton-releases/pipeline/previous/v1.13.1/release.yaml

Attestation

The Rekor UUID for this release is 108e9186e8c5677a85ce425ccafc0d84ae54b26fb57ec6dce775f05aa9b92b99e84371ddcbad2a77

Obtain the attestation:

REKOR_UUID=108e9186e8c5677a85ce425ccafc0d84ae54b26fb57ec6dce775f05aa9b92b99e84371ddcbad2a77
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.13.1/release.yaml
REKOR_UUID=108e9186e8c5677a85ce425ccafc0d84ae54b26fb57ec6dce775f05aa9b92b99e84371ddcbad2a77
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.13.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

... (truncated)

Changelog

Sourced from github.com/tektoncd/pipeline's changelog.

Tekton Pipeline Releases

Release Frequency

Tekton Pipelines follows the Tekton community [release policy][release-policy] as follows:

• Versions are numbered according to semantic versioning: vX.Y.Z
• A new release is produced on a monthly basis
• Four releases a year are chosen for long term support (LTS). All remaining releases are supported for approximately 1 month (until the next release is produced)
  • LTS releases take place in January, April, July and October every year
  • The first Tekton Pipelines LTS release will be v0.41.0 in October 2022
  • Releases happen towards the middle of the month, between the 13th and the 20th, depending on week-ends and readiness

Tekton Pipelines produces nightly builds, publicly available on gcr.io/tekton-nightly.

Transition Process

Before release v0.41 Tekton Pipelines has worked on the basis of an undocumented support period of four months, which will be maintained for the releases between v0.37 and v0.40.

Release Process

Tekton Pipeline releases are made of YAML manifests and container images. Manifests are published to cloud object-storage as well as [GitHub][tekton-pipeline-releases]. Container images are signed by [Sigstore][sigstore] via [Tekton Chains][tekton-chains]; signatures can be verified through the [public key][chains-public-key] hosted by the Tekton Chains project.

Further documentation available:

• The Tekton Pipeline [release process][tekton-releases-docs]
• [Installing Tekton][tekton-installation]
• Standard for [release notes][release-notes-standards]

Release

v1.13

• Latest Release: [v1.13.0][v1.13-0] (2026-05-29) ([docs][v1.13-0-docs], [examples][v1.13-0-examples])
• Initial Release: [v1.13.0][v1.13-0] (2026-05-29)
• End of Life: 2026-06-29
• Patch Releases: [v1.13.0][v1.13-0]

v1.12 (LTS)

... (truncated)

Commits

• e32fe4d fix(resolvers): Allow ResolutionRequests to resolve all Tekton kinds
• e9ed60c fix: TaskRun stuck in Running when init container is OOMKilled with enableKub...
• 4ffddd2 fix: add automated draft release support to release pipeline
• fc54377 fix: avoid spurious termination parse warning
• b974170 fix: make internal container resources opt-in
• 31e7226 fix: allow finally tasks to run when tasks timeout is exceeded (#6794)
• e7c660e build: bump go directive to 1.26
• e0ed3ff ci: fix setup-go version comment in codeql-analysis.yml
• 285339d fix: truncate affinity assistant volume names to 63 characters
• 9a18647 fix: avoid throttling script init container
• Additional commits viewable 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)

[tekton-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign savitaashture after the PR has been reviewed.
You can assign the PR to them by writing /assign @savitaashture in a comment when ready.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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