doc: fix metadata for v11.8.0 doc changes

Refs: https://github.com/nodejs/node/commit/641de82404d5fa381053e0f5abd522c7f5881e5a

PR-URL: https://github.com/nodejs/node/pull/25709
Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Myles Borins <myles.borins@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>

4 files changed, 14 insertions, 14 deletions

diff --git a/doc/api/cli.md b/doc/api/cli.md
index 5d34d476e4..857f7de6ce 100644
--- a/doc/api/cli.md
+++ b/doc/api/cli.md
@@ -77,21 +77,21 @@ $ source node_bash_completion
 
 ### `--diagnostic-report-directory=directory`
 <!-- YAML
-added: v11.7.0
+added: v11.8.0
 -->
 
 Location at which the report will be generated.
 
 ### `--diagnostic-report-filename=filename`
 <!-- YAML
-added: v11.7.0
+added: v11.8.0
 -->
 
 Name of the file to which the report will be written.
 
 ### `--diagnostic-report-on-fatalerror`
 <!-- YAML
-added: v11.7.0
+added: v11.8.0
 -->
 
 Enables the report to be triggered on fatal errors (internal errors within
@@ -102,7 +102,7 @@ consumption etc. to reason about the fatal error.
 
 ### `--diagnostic-report-on-signal`
 <!-- YAML
-added: v11.7.0
+added: v11.8.0
 -->
 
 Enables report to be generated upon receiving the specified (or predefined)
@@ -111,7 +111,7 @@ The signal to trigger the report is specified through `--diagnostic-report-signa
 
 ### `--diagnostic-report-signal=signal`
 <!-- YAML
-added: v11.7.0
+added: v11.8.0
 -->
 
 Sets or resets the signal for report generation (not supported on Windows).
@@ -119,7 +119,7 @@ Default signal is `SIGUSR2`.
 
 ### `--diagnostic-report-uncaught-exception`
 <!-- YAML
-added: v11.7.0
+added: v11.8.0
 -->
 
 Enables report to be generated on un-caught exceptions, if
@@ -128,7 +128,7 @@ conjunction with native stack and other runtime environment data.
 
 ### `--diagnostic-report-verbose`
 <!-- YAML
-added: v11.7.0
+added: v11.8.0
 -->
 
 Flag that enables additional information to be printed during report generation.
@@ -150,7 +150,7 @@ Enable experimental ES module support and caching modules.
 
 ### `--experimental-policy`
 <!-- YAML
-added: v11.7.0
+added: v11.8.0
 -->
 
 Use the specified file as a security policy.
@@ -164,7 +164,7 @@ Enable experimental top-level `await` keyword support in REPL.
 
 ### `--experimental-report`
 <!-- YAML
-added: v11.7.0
+added: v11.8.0
 -->
 
 Enable experimental diagnostic report feature.
diff --git a/doc/api/policy.md b/doc/api/policy.md
index fce290c049..be7ea3480b 100644
--- a/doc/api/policy.md
+++ b/doc/api/policy.md
@@ -1,6 +1,6 @@
 # Policies
 
-<!--introduced_in=v11.7.0-->
+<!--introduced_in=v11.8.0-->
 <!-- type=misc -->
 
 > Stability: 1 - Experimental
diff --git a/doc/api/process.md b/doc/api/process.md
index 80080456d9..f471a32f94 100644
--- a/doc/api/process.md
+++ b/doc/api/process.md
@@ -1662,7 +1662,7 @@ relied upon to exist.
 
 ### process.report.getReport([err])
 <!-- YAML
-added: v11.7.0
+added: v11.8.0
 -->
 
 * `err` {Object}
@@ -1682,7 +1682,7 @@ at [report documentation][].
 
 ### process.report.setDiagnosticReportOptions([options]);
 <!-- YAML
-added: v11.7.0
+added: v11.8.0
 -->
 
 Set the runtime configuration of diagnostic report data capture. Upon invocation
@@ -1731,7 +1731,7 @@ at [report documentation][].
 
 ### process.report.triggerReport([filename][, err])
 <!-- YAML
-added: v11.7.0
+added: v11.8.0
 -->
 
 * `filename` {string} The file to write into. The `filename` should be
diff --git a/doc/api/tls.md b/doc/api/tls.md
index bea4aecaa6..fb903fc114 100644
--- a/doc/api/tls.md
+++ b/doc/api/tls.md
@@ -1023,7 +1023,7 @@ being issued by trusted CA (`options.ca`).
 <!-- YAML
 added: v0.11.3
 changes:
-  - version: v11.7.0
+  - version: v11.8.0
     pr-url: https://github.com/nodejs/node/pull/25517
     description: The `timeout` option is supported now.
   - version: v8.0.0