From 5ebc79fcd690f4e44708e0121aae57a752f0ad25 Mon Sep 17 00:00:00 2001
From: Leonardo Di Giovanna <41296180+ekoops@users.noreply.github.com>
Date: Thu, 8 Jan 2026 12:11:20 +0100
Subject: [PATCH] fix(proposals): specify correct stable falco version

Updated the stable Falco version from 0.43.0 to 0.42.1 in the deprecation policy section.

Signed-off-by: Leonardo Di Giovanna <41296180+ekoops@users.noreply.github.com>
---
 ...20251215-legacy-bpf-grpc-output-gvisor-engine-deprecation.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/proposals/20251215-legacy-bpf-grpc-output-gvisor-engine-deprecation.md b/proposals/20251215-legacy-bpf-grpc-output-gvisor-engine-deprecation.md
index 29f304ce..b7372665 100644
--- a/proposals/20251215-legacy-bpf-grpc-output-gvisor-engine-deprecation.md
+++ b/proposals/20251215-legacy-bpf-grpc-output-gvisor-engine-deprecation.md
@@ -102,7 +102,7 @@ The deprecation of these components introduces user-facing changes that must be
 deprecation policy for "non-backward compatible user-facing changes" (see
 [20231220-features-adoption-and-deprecation.md#deprecation-policy](./20231220-features-adoption-and-deprecation.md#deprecation-policy)).
 
-All components are stable, and given that the current stable Falco version is `0.43.0` (ante `1.0.0`), the minimum
+All components are stable, and given that the current stable Falco version is `0.42.1` (ante `1.0.0`), the minimum
 deprecation period length is 1 release: this means that components cannot be removed before Falco `0.44.0`.
 
 At high level, the action plan is to inform users, during the deprecation period, about the deprecation: this is