Merge pull request #1040 from nodejs/main

Create a new pull request by comparing changes across two branches

Author: GulajavaMinistudio

CHANGELOG.md

@@ -39,15 +39,17 @@ release.
 </tr>
 <tr>
   <td valign="top">
-<b><a href="doc/changelogs/CHANGELOG_V23.md#23.5.0">23.5.0</a></b><br/>
+<b><a href="doc/changelogs/CHANGELOG_V23.md#23.6.0">23.6.0</a></b><br/>
+<a href="doc/changelogs/CHANGELOG_V23.md#23.5.0">23.5.0</a><br/>
 <a href="doc/changelogs/CHANGELOG_V23.md#23.4.0">23.4.0</a><br/>
 <a href="doc/changelogs/CHANGELOG_V23.md#23.3.0">23.3.0</a><br/>
 <a href="doc/changelogs/CHANGELOG_V23.md#23.2.0">23.2.0</a><br/>
 <a href="doc/changelogs/CHANGELOG_V23.md#23.1.0">23.1.0</a><br/>
 <a href="doc/changelogs/CHANGELOG_V23.md#23.0.0">23.0.0</a><br/>
   </td>
   <td valign="top">
-<b><a href="doc/changelogs/CHANGELOG_V22.md#22.12.0">22.12.0</a></b><br/>
+<b><a href="doc/changelogs/CHANGELOG_V22.md#22.13.0">22.13.0</a></b><br/>
+<a href="doc/changelogs/CHANGELOG_V22.md#22.12.0">22.12.0</a><br/>
 <a href="doc/changelogs/CHANGELOG_V22.md#22.11.0">22.11.0</a><br/>
 <a href="doc/changelogs/CHANGELOG_V22.md#22.10.0">22.10.0</a><br/>
 <a href="doc/changelogs/CHANGELOG_V22.md#22.9.0">22.9.0</a><br/>

doc/api/assert.md

@@ -2551,7 +2551,9 @@ argument.
 ## `assert.partialDeepStrictEqual(actual, expected[, message])`
 
 <!-- YAML
-added: v23.4.0
+added:
+  - v23.4.0
+  - v22.13.0
 -->
 
 > Stability: 1.0 - Early development

doc/api/cli.md

@@ -192,7 +192,9 @@ Error: Access to this API has been restricted
 <!-- YAML
 added: v20.0.0
 changes:
-  - version: v23.5.0
+  - version:
+    - v23.5.0
+    - v22.13.0
     pr-url: https://github.com/nodejs/node/pull/56201
     description: Permission Model and --allow-fs flags are stable.
   - version: v20.7.0
@@ -237,7 +239,9 @@ node --permission --allow-fs-read=/path/to/index.js index.js
 <!-- YAML
 added: v20.0.0
 changes:
-  - version: v23.5.0
+  - version:
+    - v23.5.0
+    - v22.13.0
     pr-url: https://github.com/nodejs/node/pull/56201
     description: Permission Model and --allow-fs flags are stable.
   - version: v20.7.0
@@ -886,7 +890,7 @@ It is possible to run code containing inline types unless the
 ### `--experimental-addon-modules`
 
 <!-- YAML
-added: REPLACEME
+added: v23.6.0
 -->
 
 > Stability: 1.0 - Early development
@@ -1653,7 +1657,9 @@ See [Loading ECMAScript modules using `require()`][].
 <!-- YAML
 added: v22.5.0
 changes:
-  - version: v23.4.0
+  - version:
+    - v23.4.0
+    - v22.13.0
     pr-url: https://github.com/nodejs/node/pull/55890
     description: SQLite is unflagged but still experimental.
 -->
@@ -1665,7 +1671,7 @@ Disable the experimental [`node:sqlite`][] module.
 <!-- YAML
 added: v22.6.0
 changes:
-  - version: REPLACEME
+  - version: v23.6.0
     pr-url: https://github.com/nodejs/node/pull/56350
     description: Type stripping is enabled by default.
 -->
@@ -1802,7 +1808,9 @@ developers may leverage to detect deprecated API usage.
 <!-- YAML
 added: v20.0.0
 changes:
-  - version: v23.5.0
+  - version:
+    - v23.5.0
+    - v22.13.0
     pr-url: https://github.com/nodejs/node/pull/56201
     description: Permission Model is now stable.
 -->
@@ -1960,7 +1968,9 @@ Location at which the report will be generated.
 ### `--report-exclude-env`
 
 <!-- YAML
-added: v23.3.0
+added:
+  - v23.3.0
+  - v22.13.0
 -->
 
 When `--report-exclude-env` is passed the diagnostic report generated will not
