Repository navigation
Tekton Triggers release v0.38.0 "Tekton Triggers" #2265
khrm
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Installation one-liner
Attestation
The Rekor UUID for this release is
108e9186e8c5677a5f36a3287f15f9acfe297c03b126ee9726e270cf1ad80268532062d7a514d2caObtain the attestation:
Verify that all container images in the attestation are in the release file:
Changes
Features
The GitLab interceptor can validate GitLab 19+ signing tokens via an optional
signingSecretRef(Standard Webhooks HMAC-SHA256). ExistingsecretRefsecret-token checks still work. When both are set, either a valid signature or a validX-Gitlab-Tokenis 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 to0to keep the previous unbounded behaviour.Fixes
action required: The
tekton-triggers-aggregate-editClusterRole (aggregated into the built-ineditandadminroles) no longer grants write access to the cluster-scopedclusterinterceptorsandclustertriggerbindingsresources. Read access viatekton-triggers-aggregate-viewis unchanged. Users who relied on a ClusterRoleBinding toedit/adminto manage ClusterInterceptors or ClusterTriggerBindings must be granted a dedicated ClusterRole explicitly. Namespace-scoped RoleBindings are unaffected.Misc
Docs
Thanks
Thanks to these contributors who contributed to v0.38.0!
Extra shout-out for awesome release notes:
This discussion was created from the release Tekton Triggers release v0.38.0 "Tekton Triggers".
All reactions