From d39e0a5eaeab468e4250698724b637b0c90c7b72 Mon Sep 17 00:00:00 2001 From: Allon Mureinik Date: Sun, 27 Jul 2025 18:41:44 +0300 Subject: [PATCH] doc: fix the version tls.DEFAULT_CIPHERS was added 42be7f6a0335c396810be91c3f3724007029f83d (originally included in 19.8.0 and later backported to 18.16.0) added documentation on how to use `tls.DEFAULT_CIPHERS`. However, that commit added the documentation with the version specified as `REAPLCEME`, causing the published documentation to state that `tls.DEFAULT_CIPHERS` was added in 19.8.0 and 18.16.0, which is incorrect - that commit states that `tls.DEFAULT_CIPHERS` already existed, and the only thing it added was an explanation on how to use it. In fact, by examining the git log, it can be seen that `tls.DEFAULT_CIPHERS` was added by commit af80e7bc6e6f33c582eb1f7d37c7f5bbe9f910f7, which was included in 0.11.3. Fixes: https://github.com/nodejs/node/issues/59246 --- doc/api/tls.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/doc/api/tls.md b/doc/api/tls.md index 7be5ee7fb29a56..bc7a735d571365 100644 --- a/doc/api/tls.md +++ b/doc/api/tls.md @@ -2427,9 +2427,7 @@ added: v11.4.0 ## `tls.DEFAULT_CIPHERS` * Type: {string} The default value of the `ciphers` option of