@@ -2354,7 +2364,7 @@ finished executing even if the event loop would otherwise remain active.
 <!-- YAML
 added: v22.8.0
 changes:
-  - version: REPLACEME
+  - version: v23.6.0
     pr-url: https://github.com/nodejs/node/pull/56298
     description: This flag was renamed from `--experimental-test-isolation` to
                  `--test-isolation`.
@@ -2481,7 +2491,9 @@ subtests inherit this value from their parent. The default value is `Infinity`.
 <!-- YAML
 added: v22.3.0
 changes:
-  - version: v23.4.0
+  - version:
+    - v23.4.0
+    - v22.13.0
     pr-url: https://github.com/nodejs/node/pull/55897
     description: Snapsnot testing is no longer experimental.
 -->
@@ -2599,7 +2611,9 @@ Print stack traces for deprecations.
 ### `--trace-env`
 
 <!-- YAML
-added: v23.4.0
+added:
+  - v23.4.0
+  - v22.13.0
 -->
 
 Print information about any access to environment variables done in the current Node.js
@@ -2622,15 +2636,19 @@ To print the stack trace of the access, use `--trace-env-js-stack` and/or
 ### `--trace-env-js-stack`
 
 <!-- YAML
-added: v23.4.0
+added:
+  - v23.4.0
+  - v22.13.0
 -->
 
 In addition to what `--trace-env` does, this prints the JavaScript stack trace of the access.
 
 ### `--trace-env-native-stack`
 
 <!-- YAML
-added: v23.4.0
+added:
+  - v23.4.0
+  - v22.13.0
 -->
 
 In addition to what `--trace-env` does, this prints the native stack trace of the access.
@@ -2677,6 +2695,7 @@ i.e. invoking `process.exit()`.
 <!-- YAML
 added:
  - v23.5.0
+ - v22.13.0
 -->
 
 Prints information about usage of [Loading ECMAScript modules using `require()`][].

doc/api/crypto.md

@@ -3940,6 +3940,13 @@ By default, the prime is encoded as a big-endian sequence of octets
 in an {ArrayBuffer}. If the `bigint` option is `true`, then a {bigint}
 is provided.
 
+The `size` of the prime will have a direct impact on how long it takes to
+generate the prime. The larger the size, the longer it will take. Because
+we use OpenSSL's `BN_generate_prime_ex` function, which provides only
+minimal control over our ability to interrupt the generation process,
+it is not recommended to generate overly large primes, as doing so may make
+the process unresponsive.
+
 ### `crypto.generatePrimeSync(size[, options])`
 
 <!-- YAML
@@ -3981,6 +3988,13 @@ By default, the prime is encoded as a big-endian sequence of octets
 in an {ArrayBuffer}. If the `bigint` option is `true`, then a {bigint}
 is provided.
 
+The `size` of the prime will have a direct impact on how long it takes to
+generate the prime. The larger the size, the longer it will take. Because
+we use OpenSSL's `BN_generate_prime_ex` function, which provides only
+minimal control over our ability to interrupt the generation process,
+it is not recommended to generate overly large primes, as doing so may make
+the process unresponsive.
+
 ### `crypto.getCipherInfo(nameOrNid[, options])`
 
 <!-- YAML

doc/api/deprecations.md

@@ -3779,7 +3779,9 @@ It is recommended to use the `new` qualifier instead. This applies to all REPL c
 
 <!-- YAML
 changes:
-  - version: v23.4.0
+  - version:
+    - v23.4.0
+    - v22.13.0
     pr-url: https://github.com/nodejs/node/pull/55892
     description: Documentation-only.
 -->
@@ -3793,7 +3795,9 @@ will throw an error in a future version.
 
 <!-- YAML
 changes:
-  - version: v23.4.0
+  - version:
+    - v23.4.0
+    - v22.13.0
     pr-url: https://github.com/nodejs/node/pull/55545
     description: Documentation-only deprecation.
 -->
@@ -3806,7 +3810,9 @@ These properties are unconditionally `true`. Any checks based on these propertie
 
 <!-- YAML
 changes:
-  - version: v23.4.0
+  - version:
+    - v23.4.0
+    - v22.13.0
     pr-url: https://github.com/nodejs/node/pull/55545
     description: Documentation-only deprecation.
 -->

doc/api/errors.md

@@ -2179,7 +2179,9 @@ signaling a short circuit.
 ### `ERR_LOAD_SQLITE_EXTENSION`
 
 <!-- YAML
-added: v23.5.0
+added:
+  - v23.5.0
+  - v22.13.0
 -->
 
 An error occurred while loading a SQLite extension.
@@ -2459,7 +2461,9 @@ object.
 ### `ERR_QUIC_APPLICATION_ERROR`
 
 <!-- YAML
