NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
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.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →
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
DEPRECATION NOTICE: In the future, we plan to deprecate the other status conditions in favor of the Ready status condition.
-Docs @ v0.14.0 -Examples @ v0.14.0
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.14.0/release.yaml
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.14.0/interceptors.yaml
release.yaml contains the core release artifacts while interceptors.yaml contain the 4 core interceptors (GitHub, GitLab, BitBucket, and CEL).kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.14.0/release.yaml
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.14.0/interceptors.yaml
TriggerBinding produces error on providing invalid Tekton template values.
Added Eventlistener OpenCensus metrics which captures metrics at process level.
User cannot specify both TriggerRef and (TriggerTemplate, TriggerBindings, Interceptors) as part of eventlistener spec.
The EventListener Status now has a new Condition called Ready. Ready is set to True when the other status conditions are also true (i.e. the EventListener is ready to serve traffic). It is false if any of the other statuses are false.
The EventListener Status now has a new Condition called Ready. Ready is set to True when the other status conditions are also true (i.e. the EventListener is ready to serve traffic). It is false if any of the other statuses are false.
DEPRECATION NOTICE: In the future, we plan to deprecate the other status conditions in favor of the Ready status condition.
eventListener and namespace fields in EventListener response are now deprecated. Use eventListenerUID instead.
As part of this release we have removed deprecated fields ServiceType and PodTemplate from the EventListener Spec.
Skip heavy validation on deletion in the webhook.
Triggers exposes metrics on 9000 port.
eventListener and namespace fields in EventListener response are now deprecated. Use eventListenerUID instead.
The CEL interceptor is updated to the latest version of CEL, this brings in the CEL base64 decoding functions.
These are documented here https://github.com/google/cel-go/tree/master/ext#base64decode
Note: the CEL base64 decoding function decodes to a CEL byte array, which is not a string, it uses the b'hello' syntax to represent a string of bytes "hello".
The triggers decodeb64 CEL function is now deprecated in favour of the upstream encoders package, you can replace body.value.decodeb64 with string(base64.decode(body.value))
Interceptors Page (#1035)ClusterInterceptors page for clarity and flow (#1048)EventListeners Page (#1060)Thanks to these contributors who contributed to v0.14.0!
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
To Be Done: Deprecation Notices, Backward Incompatible Changes
-Docs @ v0.13.0 -Examples @ v0.13.0
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.13.0/release.yaml
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.13.0/interceptors.yaml
As of this release, the Triggers release will contain two YAML files. release.yaml contains the core release artifacts while interceptors.yaml contain the 4 core interceptors (GitHub, GitLab, BitBucket, and CEL).
The EventListener ServiceAccount will now need a ClusterRole (and corresponding ClusterRoleBinding) to use the new ClusterInterceptor types (example)
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.13.0/release.yaml
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.13.0/interceptors.yaml
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1
metadata:
name: tekton-triggers-example-clusterrole
rules:
# EventListeners need to be able to fetch any clustertriggerbindings
- apiGroups: ["triggers.tekton.dev"]
resources: ["clustertriggerbindings", "clusterinterceptors"]
verbs: ["get", "list", "watch"]
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: tekton-triggers-example-clusterbinding
subjects:
- kind: ServiceAccount
name: tekton-triggers-example-sa
namespace: default
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: tekton-triggers-example-clusterrole
:sparkles: Adding label selector for triggers (#970)
Users can now configure triggers for an EventListener using labels
:sparkles: Added URL field to WebhookInterceptor (#1002)
Users can now configure webhook interceptors by referencing a URL
:sparkles: Add ClusterInterceptor CRD for registering interceptors (#960)
A new CRD called ClusterInterceptor has been added that allows for users to register new pluggable Interceptor types
:sparkles: Add API to configure Interceptors from a Trigger (#1001)
Trigger spec authors can now configure interceptors using a new API that includes a ref field to refer to a ClusterInterceptor, and
a params field to add parameters to pass on to the interceptor for processing
:sparkles: Migrate core interceptors to use InterceptorType CRD (#976)
The four bundled interceptors (CEL, GitHub, GitLab, BitBucket) are now implemented using the new ClusterInterceptor CRD
:sparkles: Migrate core interceptors to new format (#1029)
Any new Triggers created using the old style syntax for core interceptors is now automatically switched to the new refs/params based syntax.
:rotating_light: Move replicas to KubernetesResource from eventlistener spec (#1021)
Deprecated replicas from EventListener spec level and added replicas to KubernetesResource.
:rotating_light: Migrate core interceptors to new format (#1029)
Interceptors in a Trigger are now configured using a new ref and params based syntax as described in #1001, and in #976 we
have implemented the core interceptors using the new ClusterInterceptor CRD. So, these core interceptors can now be configured
using the new syntax. The old way of configuring these interceptors is now deprecated but it will continue to work until it is removed
in a future release. The defaulting webhook will automatically switch any usages of the old syntax to the new for any new Triggers.
TriggerTemplates and TriggerBindings (#991)Thanks to these contributors who contributed to v0.13.0!
Extra shout-out for awesome release notes:
To Be Done: Deprecation Notices, Backward Incompatible Changes
-Docs @ v0.12.1 -Examples @ v0.12.1
-Docs @ v0.12.1 -Examples @ v0.12.1
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.12.1/release.yaml
Thanks to these contributors who contributed to v0.12.1!
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
Remove deprecated field template.Name in favour of template.Ref
-Docs @ v0.12.0 -Examples @ v0.12.0
Switch to UUID for event IDs (#926)
Change the event ID representation from a 5 character random string to a UUID.
Add support for custom object to triggers eventlistener (#958)
Introduced new field customResource to support Knative Service for EventListener
apiVersion: triggers.tekton.dev/v1alpha1
kind: EventListener
metadata:
name: github-listener-interceptor-customresource
spec:
...
resources:
customResource:
apiVersion: serving.knative.dev/v1
kind: Service
metadata:
spec:
template:
spec:
serviceAccountName: tekton-triggers-example-sa
containers:
- resources:
requests:
memory: "64Mi"
cpu: "250m"
limits:
memory: "128Mi"
cpu: "500m"
Validate Event Body for Json Format (#969)
We now throw http.BadRequest status code(400) if event payload isn't json.
In current release:
Remove deprecated field template.Name in favour of template.Ref (#919)
Deprecated field template.Name in has been removed in favor of template.Ref
Switch to UUID for event IDs (#926)
Change the event ID representation from a 5 character random string to a UUID.
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.12.0/release.yaml
Thanks to these contributors who contributed to v0.12.0!
Extra shout-out for awesome release notes:
-Docs @ v0.11.2 -Examples @ v0.11.2
-Docs @ v0.11.2 -Examples @ v0.11.2
The EventListener did not have knowledge of which namespace Triggers was installed in. Instead it always assumed it was tekton-pipelines leading to the bug described in #923.
This PR fixes by having the Reconciler send the installation namespace as a environment variable set on the EventListener's pod.
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.11.2/release.yaml
Thanks to these contributors who contributed to v0.11.2!
Revert removal of template.Name field and handle Deprecation of template.Name field
-Docs @ v0.11.1 -Examples @ v0.11.1
NOTE: Please check v0.11.0 release notes for all the new features and bug fixes
Revert removal of template.Name field and handle Deprecation of template.Name field (#912)
Deprecate template.Name in favor of template.Ref
Note:
v0.11.0 and directly upgrade to v0.11.1 from v0.10.2 to avoid issue with template.Name field.v0.11.1 will get all the features and bug fixes from v0.11.0. Please check v0.11.0 release notes for all the new features and bug fixes.kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.11.1/release.yaml
Thanks to these contributors who contributed to v0.11.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
Remove deprecated spec style embedded bindings (#900) BREAKING CHANGE: The Spec field has been removed from the TriggerSpecBinding.
-Docs @ v0.11.0 -Examples @ v0.11.0
Migrate GitLab, BitBucket, GitHub interceptors to new interface (#832)
Implement marshalJSON CEL function (#842)
New CEL function marshalJSON that can encode a JSON object or array to a string.
Add a server for serving core interceptors (#858)
Add a HTTP handler for serving core interceptors and this packages all 4 core interceptors into a single HTTP server. Each interceptor is available at a different path e.g. /cel for CEL etc.
Add SecurityContext to reconciled Deployment (#862)
Add a security context on event listener deployments to prevent issues with restrictive default PSPs.
Add flag to disable security context on EL Deployment (#865)
Add a flag to disable SecurityContext on the reconciled eventlistener Deployment
Change InterceptorRequest.Body to string (#877)
InterceptorRequest.Body is now of type string. No immediate action is required but once #271 is fully implemented, interceptor authors will have to parse the Body separately as a JSON object.
Move core interceptors to their own server (#878)
Deprecate PodTemplate and ServiceType in favour of Resource (#897)
Deprecate PodTemplate and ServiceType in favour of Resource.
Spec field has been removed from the TriggerSpecBinding.Fix example SA permissions (#848)
The example service account has been updated to include access to clustertriggerbindings.
refactor: Do not use %w unless in fmt.Errorf (#855)
Merge extensions into body for webhook interceptors (#859)
Extensions added by a CEL Interceptor will be passed on to webhook interceptors by merging the extension fields into the event body under a extensions field. See docs/eventlisteners.md for more details.
Bind admin role so that SA can use PSP (#863)
Update tekton eventlistener portname owing to istio naming conventions (#880)
Event listener port should be called http-listener instead of listener.
Update TLS example (#885)
Use system.DefaultNamespace for interceptor urls (#891)
Add core interceptors image to created images (#895)
Use a test helper for rawExtension objects in tests (#843)
Remove deprecated fields podTemplate and serviceType (#852)
Use own Status type for InterceptorResponse (#854)
Update CRD to apiextensions.k8s.io/v1 (#872)
Add @savitaashture as an OWNER 🎉 (#873)
Refactor flags to improve unit tests (#876)
Pass a config struct to the reconciler instead of using flags directly.
Fix behaviour which allows EL ports to be configured (#881)
Refactor sink test (#882)
Update service account name for TLS example (#884)
Add https-listener service port name (#887)
Improve the TriggerTemplate message (#899)
Improve the error message when parsing the results of rendering a TriggerTemplate.
Bump knative to release-0.20 and pipeline to v0.20.0 (#903)
This bumps the minimum supported version of kubernetes to 0.17
Add links to versioned docs for v0.10.1 (#851)
Remove mention of dep in dev docs (#866)
Add docs for installing nightly release (#874)
Fixed link in EventListener secure connection docs (#905)
Link fixed in the docs for the EventListener example with secure connection.
Add links to versioned docs for v0.10.2 (#907)
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.11.0/release.yaml
Note: Tekton Triggers v0.11.0 requires Kubernetes 1.17+ to run.
Thanks to these contributors who contributed to v0.11.0!
Extra shout-out for awesome release notes:
-Docs @ v0.10.2 -Examples @ v0.10.2
-Docs @ v0.10.2 -Examples @ v0.10.2
extensions field. See docs/eventlisteners.md##chaining-interceptors for more details.kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.10.2/release.yaml
Thanks to these contributors who contributed to v0.10.1!
-Docs @ v0.10.1 -Examples @ v0.10.1
-Docs @ v0.10.1 -Examples @ v0.10.1
NOTE: Please check the v0.10.0 release notes for all the new features and bug fixes
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.10.1/release.yaml
Thanks to these contributors who contributed to v0.10.1!
Nothing published for this version
Nothing published for this version
BREAKING CHANGE: CEL overlays now add fields to a new top level extensions field instead of the modifying the incoming event body. TriggerBindings can…
-Docs @ v0.10.0 -Examples @ v0.10.0
Add timestamps in logs (#802):sparkles:
Add timestamp in the logs of the pipelines controller, webhook, and eventlisteners.
Improve the error message when URL form encoding is received (#806)
The GitHub interceptor now detects form-encoded hook requests and returns an explicit error for this case rather than the generic JSON parsing error.
Allow users to set resources as part of podtemplate (#815) Now trigger allow users to specify their resource information in eventlistener
apiVersion: triggers.tekton.dev/v1alpha1
kind: EventListener
metadata:
name: github-listener-interceptor
spec:
...
resources:
kubernetesResource:
spec:
template:
spec:
serviceAccountName: tekton-triggers-github-sa
containers:
- resources:
requests:
memory: "64Mi"
cpu: "250m"
limits:
memory: "128Mi"
cpu: "500m"
Use Listers to fetch data in the Sink(#821)
EventListener ServiceAccounts now need to have "list" and "watch" verbs in addition to "get" for all triggers resources. See examples at https://github.com/tektoncd/triggers//tree/v0.10.0//examples/role-resources/triggerbinding-roles/role.yaml and https://github.com/tektoncd/triggers/tree/v0.10.0//examples/role-resources/clustertriggerbinding-roles/clusterrole.yaml
Add Timeout for EventListener Server (#747)
Add Read, Write, and Idle timeout for connections to the EventListener.
TEP-0022: Switch to immutable input event bodies (#828) Migrate CEL to new Interceptor Interface
Add EventListener Selector For TriggerCRD (#773)
Added Namespace Selector field for EventListener which enables EventListener to serve across the namespace. namespaceSelector field with matchNames need to be provided to enable selector.
namespaceSelector:
matchNames:
- nsName1
- nsName2
If namespace selector is used, the service account for the EventListener will need a clusterRole. See the example at https://github.com/tektoncd/triggers/tree/v0.10.0/examples/selectors/01_rbac.yaml
apiVersion: triggers.tekton.dev/v1alpha1
kind: EventListener
metadata:
name: github-listener-interceptor
spec:
...
resources:
kubernetesResource:
spec:
template:
spec:
serviceAccountName: tekton-triggers-github-sa
containers:
- env:
- name: TLS_CERT
valueFrom:
secretKeyRef:
name: tls-key-secret
key: tls.crt
- name: TLS_KEY
valueFrom:
secretKeyRef:
name: tls-key-secret
key: tls.key
In the current release:
TEP-0022: Switch to immutable input event bodies (#828)
action required: If you are using overlays in the CEL Interceptor, please update your bindings to use $(extensions.<overlay-key>) instead of $(body.<overlay-key>)
BREAKING CHANGE:
CEL overlays now add fields to a new top level extensions field instead of the modifying the incoming event body. TriggerBindings can access values within this new extensions field using $(extensions.<key>) syntax.
Drop escaping of strings in the JSON (#823)
Previously, parameters were escaped as they were being replaced into a TriggerTemplate, by replacing double-quotes " with an escaped version ", this functionality has been removed, as it was breaking quoted strings, and in some cases, rendering the resulting output unparseable.
action required: If you were relying on the escaping, you can retain the old behaviour by adding an annotation to an affected TriggerTemplate, triggers.tekton.dev/old-escape-quotes: "true"
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.10.0/release.yaml
Thanks to these contributors who contributed to v0.10.0!
Extra shout-out for awesome release notes:
-Docs @ v0.9.1 -Examples @ v0.9.1
-Docs @ v0.9.1 -Examples @ v0.9.1
NOTE: Please check the v0.9.0 release notes for all the new features and bug fixes
Allow webhook to create secrets (for TLS certs)
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.9.1/release.yaml
Thanks to these contributors who contributed to v0.9.1!
BREAKING CHANGE: With this change, users cannot specify both name and ref for a single binding. Use ref to refer to a TriggerBinding resource and name…
-Docs @ v0.9.0 -Examples @ v0.9.0
Enhance existing eventlistener to support PodTemplate for Deployment using duck type (#734) :sparkles:
A new field resources has been introduced as part of EventListener spec
apiVersion: triggers.tekton.dev/v1alpha1
kind: EventListener
metadata:
name: github-listener-interceptor
spec:
triggers:
...
resources:
kubernetesResource:
serviceType: NodePort
spec:
template:
metadata:
labels:
key: "value"
annotations:
key: "value"
spec:
serviceAccountName: tekton-triggers-github-sa
nodeSelector:
app: test
tolerations:
- key: key
value: value
operator: Equal
effect: NoSchedule
As of now the resources field supports kubernetesResource which helps us use PodSpecable ducktype. For backward compatibility both ways are supported and resources are optional.
cel-go with string upper and lower-casing. (#766)
Updated version of cel-go with new functionality for upper and lower-casing ASCII strings. e.g. body.upperMsg.lowerAscii()
Adds support for name/value embedded Bindings (#768)
TriggerBindings can now be embedded by using just name/value fields inside a Trigger or a EventListener.
BREAKING CHANGE: With this change, users cannot specify both name and ref
for a single binding. Use ref to refer to a TriggerBinding resource and
name for embedded bindings.
# NEW SYNTAX:
bindings:
- ref: some-name
- name: commit_id # embedded binding
value: "$(body.head_commit_id)"
# OLD SYNTAX:
bindings:
- name: some-name
spec:
params:
- name: commit_id # embedded binding
value: "$(body.head_commit_id)
PodSecurityPolicy Config fixes to allow runnning in restricted envs (#707)
The PodSecurityPolicy configuration was updated so that container must run as non-root, and the RBAC for utilizing the PSP was moved from cluster scoped to namespace scoped to better ensure triggers can not utilize other PSPs unrelated to this project
Add support for embedded trigger templates (#783)
Users can now specify embed a TriggerTemplate spec inside a Trigger.
Use template.ref instead of template.name (#787)
Use template.ref to refer to trigger templates in a Trigger instead of template.name. The name field is deprecated and will be removed in a future release.
Enhance validation code for triggers (#785)
Triggers validation now reports all the error at once with more detailed information.
Use template.ref instead of template.name (#787)
The template.name field is deprecated (in favor of template.ref) and will be removed in a future release.
Adds support for name/value embedded Bindings (#768)
The old syntax for embedded TriggerBindings (using spec.params) is deprecated. Use the new name/value fields instead:
In current release:
Bump Knative/K8s dependencies. (#784)
action required: Users of the generated clients will need to conform to the K8s 1.18 style breaking changes (namely passing context.Context to all calls)
Adds support for name/value embedded Bindings (#768)
BREAKING CHANGE: users cannot specify both name and ref for a single binding. Use ref to refer to a TriggerBinding resource and name for embedded bindings.
remove interceptor cross namespace secret references (#748)
BREAKING CHANGE: any interceptors that attempt to reference a Secret outside of the EventListener's namespace will have to change to have those Secrets reside in the EventListener's namespace.
Apply triggertemplate param default value if triggerbinding param missing from body/header (#761)
Triggers now applies the default value of a trigger template param if it's value cannot be resolved from a TriggerBinding. This is a BREAKING CHANGE. Previously, Triggers would throw an error saying that the binding value could not be resolved (See #568)
Apply triggertemplate param default value if triggerbinding param missing from body/header (#761)
Triggers now applies the default value of a trigger template param if it's value cannot be resolved from a TriggerBinding. This is a BREAKING CHANGE. Previously, Triggers would throw an error saying that the binding value could not be resolved (See #568)
Set runAsUser uid for nonroot distroless image (#789)
Fix inconsistent uid for the controller and webhook deployment, resulting in failure of installing tekton pipeline on minikube (and other platforms.)
Fix Binding test builder to only use ref (#769)
remove interceptor cross namespace secret references (#748)
BREAKING CHANGE: any interceptors that attempt to reference a Secret outside of the EventListener's namespace will have to change to have those Secrets reside in the EventListener's namespace.
Add Clusterrole Aggregate View and Edit for Trigger CRD (#790)
Remove explicit pinning of golang version (#794)
Fix TestTrigger_Error using deterministic inputs (#798)
Add release links to versioned docs for v0.8.1 (#756)
Refactor to not use logger from pipeline (#760)
Use refs instead of name to refer to Bindings (#757)
Un-indent release note blocks in PR template (#763)
Cleanup exported methods which are used in the same package (#764)
Add the pod resource to the test controller (#780)
Update submitter checklist to have release notes block (#786)
Bump pipeline version to v0.16.3 (#767)
Bump Knative/K8s dependencies. (#784)
action required: Users of the generated clients will need to conform to the K8s 1.18 style breaking changes (namely passing context.Context to all calls)
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.9.0/release.yaml
Thanks to these contributors who contributed to v0.9.0!
Nothing published for this version
Nothing published for this version
Nothing published for this version
-Docs @ v0.8.1 -Examples @ v0.8.1
-Docs @ v0.8.1 -Examples @ v0.8.1
If provided replicas value as 0 as part of EventListener spec then a default value 1 will be set by webhook.
Triggers no longer overwrites annotations set on the underlying deployment and service objects.
EventListeners close idle connections after 120 seconds.
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.8.1/release.yaml
Thanks to these contributors who contributed to v0.8.1!
Extra shout-out for awesome release notes:
-Docs @ v0.8.0 -Examples @ v0.8.0
-Docs @ v0.8.0 -Examples @ v0.8.0
This PR adds feasibility to propagate annotations from the EventListener to deployment and services. If there are any custom annotations on services/deployment, then it needs to be added to EventListener annotations, so that those will be propagated otherwise they will be overwritten.
This PR handles proper validation for replicas which are provided as part of EventListener spec. Produce below error if provided replica is invalid Error from server (BadRequest): error when creating "STDIN": admission webhook "validation.webhook.triggers.tekton.dev"
This PR helps to specify TriggerCRD object inside the Eventlistener spec as a reference using triggerRef field, So this way user can create TriggerCRD separately and bind it inside Eventlistener spec.
PR uses genreconciler from knative/pkg to reduce boilerplate code which was required for writing reconciler. Also triggers reconciler now emits K8s events on reconciliation failures.
This PR adds the validation and defaults around TriggerCRD.
In current release:
Switch trigger sa based auth to impersonate (#705)
Switch trigger sa ref from global to namespace scoped (#704)
The optional EventListenerTrigger based level of authentication for creating Tekton object has had its ServiceAccount reference changed from an ObjectReference to a string ServiceAccountName, effectively enforcing that the ServiceAccount be in the same namespace as the EventListenerTrigger.
Fix Incorrect number of response for Forbidden error (#673)
Use Kaniko instead of img in the tutorial to fix permission issue (#701)
Cleanup Reconciler Tests in order to pick up Genreconciler updates (#706)
Fix update deployment when there is a change in replicas (#715)
Add basic syntactical parsing of CEL filters and expressions (#745)
Perform simple syntax checking of CEL filter and overlays in the Webhook validator, perfunctory syntax validation of the expressions in the interceptor but it won't detect logical errors (expressions that rely on JSON bodies).
Add TestBuilder for TriggerCRD (#680)
Use ko:// prefix for all images (#692)
Adds ko:// scheme to images used by ko (dev only)
Fix GitHub example bindings (#694)
Add interceptor to processTriggerSpec (#695)
This is an experimental feature and its a part of creating CLI for TriggerRun. It contains the parts that add an interceptor to processTriggerSpec, updates readHTTP to print out resources, and trigger function to run Trigger CLI.
Fix URL in Release Cheat Sheet (#696)
Change tekton.dev to triggers.tekton.dev for e2e Tests (#702)
Add createResource in TriggerRun CLI (#708)
This is also an experimental feature for TriggerRun CLI
Add khrm@ as an OWNER (#710) :heart"
Mark some command tests as end-to-end (#719)
Use another NodeSelector value in EventListener tests (#720)
This change helps to run e2e on non amd64 architecture (s390x, ppc64le, etc).
Change Eventlistener Trigger Binding and Trigger Template type to TriggerSpec (#740)
Fix release cheat sheet doc (#693)
Add namespace to the commands in Nginx ingress doc (#698)
Add links to versioned docs for v0.7.0 (#703)
Update eventlistener doc to include eventlistener responsibility (#721)
Added information about the responsibility of Eventlistener.
Update README for Bitbucket example (#724)
Update triggertemplate doc and example to use tt.params (#725)
Clarify Bitbucket and Github HMAC generation instruction in example (#728)
Updates to the happy path readme(s) (#730)
Remove vendor specific cluster setup instructions (#739)
Update link to happy path (#742)
Update pull request template for release-note (#743)
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.8.0/release.yaml
NOTE: Due to #750, you will have to manually add replicas: 1 to your EL spec before applying the upgrade
Thanks to these contributors who contributed to v0.8.0!
Extra shout-out for awesome release notes:
:heart_eyes: @savitaashture :heart_eyes: @piyush-garg :heart_eyes: @gabemontero :heart_eyes: @dibyom :heart_eyes: @khrm :heart_eyes: @bigkevmcd
Remove deprecated $(params) (#690) This is a breaking change as this PR remove complete support of $(params) and moved to $(tt.params) in order to avo…
This PR will add a CEL function named parseYAML that can parse a YAML string into a map of strings to dynamic values Syntax: .parseYAML() -> map<string, dyn>
This adds a requestURL key to the CEL expression context. For example, requestURL.parseURL().path would get the path of the incoming request URL.
Improve the error messages around parsing CEL expressions. This improves the granularity of the error messages that are returned by evaluating expressions. It also improves the error message when parsing the hook body when creating the evaluation environment.
This adds support for marshaling bool values, and maps if they're used as the values of expressions in a CEL overlay.
Add nodeSelector and replicas feature to eventListener. With this, user could schedule eventListener pod to the node with specific label. Also, if needed, user could specify the number of replicas in yaml file.
Webhook Interceptors can parse the EventListener-Request-URL if they want to extract parameters from the original request URL being handled by the EventListener.
The EventListener was referring to the Binding via name instead of ref. Also, run the getting-started examples as part of the e2e YAML tests. While this won't catch all issues with the examples, it should catch obvious syntax issues like this one.
Fix a bug in the sink where is not passing the URL through to the incoming requests.
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.7.0/release.yaml
Thanks to these contributors who contributed to v0.7.0!
Extra shout-out for awesome release notes:
-Docs @ v0.6.1 -Examples @ v0.6.1
-Docs @ v0.6.1 -Examples @ v0.6.1
Fix bug marshaling list values from a CEL expression, which was causing panics.
The CEL function compareSecret now returns a boolean value, which makes it work in multiple logical comparisons in a filter.
The marshaled JSON output is flaky, this ensures that it matches after parsing.
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.6.1/release.yaml
Thanks to these contributors who contributed to v0.6.1!
Variable interpolation in TriggerTemplates using $(params) has been deprecated in favor of using $(tt.params)
-Docs @ v0.6.0 -Examples @ v0.6.0
Add URL parsing to CEL expressions. (#591)
This adds a new function parseURL to the CEL expression library.
This will act on a string, and parse it into a map which can be accessed from the remainder of the expression.
For example, 'https://example.com/testing#test'.parseURL().fragment == 'test'
Add BitBucket Interceptor with examples and README (#578)
Adds a new core interceptor for webhooks from Bitbuckert. Check out the docs and examples for more information
Add extra columns for EventListeners (#614)
EventListeners now display the status.address.url and Available status.Condition as additional fields when listed with kubectl get
Modify spec params to avoid confusion between resourcetemplates and triggertemplate params (#589)
Variable interpolation support in TriggerTemplate now uses the form $(tt.params.<paramName>) instead of $(params.<paramName>) in order to reduce confusion with Pipeline variable interpolation syntax. To maintain backwards compatibility, the $(params.<paramName>) syntax continues to be supported but will be removed in a future release. Users are advised to start using $(tt.params) in their TriggerTemplates. See #589 for more information and examples.
Add tolerations to eventlistener (#597)
Adds a podTemplate.tolerations field to the EventListener spec that allows users to customize the EventListener Pod.
See the docs for details.
Variable interpolation in TriggerTemplates using $(params) has been deprecated in favor of using $(tt.params)
Variable interpolation support in TriggerTemplate now uses the form $(tt.params.<paramName>) instead of $(params.<paramName>) in order to reduce confusion with Pipeline variable interpolation syntax. To maintain backwards compatibility, the $(params.<paramName>) syntax continues to be supported but will be removed in a future release. Users are advised to start using $(tt.params) in their TriggerTemplates. See #589 for more information and examples.
In current release:
Triggers no longer supports referring to TriggerBindings in a EventListener using the name field. Use the ref field instead. (#603)
The name field was depreacted in favor of the ref field in Triggers v0.5.0. To ease the upgrade, Triggers would automatically set the ref field to the value of the name field. Starting this release, Triggers will stop setting the default automatically. See #603 and #548 for more details
Publish both tagged and untagged images for releases (#598)
All triggers release images are now tagged with the release version.
Cache trigger secrets for the duration of request (with tests) (#595)
Cache Kubernetes secret refs for each EventListener webhook, using the cached value to process each trigger
Ensure that decodeB64 returns a String rather than Bytes. (#609)
Fix formatting of version in config (#623)
Fix the Data Race in portforward e2e test of EventListener (#631)
name field to refer to a TriggerBinding to use a ref field insteadkubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.6.0/release.yaml
Thanks to these contributors who contributed to v0.6.0!
Extra shout-out for awesome release notes:
Nothing published for this version
The name field in triggers.bindings within an EventListener has been deprecated in favor of the ref field and will be removed in a future release. See…
kubectl -n tekton-pipelines delete deployments tekton-triggers-controller tekton-triggers-webhook
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.5.0/release.yaml
This is an overview of new changes. For all changes, see Milestone.
/live. https://github.com/tektoncd/triggers/pull/467app.kubernetes.io labels. https://github.com/tektoncd/triggers/pull/556https://github.com/tektoncd/triggers/pull/556 Tekton Trigger controllers will need to be updated (by deleting and creating the deployments) in order to apply the new labels:
kubectl -n tekton-pipelines delete deployments tekton-triggers-controller tekton-triggers-webhook
kubectl apply -f https://storage.googleapis.com/tekton-releases/triggers/previous/v0.5.0/release.yaml
https://github.com/tektoncd/triggers/pull/532 removes the undocumented and unsupported type field from TriggerTemplate params. If you were using the field in your TriggerTemplate, you'll have to delete the resource, and recreate it after deleting the type field.
https://github.com/tektoncd/triggers/issues/472 requires users to update to new cel-go strings syntax.
It brings in the upstream cel-go Strings library, with a number of additional methods in your CEL expressions, see below for more information:
This also standardises the CEL extensions as "instance overloads", which changes the way they are called:
old style:
expression: "truncate(body.pull_request.head.sha, 7)"
new style:
expression: "body.pull_request.head.sha.truncate(7)"
The new functions that the Strings extension library brings in are:
name field in triggers.bindings within an EventListener has been deprecated in favor of the ref field and will be removed in a future release. See #371 for details.Thanks to these contributors who contributed to v0.5.0!
Nothing published for this version
Switch API group for triggers to triggers.tekton.dev (#497) All Triggers resources now use the triggers.tekton.dev API Group. BREAKING CHANGE: Users w…
-Docs @ v0.4.0 -Examples @ v0.4.0
compareSecrets for securely comparing strings to secrets in CEL expressions.In current release:
Switch API group for triggers to triggers.tekton.dev (#497) All Triggers resources now use the triggers.tekton.dev API Group. BREAKING CHANGE: Users will have to delete and recreate resources after updating the API Group. Users will also have to update their EventListener Role resource to point to the triggers.tekton.dev API Group for Triggers resources.
Update pipeline version to 0.11-rc1 (#469) Triggers now requires kubernetes version 1.15 or higher.
Once you have updated your cluster with the 0.4.0 release:
First, get all existing Trigger resources and store the yaml locally if you do not already have them locally.
Next, delete all of the existing Triggers resources:
kubectl delete triggertemplates --all
kubectl delete triggerbindings --all
kubectl delete clustertriggerbindings --all
kubectl delete eventlisteners --all
Update the Role resource used by each EventListener's ServiceAccount to use the new APIGroups
Change the apiVersion field to triggers.tekton.dev for each resource yaml and reapply the yaml
Delete the old CRDs:
kubectl delete crd triggerbindings.tekton.dev
kubectl delete crd clustertriggerbindings.tekton.dev
kubectl delete crd triggertemplates.tekton.dev
kubectl delete crd eventlisteners.tekton.dev
If you are using the Triggers Client in your go code, then update TriggersClient.TektonV1alpha1() to TriggersClient.TriggersV1alpha1() (here is a link to the relevant clientset code).
Thanks to these contributors who contributed to v0.4.0!
Extra shout-out for awesome release notes:
Switch API group for triggers to triggers.tekton.dev (#497) All Triggers resources now use the triggers.tekton.dev API Group. BREAKING CHANGE: Users w…
-Docs @ v0.4.0-rc1 -Examples @ v0.4.0-rc1
compareSecrets for securely comparing strings to secrets in CEL expressions.In current release:
Switch API group for triggers to triggers.tekton.dev (#497) All Triggers resources now use the triggers.tekton.dev API Group. BREAKING CHANGE: Users will have to delete and recreate resources after updating the API Group. Users will also have to update their EventListener Role resource to point to the triggers.tekton.dev API Group for Triggers resources.
Update pipeline version to 0.11-rc1 (#469) Triggers now requires kubernetes version 1.15 or higher.
Once you have updated your cluster with the 0.4.1-rc1 release:
First, get all existing Trigger resources and store the yaml locally if you do not already have them locally.
Next, delete all of the existing Triggers resources:
kubectl delete triggertemplates --all
kubectl delete triggerbindings --all
kubectl delete clustertriggerbindings --all
kubectl delete eventlisteners --all
Update the Role resource used by each EventListener's ServiceAccount to use the new APIGroups
Change the apiVersion field to triggers.tekton.dev for each resource yaml and reapply the yaml
Delete the old CRDs:
kubectl delete crd triggerbindings.tekton.dev
kubectl delete crd clustertriggerbindings.tekton.dev
kubectl delete crd triggertemplates.tekton.dev
kubectl delete crd eventlisteners.tekton.dev
If you are using the Triggers Client in your go code, then update TriggersClient.TektonV1alpha1() to TriggersClient.TriggersV1alpha1() (here is a link to the relevant clientset code).
Thanks to these contributors who contributed to v0.4.0-rc1!
Extra shout-out for awesome release notes:
Nothing published for this version
Nothing published for this version
-Docs @ v0.3.1 -Examples @ v0.3.1
-Docs @ v0.3.1 -Examples @ v0.3.1
Thanks to these contributors who contributed to v0.3.1!
BREAKING CHANGE: Interceptors now receive HTTP POST requests regardless of the type of request the EventListener receives.
-Docs @ v0.3.0 -Examples @ v0.3.0
Use tekton instead of all as categories 🎿(#360)
Remove the category all for our CRD and have a tekton category that is shared with other tektoncd projects.
Add support for ClusterTriggerBinding (#358)
New ClusterTriggerBinding resource which is similar to TriggerBinding but cluster-scoped.
To use a ClusterTriggerBinding in an EventListener's bindings, you must specify the kind field as ClusterTriggerBinding. By default, the kind field is TriggerBinding, and it can be omitted.
CEL Interceptor improvements
Add support for adding additional fields to the body. (#329)
The CEL Interceptor can now add new derived fields to the request body that can be picked up in a TriggerBinding.
Add support for splitting strings to CEL expressions. (#411)
This adds a CEL expression function for splitting strings.
Add CEL function canonical. (#410)
This adds a new canonical function on the header, making it easy to fetch a request header by name.
Add decodeb64 function to CEL expressions. (#404)
This adds a decodeb64 function to the CEL expressions usable by the overlay mechanism.
Add Liveness Probe for EventListener Deployment (#432)
Add a Liveness Probe for EventListener Deployment at URL /live
Add Version Label to Triggers Deployment & Service (#428)
Adds the version and triggers.tekton.dev/release labels with version information.
In current release:
Ensure Interceptor request uses HTTP POST. (#438)
BREAKING CHANGE: Interceptors now receive HTTP POST requests regardless of the type of request the EventListener receives.
validate ObjectMetadata for TriggerTemplate (#435)
TriggerTemplates must have a metadata field.
Remove deprecated binding (#424)
Remove deprecated Interceptor (#425)
Remove deprecated Params field from EventListener (#444)
Thanks to these contributors who contributed to v0.3.0!
-Docs @ v0.2.1 -Examples @v0.2.1
-Docs @ v0.2.1 -Examples @v0.2.1
get, list, and watch ConfigMaps. If you are using GitHub/GitLab interceptors to do payload verification, the ServiceAccount needs get on Secrets as well.params into a TriggerBinding.Thanks to these contributors who contributed to v0.2.1!
Nothing published for this version
One column per quarter.