build(deps): bump github.com/tektoncd/triggers from 0.32.0 to 0.34.0 in /tekton/ci/interceptors/github

[dependabot]

Bumps github.com/tektoncd/triggers from 0.32.0 to 0.34.0.

Release notes

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

Tekton Triggers release v0.34.0 "Tekton Triggers"

-Docs @ v0.34.0 -Examples @ v0.34.0

Installation one-liner

kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/v0.34.0/release.yaml
kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/v0.34.0/interceptors.yaml

Attestation

The Rekor UUID for this release is 108e9186e8c5677af5fc7b3c5466e79e0ce84af7fbea9da03d09fcf1f91c05e1d34c23b20af28f3f

Obtain the attestation:

REKOR_UUID=108e9186e8c5677af5fc7b3c5466e79e0ce84af7fbea9da03d09fcf1f91c05e1d34c23b20af28f3f
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/triggers/previous/v0.34.0/release.yaml
REKOR_UUID=108e9186e8c5677af5fc7b3c5466e79e0ce84af7fbea9da03d09fcf1f91c05e1d34c23b20af28f3f
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.34.0@sha256:" + .digest.sha256')
Download the release file
curl -LO "$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)

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.34 (LTS)

• Latest Release: [v0.34.0][v0-34-0] (2025-09-07) ([docs][v0-34-0-docs], [examples][v0-34-0-examples])
• Initial Release: [v0.34.0][v0-34-0] (2025-09-07)
• End of Life: 2026-08-11
• Patch Releases: [v0.34.0][v0-34-0]

v0.33 (LTS)

... (truncated)

Commits

• 76660c5 Update release-cheat-sheet
• 50a00fe update pipelines for oracle bucket target
• 662bf07 Change the Pipelines install location to oracle infra from gcs
• 8b2923e Bump actions/setup-go from 5.5.0 to 6.0.0
• f9cd24f Update Go version in golangci-lint workflow
• 645fd37 Add tkn triggers bootstrap command for automated setup
• 70eaf7e fix: prevent goroutine leak in CA cert updater
• c387fb3 fix lint
• f447727 fix: escape Tekton variable syntax in trigger parameters
• 578911b Bump actions/upload-artifact from 4.6.2 to 5.0.0
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[vdemeester]

/lgtm

[vdemeester]

/lgtm

[vdemeester]

/lgtm

[vdemeester]

/lgtm

[vdemeester]

/lgtm

[vdemeester]

@dependabot rebase

[vdemeester]

/lgtm

[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