From b190f6b9986f63f298bda209417d4daae9538a9e Mon Sep 17 00:00:00 2001
From: Julien Pivotto <291750+roidelapluie@users.noreply.github.com>
Date: Tue, 28 Oct 2025 16:32:47 +0100
Subject: [PATCH] _content/doc/security/fuzz: update OSS-Fuzz documentation

Replace outdated future reference with current information and link to
OSS-Fuzz for continuous fuzzing setup.

Signed-off-by: Julien Pivotto <291750+roidelapluie@users.noreply.github.com>
---
 _content/doc/security/fuzz/index.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/_content/doc/security/fuzz/index.md b/_content/doc/security/fuzz/index.md
index 4eb1a16984..82b1eae22f 100644
--- a/_content/doc/security/fuzz/index.md
+++ b/_content/doc/security/fuzz/index.md
@@ -85,8 +85,9 @@ issues that would already be caught by an existing test.
 
 Note that it is up to you to decide how long to run fuzzing. It is very possible
 that an execution of fuzzing could run indefinitely if it doesn't find any errors.
-There will be support to run these fuzz tests continuously using tools like OSS-Fuzz
-in the future, see [Issue #50192](/issue/50192).
+You can run these fuzz tests continuously using tools like OSS-Fuzz. See
+[OSS-Fuzz](https://google.github.io/oss-fuzz/) for more information on setting up
+continuous fuzzing for your project.
 
 **Note:** Fuzzing should be run on a platform that supports coverage
 instrumentation (currently AMD64 and ARM64) so that the corpus can meaningfully