Bump github.com/tektoncd/triggers from 0.21.0 to 0.22.0

[dependabot]

Bumps github.com/tektoncd/triggers from 0.21.0 to 0.22.0.

Release notes

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

Tekton Triggers release v0.22.0

-Docs @ v0.22.0 -Examples @ v0.22.0

Installation one-liner

Triggers now requires Kuberentes v.123 or higher

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

Attestation

The Rekor UUID for this release is 24296fb24b8ad77a825172e0ac852ced908622c18666b3dbba54ae7e1934a9424b651bdd6041f9af

Obtain the attestation:

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

... (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.21

• Latest Release: [v0.21.0][v0-21-0] (2022-09-06) ([docs][v0-21-0-docs], [examples][v0-21-0-examples])
• Initial Release: [v0.21.0][v0-21-0] (2022-09-06)
• End of Life: 2023-01-05
• Patch Releases: [v0.21.0][v0-21-0]

End of Life Releases

... (truncated)

Commits

• b4a404d Add Example for NamespacedInterceptor
• a3cdd1a Add Documentation for NamespacedInterceptor
• 8797cc0 Add Namespaced Scope Interceptor
• 6a1528d Bump tektoncd/pipeline to v0.41.0
• d5f9887 Update CEL version to 0.12.5 and modified functions
• 9ad4d63 Move CloudEvent to Stable
• 004d21b Refactor interceptor main package
• 81d2ad1 Respond appropriately to CloudEvent requests
• ea35ac4 Modify e2e test scripts to support running on kind
• ce7b976 Replace PodSecurityPolicy with PodSecurityAdmission
• 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.

[pradeepitm12]

/test pull-tekton-cli-integration-tests

[vinamra28]

/retest
/release-note-none

[vinamra28]

/lgtm

[vdemeester]

/approve
/lgtm

[piyush-garg]

/approve
/lgtm

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: piyush-garg, vdemeester

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [piyush-garg,vdemeester]

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]: rebase

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.

[piyush-garg]

@dependabot rebase

[piyush-garg]

/lgtm