From 5e1fbfd3c2a5c89891183ac82c07ce724f8c35e5 Mon Sep 17 00:00:00 2001
From: Filip Skokan <panva.ip@gmail.com>
Date: Wed, 17 Jun 2026 16:48:54 +0200
Subject: [PATCH] doc: add stability status to `crypto.setEngine`

It's been doc-deprecated (DEP0183) for a while.
---
 doc/api/crypto.md | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/doc/api/crypto.md b/doc/api/crypto.md
index 1c64a06dbf27..d3175a9a4d6a 100644
--- a/doc/api/crypto.md
+++ b/doc/api/crypto.md
@@ -6513,11 +6513,14 @@ changes:
     description: Custom engine support in OpenSSL 3 is deprecated.
 -->
 
+> Stability: 0 - Deprecated
+
 * `engine` {string}
 * `flags` {crypto.constants} **Default:** `crypto.constants.ENGINE_METHOD_ALL`
 
 Load and set the `engine` for some or all OpenSSL functions (selected by flags).
-Support for custom engines in OpenSSL is deprecated from OpenSSL 3.
+Use of this API is deprecated because custom engine support has been deprecated
+since OpenSSL 3.
 
 `engine` could be either an id or a path to the engine's shared library.