2022-05-11, Version 18.2.0 (Current)

Notable changes:

* Revert_ "deps: add template for generated headers" (Daniel Bevenius) #42978
* deps: upgrade npm to 8.9.0 (npm team) #42968
* (SEMVER-MINOR) fs: add `read(buffer[, options])` versions (Livia Medeiros) #42768
* (SEMVER-MINOR) http: added connection closing methods (Shogun) #42812

PR-URL: #43036

Author: RafaelGSS

CHANGELOG.md

@@ -35,7 +35,8 @@ release.
 </tr>
 <tr>
   <td valign="top">
-<b><a href="doc/changelogs/CHANGELOG_V18.md#18.1.0">18.1.0</a></b><br/>
+<b><a href="doc/changelogs/CHANGELOG_V18.md#18.2.0">18.2.0</a></b><br/>
+<a href="doc/changelogs/CHANGELOG_V18.md#18.1.0">18.1.0</a><br/>
 <a href="doc/changelogs/CHANGELOG_V18.md#18.0.0">18.0.0</a><br/>
   </td>
   <td valign="top">

doc/api/fs.md

@@ -420,7 +420,7 @@ number of bytes read is zero.
 #### `filehandle.read(buffer[, options])`
 
 <!-- YAML
-added: REPLACEME
+added: v18.2.0
 -->
 
 * `buffer` {Buffer|TypedArray|DataView} A buffer that will be filled with the
@@ -3273,7 +3273,7 @@ above values.
 ### `fs.read(fd, buffer[, options], callback)`
 
 <!-- YAML
-added: REPLACEME
+added: v18.2.0
 -->
 
 * `fd` {integer}

doc/api/http.md

@@ -1456,15 +1456,15 @@ Stops the server from accepting new connections. See [`net.Server.close()`][].
 ### `server.closeAllConnections()`
 
 <!-- YAML
-added: REPLACEME
+added: v18.2.0
 -->
 
 Closes all connections connected to this server.
 
 ### `server.closeIdleConnections()`
 
 <!-- YAML
-added: REPLACEME
+added: v18.2.0
 -->
 
 Closes all connections connected to this server which are not sending a request

doc/api/https.md

@@ -138,15 +138,15 @@ See [`server.close()`][] in the `node:http` module.
 ### `server.closeAllConnections()`
 
 <!-- YAML
-added: REPLACEME
+added: v18.2.0
 -->
 
 See [`server.closeAllConnections()`][] in the `node:http` module.
 
 ### `server.closeIdleConnections()`
 
 <!-- YAML
-added: REPLACEME
+added: v18.2.0
 -->
 
 See [`server.closeIdleConnections()`][] in the `node:http` module.

doc/api/perf_hooks.md

@@ -70,7 +70,7 @@ Performance Timeline. If `name` is provided, removes only the named mark.
 ### `performance.clearResourceTimings([name])`
 
 <!-- YAML
-added: REPLACEME
+added: v18.2.0
 -->
 
 * `name` {string}
@@ -215,7 +215,7 @@ Performance Timeline manually with `performance.clearMarks`.
 global, cacheMode)\`
 
 <!-- YAML
-added: REPLACEME
+added: v18.2.0
 -->
 
 * `timingInfo` {Object} [Fetch Timing Info][]
@@ -695,7 +695,7 @@ initialized.
 ## Class: `PerformanceResourceTiming`
 
 <!-- YAML
-added: REPLACEME
+added: v18.2.0
 -->
 
 * Extends: {PerformanceEntry}
@@ -708,7 +708,7 @@ The constructor of this class is not exposed to users directly.
 ### `performanceResourceTiming.workerStart`
 
 <!-- YAML
-added: REPLACEME
+added: v18.2.0
 -->
 
 * {number}
@@ -720,7 +720,7 @@ will always return 0.
 ### `performanceResourceTiming.redirectStart`
 
 <!-- YAML
-added: REPLACEME
+added: v18.2.0
 -->
 
 * {number}
@@ -731,7 +731,7 @@ of the fetch which initiates the redirect.
 ### `performanceResourceTiming.redirectEnd`
 
 <!-- YAML
-added: REPLACEME
+added: v18.2.0
 -->
 
 * {number}
@@ -742,7 +742,7 @@ receiving the last byte of the response of the last redirect.
 ### `performanceResourceTiming.fetchStart`
 
 <!-- YAML
-added: REPLACEME
+added: v18.2.0
 -->
 
 * {number}
@@ -753,7 +753,7 @@ to fetch the resource.
 ### `performanceResourceTiming.domainLookupStart`
 
 <!-- YAML
-added: REPLACEME
+added: v18.2.0
 -->
 
 * {number}
@@ -764,7 +764,7 @@ the domain name lookup for the resource.
 ### `performanceResourceTiming.domainLookupEnd`
 
 <!-- YAML
-added: REPLACEME
+added: v18.2.0
 -->
 
 * {number}
@@ -775,7 +775,7 @@ after the Node.js finished the domain name lookup for the resource.
 ### `performanceResourceTiming.connectStart`
 
 <!-- YAML
-added: REPLACEME
+added: v18.2.0
 -->
 
 * {number}
@@ -787,7 +787,7 @@ the resource.
 ### `performanceResourceTiming.connectEnd`
 
 <!-- YAML
-added: REPLACEME
+added: v18.2.0
 -->
 
 * {number}
@@ -799,7 +799,7 @@ the resource.
 ### `performanceResourceTiming.secureConnectionStart`
 
 <!-- YAML
-added: REPLACEME
+added: v18.2.0
 -->
 
 * {number}
@@ -810,7 +810,7 @@ before Node.js starts the handshake process to secure the current connection.
 ### `performanceResourceTiming.requestStart`
 
 <!-- YAML
-added: REPLACEME
+added: v18.2.0
 -->
 
 * {number}
@@ -821,7 +821,7 @@ before Node.js receives the first byte of the response from the server.
 ### `performanceResourceTiming.responseEnd`
 
 <!-- YAML
-added: REPLACEME
+added: v18.2.0
 -->
 
 * {number}
@@ -833,7 +833,7 @@ the transport connection is closed, whichever comes first.
 ### `performanceResourceTiming.transferSize`
 
 <!-- YAML
-added: REPLACEME
+added: v18.2.0
 -->
 
 * {number}
@@ -844,7 +844,7 @@ includes the response header fields plus the response payload body.
 ### `performanceResourceTiming.encodedBodySize`
 
 <!-- YAML
-added: REPLACEME
+added: v18.2.0
 -->
 
 * {number}
@@ -856,7 +856,7 @@ content-codings.
 ### `performanceResourceTiming.decodedBodySize`
 
 <!-- YAML
-added: REPLACEME
+added: v18.2.0
 -->
 
 * {number}
@@ -868,7 +868,7 @@ content-codings.
 ### `performanceResourceTiming.toJSON()`
 
 <!-- YAML
-added: REPLACEME
+added: v18.2.0
 -->
 
 Returns a `object` that is the JSON representation of the