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

[dependabot[bot]]

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

Release notes

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

Tekton Pipeline release v0.38.3 "Ocicat Ava"

-Docs @ v0.38.3 -Examples @ v0.38.3

Installation one-liner

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

Attestation

The Rekor UUID for this release is 362f8ecba72f4326a418baaecb593233a0d4ac99b5f9657b66533bd25da323933e8994b6d424c6f1

Obtain the attestation:

REKOR_UUID=362f8ecba72f4326a418baaecb593233a0d4ac99b5f9657b66533bd25da323933e8994b6d424c6f1
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.38.3/release.yaml
REKOR_UUID=362f8ecba72f4326a418baaecb593233a0d4ac99b5f9657b66533bd25da323933e8994b6d424c6f1
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.38.3@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

• 365f1ef Unscheduled Runs shouldn't be included in full status
• 4512521 Use step.ImageID instead of looking into status.TaskSpec
• 1bed305 Add SetDefaults for pipelineSpec in reconciler
• e37fa6c Do not serve v1alpha1 for CRDs that do not exists anymore
• b8e244a Add StdoutConfig and StderrorConfig to v1 Step
• 3f53972 Add TerminationMessagePolicy in container conversion
• b2e3cfe Update GCR IAM settings in Tekton development doc
• 10a5ae6 use fake version matching testdata
• a1620c9 Prepare tests for impending knative/pkg version bump
• 85d5344 Move step and sidecar replacements to new package
• 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)

[tekton-robot]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a tektoncd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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 lukehinds after the PR has been reviewed. You can assign the PR to them by writing /assign @lukehinds in a comment when ready.

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

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

[tekton-robot]

@dependabot[bot]: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-tekton-chains-unit-tests	b68d5a1dd67bdb2051dd20285c873cb53afa62fa	link	true	/test pull-tekton-chains-unit-tests
pull-tekton-chains-build-tests	b68d5a1dd67bdb2051dd20285c873cb53afa62fa	link	true	/test pull-tekton-chains-build-tests
pull-tekton-chains-integration-tests	b68d5a1dd67bdb2051dd20285c873cb53afa62fa	link	true	/test pull-tekton-chains-integration-tests

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[dependabot[bot]]

Superseded by #525.