build(deps): bump github.com/tektoncd/triggers from 0.32.0 to 0.33.0 in /tekton/ci/interceptors/github
Bumps github.com/tektoncd/triggers from 0.32.0 to 0.33.0.
Release notes
Sourced from github.com/tektoncd/triggers's releases.
Tekton Triggers release v0.33.0 "Tekton Triggers"
-Docs @ v0.33.0 -Examples @ v0.33.0
Installation one-liner
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.33.0/release.yamlAttestation
The Rekor UUID for this release is
108e9186e8c5677a920a272eb27aa6fcc7d307787cce0478a57a43ac0c60867837b79d610ea3608eObtain the attestation:
REKOR_UUID=108e9186e8c5677a920a272eb27aa6fcc7d307787cce0478a57a43ac0c60867837b79d610ea3608e 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/${VERSION_TAG}/release.yaml INTERCEPTORS_FILE=https://storage.googleapis.com/tekton-releases/triggers/previous/${VERSION_TAG}/interceptors.yaml REKOR_UUID=108e9186e8c5677a920a272eb27aa6fcc7d307787cce0478a57a43ac0c60867837b79d610ea3608eObtains 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.33.0@sha256:" + .digest.sha256')
Download the release file
curl "$RELEASE_FILE" > release.yaml
curl "$INTERCEPTORS_FILE" >> release.yamlFor 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
- :sparkles: Add anti-affinity rules to controller's replicas (#1861) As part of improving high availability (HA) for the Tekton Triggers controller, this update adds a preferredDuringSchedulingIgnoredDuringExecution pod anti-affinity rule. This ensures that multiple replicas of the controller are preferably scheduled on different nodes, reducing the risk of service disruption in case of a node failure.
... (truncated)
Commits
8ff0d9cUpdate the ko to v0.18.0 with go1.24.5bda72d1Implement deep-copy fix for data raceb9c84cdRevert "fix data race with mutex"000c460Update some dependancy from dependabot711f6f8Bump the all group across 1 directory with 2 updates508d4bbGenerate the api docs and swagger API jsondbeacf1Fix the GolangCI Lint failures after deps updated85ca02Exclude some GolangCI lint tests from *_test filesf42ec98Pin golangci-lint to v2.1.6b9b35d4Fix test: the non-constant format passed to bitbucket interceptor- 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill 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.
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.
/retest
@dependabot rebase
[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
- ~~OWNERS~~ [vdemeester]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
Superseded by #2939.