-added: v23.4.0
+added:
+  - v23.4.0
+  - v22.13.0
 -->
 
 > Stability: 1 - Experimental
@@ -2513,7 +2517,9 @@ Opening a QUIC stream failed.
 ### `ERR_QUIC_TRANSPORT_ERROR`
 
 <!-- YAML
-added: v23.4.0
+added:
+  - v23.4.0
+  - v22.13.0
 -->
 
 > Stability: 1 - Experimental
@@ -2525,7 +2531,9 @@ A QUIC transport error occurred.
 ### `ERR_QUIC_VERSION_NEGOTIATION_ERROR`
 
 <!-- YAML
-added: v23.4.0
+added:
+  - v23.4.0
+  - v22.13.0
 -->
 
 > Stability: 1 - Experimental

doc/api/module.md

@@ -223,7 +223,9 @@ See [Customization hooks][].
 ### `module.stripTypeScriptTypes(code[, options])`
 
 <!-- YAML
-added: v23.2.0
+added:
+  - v23.2.0
+  - v22.13.0
 -->
 
 > Stability: 1.1 - Active development

doc/api/modules.md

@@ -177,6 +177,7 @@ added:
 changes:
   - version:
     - v23.5.0
+    - v22.13.0
     pr-url: https://github.com/nodejs/node/pull/56194
     description: This feature no longer emits an experimental warning by default,
                  though the warning can still be emitted by --trace-require-module.

doc/api/net.md

@@ -173,7 +173,9 @@ The list of rules added to the blocklist.
 ### `BlockList.isBlockList(value)`
 
 <!-- YAML
-added: v23.4.0
+added:
+  - v23.4.0
+  - v22.13.0
 -->
 
 * `value` {any} Any JS value
@@ -247,7 +249,9 @@ added:
 ### `SocketAddress.parse(input)`
 
 <!-- YAML
-added: v23.4.0
+added:
+  - v23.4.0
+  - v22.13.0
 -->
 
 * `input` {string} An input string containing an IP address and optional port,

doc/api/process.md

@@ -1930,7 +1930,9 @@ A boolean value that is `true` if the current Node.js build includes the inspect
 
 <!-- YAML
 added: v0.5.3
-deprecated: v23.4.0
+deprecated:
+  - v23.4.0
+  - v22.13.0
 -->
 
 > Stability: 0 - Deprecated. This property is always true, and any checks based on it are
@@ -1969,7 +1971,9 @@ A boolean value that is `true` if the current Node.js build includes support for
 
 <!-- YAML
 added: v4.8.0
-deprecated: v23.4.0
+deprecated:
+  - v23.4.0
+  - v22.13.0
 -->
 
 > Stability: 0 - Deprecated. Use `process.features.tls` instead.
@@ -1985,7 +1989,9 @@ This value is therefore identical to that of `process.features.tls`.
 
 <!-- YAML
 added: v0.11.13
-deprecated: v23.4.0
+deprecated:
+  - v23.4.0
+  - v22.13.0
 -->
 
 > Stability: 0 - Deprecated. Use `process.features.tls` instead.
@@ -2001,7 +2007,9 @@ This value is therefore identical to that of `process.features.tls`.
 
 <!-- YAML
 added: v0.5.3
-deprecated: v23.4.0
+deprecated:
+  - v23.4.0
+  - v22.13.0
 -->
 
 > Stability: 0 - Deprecated. Use `process.features.tls` instead.
@@ -2033,7 +2041,9 @@ Node.js is run with `--no-experimental-strip-types`.
 
 <!-- YAML
 added: v0.5.3
-deprecated: v23.4.0
+deprecated:
+  - v23.4.0
+  - v22.13.0
 -->
 
 > Stability: 0 - Deprecated. This property is always true, and any checks based on it are
@@ -3235,7 +3245,7 @@ console.log(`The parent process is pid ${ppid}`);
 ## `process.ref(maybeRefable)`
 
 <!-- YAML
-added: REPLACEME
+added: v23.6.0
 -->
 
 * `maybeRefable` {any} An object that may be "refable".
@@ -3544,7 +3554,9 @@ console.log(`Report on exception: ${report.reportOnUncaughtException}`);
 ### `process.report.excludeEnv`
 
 <!-- YAML
-added: v23.3.0
+added:
+  - v23.3.0
+  - v22.13.0
 -->
 
 * {boolean}
@@ -4292,7 +4304,7 @@ In [`Worker`][] threads, `process.umask(mask)` will throw an exception.
 ## `process.unref(maybeRefable)`
 
 <!-- YAML
-added: REPLACEME
+added: v23.6.0
 -->
 
 * `maybeUnfefable` {any} An object that may be "unref'd".