Bump github.com/tektoncd/pipeline from 0.43.0 to 0.43.1

[dependabot[bot]]

Bumps github.com/tektoncd/pipeline from 0.43.0 to 0.43.1.

Release notes

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

Tekton Pipeline release v0.43.1 "British-Shorthair Jarvis"

-Docs @ v0.43.1 -Examples @ v0.43.1

Installation one-liner

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

Attestation

The Rekor UUID for this release is 24296fb24b8ad77aafc26483b3dd67610086643ab88bb7166bfd137136fbdf182dc3bc8d76987194

Obtain the attestation:

REKOR_UUID=24296fb24b8ad77aafc26483b3dd67610086643ab88bb7166bfd137136fbdf182dc3bc8d76987194
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.43.1/release.yaml
REKOR_UUID=24296fb24b8ad77aafc26483b3dd67610086643ab88bb7166bfd137136fbdf182dc3bc8d76987194
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.43.1@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

Fixes

• :bug: [release-v0.43.x] Register informers for v1 TaskRun and PipelineRun (#5948)

... (truncated)

Commits

• be1ce9d tekton: fix KO_CONFIG_PATH on release pipeline
• a1bac54 ChildReference status helper functions should support both CustomRuns and Runs
• 8587b7b Register informers for v1 TaskRun and PipelineRun
• d5a98a6 Use the golangci-lint configured in Makefile in build tests
• 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 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)