chore(deps): bump github.com/tektoncd/pipeline from 1.15.0 to 1.16.0

[dependabot]

Bumps github.com/tektoncd/pipeline from 1.15.0 to 1.16.0.

Release notes

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

Tekton Pipeline release v1.16.0 "Manx WALL-E"

🎉 Secure by default, sharper traces 🎉

-Docs @ v1.16.0 -Examples @ v1.16.0

Installation one-liner

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

Attestation

The Rekor UUID for this release is 108e9186e8c5677a13e773b2ae0f6c52943d2b44a284030efb9b43068a9927a698b4799e13342b14

Obtain the attestation:

REKOR_UUID=108e9186e8c5677a13e773b2ae0f6c52943d2b44a284030efb9b43068a9927a698b4799e13342b14
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.16.0/release.yaml
REKOR_UUID=108e9186e8c5677a13e773b2ae0f6c52943d2b44a284030efb9b43068a9927a698b4799e13342b14
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.16.0@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

Upgrade Notices

• 🚨 set-security-context enabled by default

action required: set-security-context now defaults to true and applies only to Tekton-injected TaskRun containers and Affinity Assistants (#9589, #10680). User-defined Steps and Sidecars must supply their own restricted-compatible security contexts. If the generated security contexts are incompatible with your images or Kubernetes implementation, set set-security-context to "false".

Changes

Features

• ✨ feat(tracing): add spans for task parameter and workspace substitution #9801 (#10271)

... (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.16

• Latest Release: [v1.16.0][v1.16-0] (2026-08-31) ([docs][v1.16-0-docs], [examples][v1.16-0-examples])
• Initial Release: [v1.16.0][v1.16-0] (2026-08-31)
• End of Life: 2026-09-30
• Patch Releases: [v1.16.0][v1.16-0]

v1.15 (LTS)

... (truncated)

Commits

• 63c28f0 Fix critical libcurl CVEs in resolvers base image
• 9b5c227 Fix critical libcurl CVEs in resolvers base image
• 3f92dd0 docs: clarify set-security-context scope and rollback
• 2ba63de feat: enable set-security-context feature flag by default
• ce96643 build(deps): bump google.golang.org/grpc from 1.83.1 to 1.83.2
• 9e0103d build(deps): bump chainguard-dev/actions/kind-diag from 1.6.31 to 1.6.32
• f7fff2b build(deps): bump step-security/harden-runner from 2.20.1 to 2.21.0
• 3a7efbb build(deps): bump chainguard-dev/actions/setup-kind
• d13163c build(deps): bump github.com/tektoncd/pipeline
• bbc5b44 Bump github/codeql-action/analyze to v4.37.7
• Additional commits viewable in compare view

Most Recent Ignore Conditions Applied to This Pull Request

Dependency Name	Ignore Conditions
github.com/tektoncd/pipeline	[>= 0.43.a, < 0.44]

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]

@dependabot[bot]: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[tekton-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign vdemeester after the PR has been reviewed.
You can assign the PR to them by writing /assign @vdemeester 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