chore(deps): bump github.com/tektoncd/pipeline from 1.0.0 to 1.0.3

[dependabot]

Bumps github.com/tektoncd/pipeline from 1.0.0 to 1.0.3.

Release notes

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

Tekton Pipeline release v1.0.3 "Oriental Omnidroid"

Tekton Pipeline release v1.0.3

-Docs @ v1.0.3 -Examples @ v1.0.3

Installation one-liner

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

Attestation

The Rekor UUID for this release is 108e9186e8c5677af9a0b5c0d190a06d3da1caf538bf0a6bb9020c707dcfdbe4dd8d2cbceec407d1

Obtain the attestation:

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

Fixes

• 🐛 Fix cross-arch platform command lookup in entrypoint (#10165)

Fix entrypoint command lookup when controller and worker nodes run on different CPU architectures (e.g., ARM controller with AMD64 workloads). The controller's CPU variant was leaking into TEKTON_PLATFORM_COMMANDS keys via platforms.NewPlatform(), causing "could not find command for platform" errors on worker nodes of a different architecture.

... (truncated)

Commits

• 063f14a fix: prevent controller CPU variant from leaking into platform commands
• dc544b1 build(deps): bump github.com/jenkins-x/go-scm from 1.14.56 to 1.14.59
• 857a6eb build(deps): bump go.uber.org/zap from 1.27.0 to 1.27.1
• fef382d build(deps): bump tj-actions/changed-files
• 6391d4e build(deps): bump the all group in /tekton with 4 updates
• 2f18d35 build(deps): bump step-security/harden-runner from 2.12.0 to 2.12.2
• dc4b0b0 build(deps): bump k8s.io/apiextensions-apiserver from 0.32.1 to 0.32.13
• 91c5032 build(deps): bump chainguard-dev/actions from 1.5.3 to 1.5.16
• 41c680b build(deps): bump ossf/scorecard-action from 2.4.1 to 2.4.3
• 784d6bd build(deps): bump tj-actions/changed-files
• 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)

[vdemeester]

/lgtm

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vdemeester

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [vdemeester]

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