Bump github.com/tektoncd/pipeline from 0.38.3 to 0.40.2

[dependabot[bot]]

Bumps github.com/tektoncd/pipeline from 0.38.3 to 0.40.2.

Release notes

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

Tekton Pipeline release v0.40.2 "Himalayan Sonny"

-Docs @ v0.40.2 -Examples @ v0.40.2

Installation one-liner

kubectl apply -f https://storage.googleapis.com/tekton-releases/pipeline/previous/v0.40.2/release.yaml

Attestation

The Rekor UUID for this release is 24296fb24b8ad77a2573afa5bfbd4582c0eb8c844009ee685a7e9abf6ae42b4d00b20c7485096315

Obtain the attestation:

REKOR_UUID=24296fb24b8ad77a2573afa5bfbd4582c0eb8c844009ee685a7e9abf6ae42b4d00b20c7485096315
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://storage.googleapis.com/tekton-releases/pipeline/previous/v0.40.2/release.yaml
REKOR_UUID=24296fb24b8ad77a2573afa5bfbd4582c0eb8c844009ee685a7e9abf6ae42b4d00b20c7485096315
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.40.2@sha256:" + .digest.sha256')
Download the release file
curl "$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

• 40a438a Write TaskRun.Status.TaskSpec with replaced spec on every reconcile run
• e6a2dc3 tekton: make sure the git workingdir is not dirty…
• f1e7c22 Update ko to v0.12.0
• 9cf7590 Fix taskrun not working with workspace having volumeClaimTemplate
• 782e492 Fix empty string paramValueType conversion
• 9221ac3 harden look like a result references check
• 34274fb fix regexp for ssh
• 75ac2fb Add ResolutionRequest v1beta1, without serving yet
• 1a1f2e3 add key to identify node instead of holding task
• 56dc8d9 TEP-0111 - Propagating workspaces pipelinerun
• 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 merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@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)

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.