Bump github.com/tektoncd/triggers from 0.24.1 to 0.25.0

[dependabot]

Bumps github.com/tektoncd/triggers from 0.24.1 to 0.25.0.

Release notes

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

Tekton Triggers release v0.25.0 "Tekton Triggers"

-Docs @ v0.25.0 -Examples @ v0.25.0

Installation one-liner

kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.25.0/release.yaml
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.25.0/interceptors.yaml

Attestation

The Rekor UUID for this release is 24296fb24b8ad77a3b75040e94727f4d7a7246d5e704172f48f5969d1202903ecd5fb22a0cc5b0f5

Obtain the attestation:

REKOR_UUID=24296fb24b8ad77a3b75040e94727f4d7a7246d5e704172f48f5969d1202903ecd5fb22a0cc5b0f5
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/triggers/previous/v0.25.0/release.yaml
INTERCEPTORS_FILE=https://storage.googleapis.com/tekton-releases/triggers/previous/v0.25.0/interceptors.yaml
REKOR_UUID=24296fb24b8ad77a3b75040e94727f4d7a7246d5e704172f48f5969d1202903ecd5fb22a0cc5b0f5
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.25.0@sha256:" + .digest.sha256')
Download the release file
curl "$RELEASE_FILE" > release.yaml
curl "$INTERCEPTORS_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

... (truncated)

Changelog

Sourced from github.com/tektoncd/triggers's changelog.

Tekton Triggers Releases

Release Frequency

Tekton Triggers 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, when enough content is available
• 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 Triggers LTS release will be v0.22.0 in October 2022
  • Releases usually happen towards the middle of the month, but the exact date may vary, depending on week-ends and readiness

Tekton Triggers produces nightly builds, publicly available on gcr.io/tekton-nightly.

Transition Process

Before release v0.22 Tekton Triggers has worked on the basis of an undocumented support period of four months, which will be maintained for the release v0.21.

Release Process

Tekton Triggers releases are made of YAML manifests and container images. Manifests are published to cloud object-storage as well as [GitHub][tekton-triggers-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 Triggers [release process][tekton-releases-docs]
• [Installing Tekton][tekton-installation]
• Standard for [release notes][release-notes-standards]

Releases

v0.25

• Latest Release: [v0.25.0][v0-25-0] (2023-08-29) ([docs][v0-25-0-docs], [examples][v0-25-0-examples])
• Initial Release: [v0.24.1][v0-24-1] (2023-06-11)
• End of Life: 2023-09-30
• Patch Releases: [v0.25.0][v0-25-0]

v0.24 (LTS)

... (truncated)

Commits

• 9498e02 Bump tekton/pipelines v0.50.1 LTS in preparation of release
• 33af25d Fix EL Status URL for kubernetesresource.serviceport
• a50a972 Fix SA1019 error by staticcheck due to deprecation
• a4a4dc7 Change Leader Election Config Map for Controllers and Webhook
• 1c992ed Add AWS CodeCommit examples for push request and also README to configure AWS...
• b978eab Add probes support in Triggers eventlistener
• 9a29423 Added clarification about escaping special character in TB
• 57aa9a5 Update Cel-Go to v0.17.1
• 4b5f17a Update Cel-Go to v0.16.0
• ed70653 Fix the integraion Test by upgrading Knative
• 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 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)

[dependabot]

The following labels could not be found: ok-to-test, kind/misc, release-note-none.