NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules
Go modules, #2444 by repository stars
Latest stable
v0.38.0
Last release 13 days ago
09 Nov 2026
Ships on a steady schedule
a new release about every 2 weeks
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
7 years old
399 releases · first in 2019
Drag across the ruler to compare, or tap a release to open it.
kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/v0.38.0/release.yaml
kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/v0.38.0/release.yamlThe Rekor UUID for this release is 108e9186e8c5677a5f36a3287f15f9acfe297c03b126ee9726e270cf1ad80268532062d7a514d2ca
Obtain the attestation:
REKOR_UUID=108e9186e8c5677a5f36a3287f15f9acfe297c03b126ee9726e270cf1ad80268532062d7a514d2ca
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:
VERSION_TAG=v0.38.0
RELEASE_FILE=https://infra.tekton.dev/tekton-releases/triggers/previous/v0.38.0/release.yaml
INTERCEPTORS_FILE=https://infra.tekton.dev/tekton-releases/triggers/previous/${VERSION_TAG}/interceptors.yaml
REKOR_UUID=108e9186e8c5677a5f36a3287f15f9acfe297c03b126ee9726e270cf1ad80268532062d7a514d2ca
# 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.38.0@sha256:" + .digest.sha256')
# Download the release file
curl -L "$RELEASE_FILE" > release.yaml
curl -L "$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";
doneThe GitLab interceptor can validate GitLab 19+ signing tokens via an optional signingSecretRef (Standard Webhooks HMAC-SHA256). Existing secretRef secret-token checks still work. When both are set, either a valid signature or a valid X-Gitlab-Token is enough, so that you can migrate without downtime.
Breaking:
The EventListener sink now rejects event requests whose body exceeds a configurable limit with 413 Request Entity Too Large. The limit is set by the new controller flag -el-max-body-size (bytes, default 3145728 = 3 MiB); set it to 0 to keep the previous unbounded behaviour.
action required: The tekton-triggers-aggregate-edit ClusterRole (aggregated into the built-in edit and admin roles) no longer grants write access to the cluster-scoped clusterinterceptors and clustertriggerbindings resources. Read access via tekton-triggers-aggregate-view is unchanged. Users who relied on a ClusterRoleBinding to edit/admin to manage ClusterInterceptors or ClusterTriggerBindings must be granted a dedicated ClusterRole explicitly. Namespace-scoped RoleBindings are unaffected.
Thanks to these contributors who contributed to v0.38.0!
Extra shout-out for awesome release notes:
Your coding agent can read these notes before it upgrades. Set up the MCP server →
<!-- For major releases, add a tag line
-->
kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/v0.38.0/release.yaml
The Rekor UUID for this release is 108e9186e8c5677a5f36a3287f15f9acfe297c03b126ee9726e270cf1ad80268532062d7a514d2ca
Obtain the attestation:
REKOR_UUID=108e9186e8c5677a5f36a3287f15f9acfe297c03b126ee9726e270cf1ad80268532062d7a514d2ca
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:
VERSION_TAG=v0.38.0
RELEASE_FILE=https://infra.tekton.dev/tekton-releases/triggers/previous/v0.38.0/release.yaml
INTERCEPTORS_FILE=https://infra.tekton.dev/tekton-releases/triggers/previous/${VERSION_TAG}/interceptors.yaml
REKOR_UUID=108e9186e8c5677a5f36a3287f15f9acfe297c03b126ee9726e270cf1ad80268532062d7a514d2ca
# 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.38.0@sha256:" + .digest.sha256')
# Download the release file
curl -L "$RELEASE_FILE" > release.yaml
curl -L "$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
<!-- Any special upgrade notice
-->
The GitLab interceptor can validate GitLab 19+ signing tokens via an optional signingSecretRef (Standard Webhooks HMAC-SHA256). Existing secretRef secret-token checks still work. When both are set, either a valid signature or a valid X-Gitlab-Token is enough, so that you can migrate without downtime.
Breaking:
The EventListener sink now rejects event requests whose body exceeds a configurable limit with 413 Request Entity Too Large. The limit is set by the new controller flag -el-max-body-size (bytes, default 3145728 = 3 MiB); set it to 0 to keep the previous unbounded behaviour.
<!-- Fill in deprecation notices when applicable
[Detailed deprecation notice description] (#Number).
[Fill list here] -->
<!-- Fill in backward incompatible changes when applicable
In current release:
[Detailed change description] (#Number).
[Fill list here] -->
action required: The tekton-triggers-aggregate-edit ClusterRole (aggregated into the built-in edit and admin roles) no longer grants write access to the cluster-scoped clusterinterceptors and clustertriggerbindings resources. Read access via tekton-triggers-aggregate-view is unchanged. Users who relied on a ClusterRoleBinding to edit/admin to manage ClusterInterceptors or ClusterTriggerBindings must be granted a dedicated ClusterRole explicitly. Namespace-scoped RoleBindings are unaffected.
Thanks to these contributors who contributed to v0.38.0!
Extra shout-out for awesome release notes:
<!--
To Be Done: Deprecation Notices, Backward Incompatible Changes -->
kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/v0.37.3/release.yaml kubectl apply -f https://infra.tekton.dev/tekton-rele
kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/v0.37.3/release.yaml
kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/${VERSION_TAG}/interceptors.yaml
The Rekor UUID for this release is 108e9186e8c5677a33a1c2e06db7e1e7f0731543afd4e94247c047bf7b963e3f354dc002721ab392
Obtain the attestation:
REKOR_UUID=108e9186e8c5677a33a1c2e06db7e1e7f0731543afd4e94247c047bf7b963e3f354dc002721ab392
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.37.3/release.yaml
INTERCEPTORS_FILE=https://infra.tekton.dev/tekton-releases/triggers/previous/${VERSION_TAG}/interceptors.yaml
REKOR_UUID=108e9186e8c5677a33a1c2e06db7e1e7f0731543afd4e94247c047bf7b963e3f354dc002721ab392
# 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.37.3@sha256:" + .digest.sha256')
# Download the release file
curl -L "$RELEASE_FILE" > release.yaml
curl -L "$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";
doneThanks to these contributors who contributed to v0.37.3!
Extra shout-out for awesome release notes:
kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/v0.37.2/release.yaml kubectl apply -f https://infra.tekton.dev/tekton-rele
kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/v0.37.2/release.yaml
kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/v0.37.2/interceptors.yamlThe Rekor UUID for this release is 108e9186e8c5677a889346219c9d5f355c0a1bd1004763a9798a6ba12261500c1e9e6be332e5ac50
Obtain the attestation:
REKOR_UUID=108e9186e8c5677a889346219c9d5f355c0a1bd1004763a9798a6ba12261500c1e9e6be332e5ac50
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.37.2/release.yaml
REKOR_UUID=108e9186e8c5677a889346219c9d5f355c0a1bd1004763a9798a6ba12261500c1e9e6be332e5ac50
# 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.37.2@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";
doneThanks to these contributors who contributed to v0.37.2!
Extra shout-out for awesome release notes:
kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/v0.37.1/release.yaml kubectl apply -f https://infra.tekton.dev/tekton-rele
kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/v0.37.1/release.yaml
kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/v0.37.1/interceptors.yamlThe Rekor UUID for this release is 108e9186e8c5677ad028f84990e7f434fcb63d84486bf5505a4c7376a9efedfb1ba298536d13a88c
Obtain the attestation:
REKOR_UUID=108e9186e8c5677ad028f84990e7f434fcb63d84486bf5505a4c7376a9efedfb1ba298536d13a88c
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.37.1/release.yaml
INTERCEPTORS_FILE=https://infra.tekton.dev/tekton-releases/triggers/previous/v0.37.1/interceptors.yaml
REKOR_UUID=108e9186e8c5677ad028f84990e7f434fcb63d84486bf5505a4c7376a9efedfb1ba298536d13a88c
# 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.37.1@sha256:" + .digest.sha256')
# Download the release file
curl -L "$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";
doneEnforce that the Github Interceptor must be used in conjunction with secretRef, to ensure all Github payloads are verifiably signed
Action Required: Users using the Github Interceptor must ensure the interceptor uses a secretRef, as described in the documentation
Add a configmap-driven allowlist for allowed hosts by the Github Interceptors. A new feature flag interceptors.github.use-enterprise-host-allowlist controls whether or not the allow-list is enforced. The feature flag defaults to false for backwards compatiblity but in later releases it will default to true and eventually be removed
Thanks to these contributors who contributed to v0.37.1!
Extra shout-out for awesome release notes:
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/v0.37.0/release.yaml
kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/v0.37.0/release.yamlThe Rekor UUID for this release is 108e9186e8c5677a1a23009a1951f3bd03d8d05e083fa175f2559de39d752ad4f3e71db31cb030b4
Obtain the attestation:
REKOR_UUID=108e9186e8c5677a1a23009a1951f3bd03d8d05e083fa175f2559de39d752ad4f3e71db31cb030b4
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.37.0/release.yaml
INTERCEPTORS_FILE=https://infra.tekton.dev/tekton-releases/triggers/previous/v0.37.0/interceptors.yaml
REKOR_UUID=108e9186e8c5677a1a23009a1951f3bd03d8d05e083fa175f2559de39d752ad4f3e71db31cb030b4
# 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.37.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";
doneFix a bug where a webhook-type interceptor placed first in a trigger's
interceptor chain would receive a pre-parsed JSON body instead of the
original request body for application/x-www-form-urlencoded requests
(e.g. Slack slash commands), breaking custom interceptors that parse the
raw form-encoded payload themselves.
Thanks to these contributors who contributed to v0.37.0!
Extra shout-out for awesome release notes:
<!-- For major releases, add a tag line
-->
kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/v0.37.0/release.yaml
The Rekor UUID for this release is 108e9186e8c5677a1a23009a1951f3bd03d8d05e083fa175f2559de39d752ad4f3e71db31cb030b4
Obtain the attestation:
REKOR_UUID=108e9186e8c5677a1a23009a1951f3bd03d8d05e083fa175f2559de39d752ad4f3e71db31cb030b4
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.37.0/release.yaml
INTERCEPTORS_FILE=https://infra.tekton.dev/tekton-releases/triggers/previous/v0.37.0/interceptors.yaml
REKOR_UUID=108e9186e8c5677a1a23009a1951f3bd03d8d05e083fa175f2559de39d752ad4f3e71db31cb030b4
# 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.37.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
<!-- Any special upgrade notice
-->
<!-- Fill in deprecation notices when applicable
[Detailed deprecation notice description] (#Number).
[Fill list here] -->
<!-- Fill in backward incompatible changes when applicable
In current release:
[Detailed change description] (#Number).
[Fill list here] -->
Fix a bug where a webhook-type interceptor placed first in a trigger's
interceptor chain would receive a pre-parsed JSON body instead of the
original request body for application/x-www-form-urlencoded requests
(e.g. Slack slash commands), breaking custom interceptors that parse the
raw form-encoded payload themselves.
Thanks to these contributors who contributed to v0.37.0!
Extra shout-out for awesome release notes:
kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/v0.36.5/release.yaml kubectl apply -f https://infra.tekton.dev/tekton-rele
kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/v0.36.5/release.yaml
kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/v0.36.5/interceptors.yamlThe Rekor UUID for this release is 108e9186e8c5677a116fd402a4b88d7f86c9307184bd21d1f9e04c79f5b422475abd9a5d6b096b09
Obtain the attestation:
REKOR_UUID=108e9186e8c5677a116fd402a4b88d7f86c9307184bd21d1f9e04c79f5b422475abd9a5d6b096b09
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.36.5/release.yaml
REKOR_UUID=108e9186e8c5677a116fd402a4b88d7f86c9307184bd21d1f9e04c79f5b422475abd9a5d6b096b09
# 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.36.5@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";
doneThanks to these contributors who contributed to v0.36.5!
Extra shout-out for awesome release notes:
kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/v0.36.4/release.yaml kubectl apply -f https://infra.tekton.dev/tekton-rele
kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/v0.36.4/release.yaml
kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/v0.36.4/interceptors.yaml
The Rekor UUID for this release is 108e9186e8c5677ada1ecf1b8eeef5c1981e8f0ac8c97547d1ac2ac60faaebc8cbdd1ed029be6683
Obtain the attestation:
REKOR_UUID=108e9186e8c5677ada1ecf1b8eeef5c1981e8f0ac8c97547d1ac2ac60faaebc8cbdd1ed029be6683
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.36.4/release.yaml
REKOR_UUID=108e9186e8c5677ada1ecf1b8eeef5c1981e8f0ac8c97547d1ac2ac60faaebc8cbdd1ed029be6683
# 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.36.4@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";
doneThanks to these contributors who contributed to v0.36.4!
Extra shout-out for awesome release notes:
kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/v0.36.3/release.yaml kubectl apply -f https://infra.tekton.dev/tekton-rele
kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/v0.36.3/release.yaml
kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/v0.36.3/interceptors.yaml
The Rekor UUID for this release is 108e9186e8c5677abce739e139f4749e4c555c2475a0dd52f6399ee19f321775e74a586696fc6e7e
Obtain the attestation:
REKOR_UUID=108e9186e8c5677abce739e139f4749e4c555c2475a0dd52f6399ee19f321775e74a586696fc6e7e
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.36.3/release.yaml
REKOR_UUID=108e9186e8c5677abce739e139f4749e4c555c2475a0dd52f6399ee19f321775e74a586696fc6e7e
# 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.36.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";
doneThanks to these contributors who contributed to v0.36.3!
Extra shout-out for awesome release notes:
message: 'Back-off pulling image "ghcr.io/tektoncd/triggers/github.com/tektoncd/triggers/cmd/interceptors:v0.36.1@sha256:dd912184e0213e0bb4db968ba0909
currently we are facing
message: 'Back-off pulling image "ghcr.io/tektoncd/triggers/github.com/tektoncd/triggers/cmd/interceptors:v0.36.1@sha256:dd912184e0213e0bb4db968ba0909a4b77579c423c12307105642275acb3efb0":
ErrImagePull: failed to pull and unpack image "ghcr.io/tektoncd/triggers/github.com/tektoncd/triggers/cmd/interceptors@sha256:dd912184e0213e0bb4db968ba0909a4b77579c423c12307105642275acb3efb0":
failed to resolve reference "ghcr.io/tektoncd/triggers/github.com/tektoncd/triggers/cmd/interceptors@sha256:dd912184e0213e0bb4db968ba0909a4b77579c423c12307105642275acb3efb0":
failed to authorize: failed to fetch anonymous token: unexpected status
from GET request to https://ghcr.io/token?scope=repository%3Atektoncd%2Ftriggers%2Fgithub.com%2Ftektoncd%2Ftriggers%2Fcmd%2Finterceptors%3Apull&service=ghcr.io:
401 Unauthorized'
reason: ImagePullBackOff
As it looks ko path
making koExtraArgs to " " should fix
kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/v0.36.1/release.yaml kubectl apply -f https://infra.tekton.dev/tekton-rele
kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/v0.36.1/release.yaml
kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/v0.36.1/interceptors.yamlThe Rekor UUID for this release is 108e9186e8c5677a657a035abaa26626fb70696b986e9a50cab171d2e2fa7047a72e03f050c5f135
Obtain the attestation:
REKOR_UUID=108e9186e8c5677a657a035abaa26626fb70696b986e9a50cab171d2e2fa7047a72e03f050c5f135
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.36.1/release.yaml
INTERCEPTORS_FILE=https://infra.tekton.dev/tekton-releases/triggers/previous/v0.36.1/interceptors.yaml
REKOR_UUID=108e9186e8c5677a657a035abaa26626fb70696b986e9a50cab171d2e2fa7047a72e03f050c5f135
REKOR_ATTESTATION_IMAGES=$(rekor-cli get --uuid "$REKOR_UUID" --format json | jq -r .Attestation | jq -r '.subject[]|.name + ":v0.36.1@sha256:" + .digest.sha256')
curl -L "$RELEASE_FILE" > release.yaml
curl "$INTERCEPTORS_FILE" >> release.yaml
for image in $REKOR_ATTESTATION_IMAGES; do
printf $image; grep -q $image release.yaml && echo " ===> ok" || echo " ===> no match";
donePatch release on top of v0.36.0.
This release was created manually; automated GitHub draft release creation for triggers is being added in #2171.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Tekton Triggers release v0.36.0 "Tekton Triggers"
Tekton Triggers release v0.36.0 "Tekton Triggers"
-Docs @ v0.36.0
-Examples @ v0.36.0
kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/v0.36.0/release.yamlThe Rekor UUID for this release is 108e9186e8c5677a6b2a69794ca92fea0d3bb45b80f923817fd184a39c84987cd53cee88dcf9dc5f
Obtain the attestation:
REKOR_UUID=108e9186e8c5677a6b2a69794ca92fea0d3bb45b80f923817fd184a39c84987cd53cee88dcf9dc5f
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.36.0/release.yaml
INTERCEPTORS_FILE=https://infra.tekton.dev/tekton-releases/triggers/previous/${VERSION_TAG}/interceptors.yaml
REKOR_UUID=108e9186e8c5677a6b2a69794ca92fea0d3bb45b80f923817fd184a39c84987cd53cee88dcf9dc5f
# 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.36.0@sha256:" + .digest.sha256')
# Download the release file
curl -L "$RELEASE_FILE" > release.yaml
curl -L "$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";
doneCore interceptors now honor the TLS security profile injected by the Tekton operator via TLS_MIN_VERSION, TLS_CIPHER_SUITES, and TLS_CURVE_PREFERENCES environment variables, allowing cluster-wide TLS policy enforcement on OpenShift.
Migrated metrics from OpenCensus to OpenTelemetry.
ACTION REQUIRED:
Configuration key change
Replace metrics.backend-destination with metrics-protocol in your config-observability-triggers ConfigMap.
Prometheus export remains the default — no change needed if you were not customizing observability.
Infrastructure metric renaming
Infrastructure metrics (workqueue, K8s client) have been renamed from the
tekton_triggers_controller_ prefix to standard Knative/OpenTelemetry namespaces.
┌──────────────────────────────────────────────────────────┬───────────────────────────────────────────────────┐
│ Old Metric Name (OpenCensus) │ New Metric Name (OpenTelemetry) │
├──────────────────────────────────────────────────────────┼───────────────────────────────────────────────────┤
│ tekton_triggers_controller_workqueue_depth │ kn_workqueue_depth │
│ tekton_triggers_controller_workqueue_adds_total │ kn_workqueue_adds_total │
│ tekton_triggers_controller_workqueue_queue_latency_* │ kn_workqueue_queue_duration_seconds_* │
│ tekton_triggers_controller_workqueue_work_duration_* │ kn_workqueue_process_duration_seconds_* │
│ tekton_triggers_controller_workqueue_unfinished_work_* │ kn_workqueue_unfinished_work_seconds │
│ tekton_triggers_controller_workqueue_retries_total │ kn_workqueue_retries_total │
│ tekton_triggers_controller_client_latency │ http_client_request_duration_seconds_* │
│ tekton_triggers_controller_client_results │ kn_k8s_client_http_response_status_code_total │
└──────────────────────────────────────────────────────────┴───────────────────────────────────────────────────┘
Sink counter metrics renamed
┌──────────────────────────────────────────┬────────────────────────────────────────────┐
│ Old Metric Name (OpenCensus) │ New Metric Name (OpenTelemetry) │
├──────────────────────────────────────────┼────────────────────────────────────────────┤
│ eventlistener_event_received_count │ eventlistener_event_received_total │
│ eventlistener_triggered_resources │ eventlistener_triggered_resources_total │
└──────────────────────────────────────────┴────────────────────────────────────────────┘
All other metric names are unchanged
controller_eventlistener_count, controller_triggerbinding_count,
controller_triggertemplate_count, controller_clustertriggerbinding_count,
controller_clusterinterceptor_count, eventlistener_http_duration_seconds
Thanks to these contributors who contributed to v0.36.0!
Extra shout-out for awesome release notes:
Tekton Triggers release v0.36.0 "Tekton Triggers"
<!-- For major releases, add a tag line
-->
-Docs @ v0.36.0 -Examples @ v0.36.0
kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/v0.36.0/release.yaml
The Rekor UUID for this release is 108e9186e8c5677a6b2a69794ca92fea0d3bb45b80f923817fd184a39c84987cd53cee88dcf9dc5f
Obtain the attestation:
REKOR_UUID=108e9186e8c5677a6b2a69794ca92fea0d3bb45b80f923817fd184a39c84987cd53cee88dcf9dc5f
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.36.0/release.yaml
INTERCEPTORS_FILE=https://infra.tekton.dev/tekton-releases/triggers/previous/${VERSION_TAG}/interceptors.yaml
REKOR_UUID=108e9186e8c5677a6b2a69794ca92fea0d3bb45b80f923817fd184a39c84987cd53cee88dcf9dc5f
# 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.36.0@sha256:" + .digest.sha256')
# Download the release file
curl -L "$RELEASE_FILE" > release.yaml
curl -L "$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
<!-- Any special upgrade notice
-->
Core interceptors now honor the TLS security profile injected by the Tekton operator via TLS_MIN_VERSION, TLS_CIPHER_SUITES, and TLS_CURVE_PREFERENCES environment variables, allowing cluster-wide TLS policy enforcement on OpenShift.
Migrated metrics from OpenCensus to OpenTelemetry.
ACTION REQUIRED:
Configuration key change Replace metrics.backend-destination with metrics-protocol in your config-observability-triggers ConfigMap. Prometheus export remains the default — no change needed if you were not customizing observability.
Infrastructure metric renaming Infrastructure metrics (workqueue, K8s client) have been renamed from the tekton_triggers_controller_ prefix to standard Knative/OpenTelemetry namespaces.
┌──────────────────────────────────────────────────────────┬───────────────────────────────────────────────────┐ │ Old Metric Name (OpenCensus) │ New Metric Name (OpenTelemetry) │ ├──────────────────────────────────────────────────────────┼───────────────────────────────────────────────────┤ │ tekton_triggers_controller_workqueue_depth │ kn_workqueue_depth │ │ tekton_triggers_controller_workqueue_adds_total │ kn_workqueue_adds_total │ │ tekton_triggers_controller_workqueue_queue_latency_* │ kn_workqueue_queue_duration_seconds_* │ │ tekton_triggers_controller_workqueue_work_duration_* │ kn_workqueue_process_duration_seconds_* │ │ tekton_triggers_controller_workqueue_unfinished_work_* │ kn_workqueue_unfinished_work_seconds │ │ tekton_triggers_controller_workqueue_retries_total │ kn_workqueue_retries_total │ │ tekton_triggers_controller_client_latency │ http_client_request_duration_seconds_* │ │ tekton_triggers_controller_client_results │ kn_k8s_client_http_response_status_code_total │ └──────────────────────────────────────────────────────────┴───────────────────────────────────────────────────┘
Sink counter metrics renamed
┌──────────────────────────────────────────┬────────────────────────────────────────────┐ │ Old Metric Name (OpenCensus) │ New Metric Name (OpenTelemetry) │ ├──────────────────────────────────────────┼────────────────────────────────────────────┤ │ eventlistener_event_received_count │ eventlistener_event_received_total │ │ eventlistener_triggered_resources │ eventlistener_triggered_resources_total │ └──────────────────────────────────────────┴────────────────────────────────────────────┘
All other metric names are unchanged controller_eventlistener_count, controller_triggerbinding_count, controller_triggertemplate_count, controller_clustertriggerbinding_count, controller_clusterinterceptor_count, eventlistener_http_duration_seconds
<!-- Fill in deprecation notices when applicable
[Detailed deprecation notice description] (#Number).
[Fill list here] -->
<!-- Fill in backward incompatible changes when applicable
In current release:
[Detailed change description] (#Number).
[Fill list here] -->
Thanks to these contributors who contributed to v0.36.0!
Extra shout-out for awesome release notes:
<!--
To Be Done: Deprecation Notices, Backward Incompatible Changes -->
kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/v0.35.3/release.yaml kubectl apply -f https://infra.tekton.dev/tekton-rele
kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/v0.35.3/release.yaml
kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/v0.35.3/interceptors.yamlThe Rekor UUID for this release is 108e9186e8c5677a23907429ba9cf60fe88e47485b8efc54b43d58ff57d780f0bfd45dadca5d1fa5
Obtain the attestation:
REKOR_UUID=108e9186e8c5677a23907429ba9cf60fe88e47485b8efc54b43d58ff57d780f0bfd45dadca5d1fa5
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.35.3/release.yaml
REKOR_UUID=108e9186e8c5677a23907429ba9cf60fe88e47485b8efc54b43d58ff57d780f0bfd45dadca5d1fa5
# 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.35.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";
doneThanks to these contributors who contributed to v0.35.3!
Extra shout-out for awesome release notes:
message: 'Back-off pulling image "ghcr.io/tektoncd/triggers/github.com/tektoncd/triggers/cmd/interceptors:v0.36.1@sha256:dd912184e0213e0bb4db968ba0909
currently we are facing
message: 'Back-off pulling image "ghcr.io/tektoncd/triggers/github.com/tektoncd/triggers/cmd/interceptors:v0.36.1@sha256:dd912184e0213e0bb4db968ba0909a4b77579c423c12307105642275acb3efb0":
ErrImagePull: failed to pull and unpack image "ghcr.io/tektoncd/triggers/github.com/tektoncd/triggers/cmd/interceptors@sha256:dd912184e0213e0bb4db968ba0909a4b77579c423c12307105642275acb3efb0":
failed to resolve reference "ghcr.io/tektoncd/triggers/github.com/tektoncd/triggers/cmd/interceptors@sha256:dd912184e0213e0bb4db968ba0909a4b77579c423c12307105642275acb3efb0":
failed to authorize: failed to fetch anonymous token: unexpected status
from GET request to https://ghcr.io/token?scope=repository%3Atektoncd%2Ftriggers%2Fgithub.com%2Ftektoncd%2Ftriggers%2Fcmd%2Finterceptors%3Apull&service=ghcr.io:
401 Unauthorized'
reason: ImagePullBackOff
As it looks ko path
making koExtraArgs to " " should fix
kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/v0.35.1/release.yaml kubectl apply -f https://infra.tekton.dev/tekton-rele
kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/v0.35.1/release.yaml
kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/v0.35.1/interceptors.yamlThe Rekor UUID for this release is 108e9186e8c5677afcbbd2fbbeb11137aa3b20516853ad8927ca19f4009f533f8669a1749ef4221b
Obtain the attestation:
REKOR_UUID=108e9186e8c5677afcbbd2fbbeb11137aa3b20516853ad8927ca19f4009f533f8669a1749ef4221b
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.35.1/release.yaml
INTERCEPTORS_FILE=https://infra.tekton.dev/tekton-releases/triggers/previous/v0.35.1/interceptors.yaml
REKOR_UUID=108e9186e8c5677afcbbd2fbbeb11137aa3b20516853ad8927ca19f4009f533f8669a1749ef4221b
REKOR_ATTESTATION_IMAGES=$(rekor-cli get --uuid "$REKOR_UUID" --format json | jq -r .Attestation | jq -r '.subject[]|.name + ":v0.35.1@sha256:" + .digest.sha256')
curl -L "$RELEASE_FILE" > release.yaml
curl "$INTERCEPTORS_FILE" >> release.yaml
for image in $REKOR_ATTESTATION_IMAGES; do
printf $image; grep -q $image release.yaml && echo " ===> ok" || echo " ===> no match";
donePatch release on top of v0.35.0.
This release was created manually; automated GitHub draft release creation for triggers is being added in #2171.
kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/v0.35.1/release.yaml
kubectl apply -f https://infra.tekton.dev/tekton-releases/triggers/previous/v0.35.1/interceptors.yaml
The Rekor UUID for this release is 108e9186e8c5677afcbbd2fbbeb11137aa3b20516853ad8927ca19f4009f533f8669a1749ef4221b
Obtain the attestation:
REKOR_UUID=108e9186e8c5677afcbbd2fbbeb11137aa3b20516853ad8927ca19f4009f533f8669a1749ef4221b
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.35.1/release.yaml
INTERCEPTORS_FILE=https://infra.tekton.dev/tekton-releases/triggers/previous/v0.35.1/interceptors.yaml
REKOR_UUID=108e9186e8c5677afcbbd2fbbeb11137aa3b20516853ad8927ca19f4009f533f8669a1749ef4221b
REKOR_ATTESTATION_IMAGES=$(rekor-cli get --uuid "$REKOR_UUID" --format json | jq -r .Attestation | jq -r '.subject[]|.name + ":v0.35.1@sha256:" + .digest.sha256')
curl -L "$RELEASE_FILE" > release.yaml
curl "$INTERCEPTORS_FILE" >> release.yaml
for image in $REKOR_ATTESTATION_IMAGES; do
printf $image; grep -q $image release.yaml && echo " ===> ok" || echo " ===> no match";
done
Patch release on top of v0.35.0.
This release was created manually; automated GitHub draft release creation for triggers is being added in #2171.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.