github.com/fluxcd/notification-controller/api
The GitOps Toolkit event forwarder and notification dispatcher
View on Github
Activity
- Latest release
- 6d ago
- Total releases
- 64
- Cadence
- ~22 days
- Last 12 months
- 12
Reach
- Stars
- 182
Details
- First release
- Sep 11, 2020
| Version | Released | |
|---|---|---|
v1.10.0
minor
|
v1.10.0
minor
Dependencies (2)
|
|
v1.9.4
patch
|
v1.9.4
patch
Dependencies (3)
|
|
v1.9.3
patch
|
v1.9.3
patch
Dependencies (3)
|
|
v1.9.2
minor
|
v1.9.2
minor
Dependencies (3)
|
|
v1.9.1
patch
|
v1.9.1
patch
Dependencies (3)
|
|
v1.9.0
minor
|
v1.9.0
minor
Dependencies (3)
|
|
v1.8.4
patch
|
v1.8.4
patch
Dependencies (3)
|
|
v1.8.3
patch
|
v1.8.3
patch
Dependencies (3)
|
|
v1.8.2
patch
|
v1.8.2
patch
Dependencies (3)
|
|
v1.8.1
minor
|
v1.8.1
minor
Dependencies (3)
|
|
v1.8.0
minor
|
v1.8.0
minor
Dependencies (3)
|
|
v1.7.5
patch
|
v1.7.5
patch
Dependencies (3)
|
|
v1.7.4
minor
|
v1.7.4
minor
Dependencies (3)
|
|
v1.7.3
patch
|
v1.7.3
patch
Dependencies (3)
|
|
v1.7.2
patch
|
v1.7.2
patch
Dependencies (3)
|
|
v1.7.1
patch
|
v1.7.1
patch
Dependencies (3)
|
|
v1.7.0
minor
|
v1.7.0
minor
Dependencies (3)
|
|
v1.6.0
minor
|
v1.6.0
minor
Dependencies (3)
|
|
v1.5.0
minor
|
v1.5.0
minor
Dependencies (3)
|
|
v1.4.0
minor
|
v1.4.0
minor
Dependencies (3)
|
|
v1.3.0
minor
|
v1.3.0
minor
Dependencies (3)
|
|
v1.2.4
patch
|
v1.2.4
patch
Dependencies (3)
|
|
v1.2.2
patch
|
v1.2.2
patch
Dependencies (3)
|
|
v1.2.1
patch
|
v1.2.1
patch
Dependencies (3)
|
|
v1.2.0
minor
|
v1.2.0
minor
Dependencies (3)
|
|
v1.1.0
major
|
v1.1.0
major
Dependencies (3)
|
|
v1.0.0-rc.4
pre
|
v1.0.0-rc.4
pre
Dependencies (3)
|
|
v1.0.0-rc.1
pre
|
v1.0.0-rc.1
pre
Dependencies (3)
|
|
v0.32.0
minor
|
v0.32.0
minor
Dependencies (3)
|
|
v0.31.0
minor
|
v0.31.0
minor
Dependencies (3)
|
|
v0.30.2
patch
|
v0.30.2
patch
Dependencies (3)
|
|
v0.30.1
patch
|
v0.30.1
patch
Dependencies (3)
|
|
v0.30.0
minor
|
v0.30.0
minor
Dependencies (3)
|
|
v0.29.1
patch
|
v0.29.1
patch
Dependencies (3)
|
|
v0.29.0
minor
|
v0.29.0
minor
Dependencies (3)
|
|
v0.28.0
minor
|
v0.28.0
minor
Dependencies (3)
|
|
v0.27.0
minor
1 CVE
CVE-2022-39272
GO-2022-1071
BIT-flux-2022-39272
BIT-kustomize-2022-39272
GHSA-f4p5-x4vc-mh4v
Oct 28, 2022
Denial of service in flux controllers in github.com/fluxcd modules Flux controllers are vulnerable to a denial of service attack. Users that have permissions to change Flux's objects, either through a Flux source or directly within a cluster, can provide invalid data to fields .spec.interval or .spec.timeout (and structured variations of these fields), causing the entire object type to stop being processed. The issue has two root causes: a) the Kubernetes type metav1.Duration is not fully compatible with the Go type time.Duration as explained in https://github.com/kubernetes/apimachinery/issues/131, and b) a lack of validation within Flux to restrict allowed values. Fixed in
0.28.0
References
Updated Feb 04, 2026 · Source: OSV.dev |
v0.27.0
minor
Dependencies (3)
|
|
v0.25.2
patch
1 CVE
CVE-2022-39272
GO-2022-1071
BIT-flux-2022-39272
BIT-kustomize-2022-39272
GHSA-f4p5-x4vc-mh4v
Oct 28, 2022
Denial of service in flux controllers in github.com/fluxcd modules Flux controllers are vulnerable to a denial of service attack. Users that have permissions to change Flux's objects, either through a Flux source or directly within a cluster, can provide invalid data to fields .spec.interval or .spec.timeout (and structured variations of these fields), causing the entire object type to stop being processed. The issue has two root causes: a) the Kubernetes type metav1.Duration is not fully compatible with the Go type time.Duration as explained in https://github.com/kubernetes/apimachinery/issues/131, and b) a lack of validation within Flux to restrict allowed values. Fixed in
0.28.0
References
Updated Feb 04, 2026 · Source: OSV.dev |
v0.25.2
patch
Dependencies (3)
|
|
v0.25.1
patch
1 CVE
CVE-2022-39272
GO-2022-1071
BIT-flux-2022-39272
BIT-kustomize-2022-39272
GHSA-f4p5-x4vc-mh4v
Oct 28, 2022
Denial of service in flux controllers in github.com/fluxcd modules Flux controllers are vulnerable to a denial of service attack. Users that have permissions to change Flux's objects, either through a Flux source or directly within a cluster, can provide invalid data to fields .spec.interval or .spec.timeout (and structured variations of these fields), causing the entire object type to stop being processed. The issue has two root causes: a) the Kubernetes type metav1.Duration is not fully compatible with the Go type time.Duration as explained in https://github.com/kubernetes/apimachinery/issues/131, and b) a lack of validation within Flux to restrict allowed values. Fixed in
0.28.0
References
Updated Feb 04, 2026 · Source: OSV.dev |
v0.25.1
patch
Dependencies (3)
|
|
v0.25.0
minor
1 CVE
CVE-2022-39272
GO-2022-1071
BIT-flux-2022-39272
BIT-kustomize-2022-39272
GHSA-f4p5-x4vc-mh4v
Oct 28, 2022
Denial of service in flux controllers in github.com/fluxcd modules Flux controllers are vulnerable to a denial of service attack. Users that have permissions to change Flux's objects, either through a Flux source or directly within a cluster, can provide invalid data to fields .spec.interval or .spec.timeout (and structured variations of these fields), causing the entire object type to stop being processed. The issue has two root causes: a) the Kubernetes type metav1.Duration is not fully compatible with the Go type time.Duration as explained in https://github.com/kubernetes/apimachinery/issues/131, and b) a lack of validation within Flux to restrict allowed values. Fixed in
0.28.0
References
Updated Feb 04, 2026 · Source: OSV.dev |
v0.25.0
minor
Dependencies (3)
|
|
v0.24.1
minor
1 CVE
CVE-2022-39272
GO-2022-1071
BIT-flux-2022-39272
BIT-kustomize-2022-39272
GHSA-f4p5-x4vc-mh4v
Oct 28, 2022
Denial of service in flux controllers in github.com/fluxcd modules Flux controllers are vulnerable to a denial of service attack. Users that have permissions to change Flux's objects, either through a Flux source or directly within a cluster, can provide invalid data to fields .spec.interval or .spec.timeout (and structured variations of these fields), causing the entire object type to stop being processed. The issue has two root causes: a) the Kubernetes type metav1.Duration is not fully compatible with the Go type time.Duration as explained in https://github.com/kubernetes/apimachinery/issues/131, and b) a lack of validation within Flux to restrict allowed values. Fixed in
0.28.0
References
Updated Feb 04, 2026 · Source: OSV.dev |
v0.24.1
minor
Dependencies (3)
|
|
v0.23.4
patch
1 CVE
CVE-2022-39272
GO-2022-1071
BIT-flux-2022-39272
BIT-kustomize-2022-39272
GHSA-f4p5-x4vc-mh4v
Oct 28, 2022
Denial of service in flux controllers in github.com/fluxcd modules Flux controllers are vulnerable to a denial of service attack. Users that have permissions to change Flux's objects, either through a Flux source or directly within a cluster, can provide invalid data to fields .spec.interval or .spec.timeout (and structured variations of these fields), causing the entire object type to stop being processed. The issue has two root causes: a) the Kubernetes type metav1.Duration is not fully compatible with the Go type time.Duration as explained in https://github.com/kubernetes/apimachinery/issues/131, and b) a lack of validation within Flux to restrict allowed values. Fixed in
0.28.0
References
Updated Feb 04, 2026 · Source: OSV.dev |
v0.23.4
patch
Dependencies (3)
|
|
v0.23.3
patch
1 CVE
CVE-2022-39272
GO-2022-1071
BIT-flux-2022-39272
BIT-kustomize-2022-39272
GHSA-f4p5-x4vc-mh4v
Oct 28, 2022
Denial of service in flux controllers in github.com/fluxcd modules Flux controllers are vulnerable to a denial of service attack. Users that have permissions to change Flux's objects, either through a Flux source or directly within a cluster, can provide invalid data to fields .spec.interval or .spec.timeout (and structured variations of these fields), causing the entire object type to stop being processed. The issue has two root causes: a) the Kubernetes type metav1.Duration is not fully compatible with the Go type time.Duration as explained in https://github.com/kubernetes/apimachinery/issues/131, and b) a lack of validation within Flux to restrict allowed values. Fixed in
0.28.0
References
Updated Feb 04, 2026 · Source: OSV.dev |
v0.23.3
patch
Dependencies (3)
|
|
v0.23.2
patch
1 CVE
CVE-2022-39272
GO-2022-1071
BIT-flux-2022-39272
BIT-kustomize-2022-39272
GHSA-f4p5-x4vc-mh4v
Oct 28, 2022
Denial of service in flux controllers in github.com/fluxcd modules Flux controllers are vulnerable to a denial of service attack. Users that have permissions to change Flux's objects, either through a Flux source or directly within a cluster, can provide invalid data to fields .spec.interval or .spec.timeout (and structured variations of these fields), causing the entire object type to stop being processed. The issue has two root causes: a) the Kubernetes type metav1.Duration is not fully compatible with the Go type time.Duration as explained in https://github.com/kubernetes/apimachinery/issues/131, and b) a lack of validation within Flux to restrict allowed values. Fixed in
0.28.0
References
Updated Feb 04, 2026 · Source: OSV.dev |
v0.23.2
patch
Dependencies (3)
|
|
v0.23.1
minor
1 CVE
CVE-2022-39272
GO-2022-1071
BIT-flux-2022-39272
BIT-kustomize-2022-39272
GHSA-f4p5-x4vc-mh4v
Oct 28, 2022
Denial of service in flux controllers in github.com/fluxcd modules Flux controllers are vulnerable to a denial of service attack. Users that have permissions to change Flux's objects, either through a Flux source or directly within a cluster, can provide invalid data to fields .spec.interval or .spec.timeout (and structured variations of these fields), causing the entire object type to stop being processed. The issue has two root causes: a) the Kubernetes type metav1.Duration is not fully compatible with the Go type time.Duration as explained in https://github.com/kubernetes/apimachinery/issues/131, and b) a lack of validation within Flux to restrict allowed values. Fixed in
0.28.0
References
Updated Feb 04, 2026 · Source: OSV.dev |
v0.23.1
minor
Dependencies (3)
|
|
v0.22.3
patch
1 CVE
CVE-2022-39272
GO-2022-1071
BIT-flux-2022-39272
BIT-kustomize-2022-39272
GHSA-f4p5-x4vc-mh4v
Oct 28, 2022
Denial of service in flux controllers in github.com/fluxcd modules Flux controllers are vulnerable to a denial of service attack. Users that have permissions to change Flux's objects, either through a Flux source or directly within a cluster, can provide invalid data to fields .spec.interval or .spec.timeout (and structured variations of these fields), causing the entire object type to stop being processed. The issue has two root causes: a) the Kubernetes type metav1.Duration is not fully compatible with the Go type time.Duration as explained in https://github.com/kubernetes/apimachinery/issues/131, and b) a lack of validation within Flux to restrict allowed values. Fixed in
0.28.0
References
Updated Feb 04, 2026 · Source: OSV.dev |
v0.22.3
patch
Dependencies (3)
|
|
v0.22.2
minor
1 CVE
CVE-2022-39272
GO-2022-1071
BIT-flux-2022-39272
BIT-kustomize-2022-39272
GHSA-f4p5-x4vc-mh4v
Oct 28, 2022
Denial of service in flux controllers in github.com/fluxcd modules Flux controllers are vulnerable to a denial of service attack. Users that have permissions to change Flux's objects, either through a Flux source or directly within a cluster, can provide invalid data to fields .spec.interval or .spec.timeout (and structured variations of these fields), causing the entire object type to stop being processed. The issue has two root causes: a) the Kubernetes type metav1.Duration is not fully compatible with the Go type time.Duration as explained in https://github.com/kubernetes/apimachinery/issues/131, and b) a lack of validation within Flux to restrict allowed values. Fixed in
0.28.0
References
Updated Feb 04, 2026 · Source: OSV.dev |
v0.22.2
minor
Dependencies (3)
|
|
v0.17.0
minor
1 CVE
CVE-2022-39272
GO-2022-1071
BIT-flux-2022-39272
BIT-kustomize-2022-39272
GHSA-f4p5-x4vc-mh4v
Oct 28, 2022
Denial of service in flux controllers in github.com/fluxcd modules Flux controllers are vulnerable to a denial of service attack. Users that have permissions to change Flux's objects, either through a Flux source or directly within a cluster, can provide invalid data to fields .spec.interval or .spec.timeout (and structured variations of these fields), causing the entire object type to stop being processed. The issue has two root causes: a) the Kubernetes type metav1.Duration is not fully compatible with the Go type time.Duration as explained in https://github.com/kubernetes/apimachinery/issues/131, and b) a lack of validation within Flux to restrict allowed values. Fixed in
0.28.0
References
Updated Feb 04, 2026 · Source: OSV.dev |
v0.17.0
minor
Dependencies (3)
|
|
v0.16.0
minor
1 CVE
CVE-2022-39272
GO-2022-1071
BIT-flux-2022-39272
BIT-kustomize-2022-39272
GHSA-f4p5-x4vc-mh4v
Oct 28, 2022
Denial of service in flux controllers in github.com/fluxcd modules Flux controllers are vulnerable to a denial of service attack. Users that have permissions to change Flux's objects, either through a Flux source or directly within a cluster, can provide invalid data to fields .spec.interval or .spec.timeout (and structured variations of these fields), causing the entire object type to stop being processed. The issue has two root causes: a) the Kubernetes type metav1.Duration is not fully compatible with the Go type time.Duration as explained in https://github.com/kubernetes/apimachinery/issues/131, and b) a lack of validation within Flux to restrict allowed values. Fixed in
0.28.0
References
Updated Feb 04, 2026 · Source: OSV.dev |
v0.16.0
minor
Dependencies (3)
|
|
v0.15.1
minor
1 CVE
CVE-2022-39272
GO-2022-1071
BIT-flux-2022-39272
BIT-kustomize-2022-39272
GHSA-f4p5-x4vc-mh4v
Oct 28, 2022
Denial of service in flux controllers in github.com/fluxcd modules Flux controllers are vulnerable to a denial of service attack. Users that have permissions to change Flux's objects, either through a Flux source or directly within a cluster, can provide invalid data to fields .spec.interval or .spec.timeout (and structured variations of these fields), causing the entire object type to stop being processed. The issue has two root causes: a) the Kubernetes type metav1.Duration is not fully compatible with the Go type time.Duration as explained in https://github.com/kubernetes/apimachinery/issues/131, and b) a lack of validation within Flux to restrict allowed values. Fixed in
0.28.0
References
Updated Feb 04, 2026 · Source: OSV.dev |
v0.15.1
minor
Dependencies (3)
|