nodejs
diff --git a/Collapse file
‎doc/api/deprecations.md‎
Copy file name to clipboardExpand all lines: doc/api/deprecations.md
+7-2Lines changed: 7 additions & 2 deletions
Display the source diff
Display the rich diff b/Collapse file
‎doc/api/deprecations.md‎
Copy file name to clipboardExpand all lines: doc/api/deprecations.md
+7-2Lines changed: 7 additions & 2 deletions
Display the source diff
Display the rich diff
diff --git a/Collapse file
‎doc/api/url.md‎
Copy file name to clipboardExpand all lines: doc/api/url.md
+9-1Lines changed: 9 additions & 1 deletion
Display the source diff
Display the rich diff b/Collapse file
‎doc/api/url.md‎
Copy file name to clipboardExpand all lines: doc/api/url.md
+9-1Lines changed: 9 additions & 1 deletion
Display the source diff
Display the rich diff
@@ -2660,11 +2660,15 @@ future release.
 
 <!-- YAML
 changes:
+  - version:
+      - v24.0.0
+    pr-url: https://github.com/nodejs/node/pull/55017
+    description: DEP0169 covers also `url.format()` and `url.resolve()`.
   - version:
       - v19.0.0
       - v18.13.0
     pr-url: https://github.com/nodejs/node/pull/44919
-    description: \`url.parse()` is deprecated again in DEP0169.
+    description: DEP0169 deprecates `url.parse()` again.
   - version:
       - v15.13.0
       - v14.17.0
@@ -3775,7 +3779,7 @@ Type: Application (non-`node_modules` code only)
 have security implications. Use the [WHATWG URL API][] instead. CVEs are not
 issued for `url.parse()` vulnerabilities.
 
-Passing a string argument to [`url.format()`][] invokes `url.parse()`
+Calling [`url.format(urlString)`][] or [`url.resolve()`][] invokes `url.parse()`
 internally, and is therefore also covered by this deprecation.
 
 ### DEP0170: Invalid port when using `url.parse()`
@@ -4580,6 +4584,7 @@ const server = http2.createSecureServer({
 [`tls.createSecureContext()`]: tls.md#tlscreatesecurecontextoptions
 [`tls.createServer()`]: tls.md#tlscreateserveroptions-secureconnectionlistener
 [`url.format()`]: url.md#urlformaturlobject
+[`url.format(urlString)`]: url.md#urlformaturlstring
 [`url.parse()`]: url.md#urlparseurlstring-parsequerystring-slashesdenotehost
 [`url.resolve()`]: url.md#urlresolvefrom-to
 [`util._extend()`]: util.md#util_extendtarget-source
 
@@ -1839,7 +1839,7 @@ changes:
 
 `url.format(urlString)` is shorthand for `url.format(url.parse(urlString))`.
 
-Because it invokes the deprecated [`url.parse()`][], passing a string argument
+Because it invokes the deprecated [`url.parse()`][] internally, passing a string argument
 to `url.format()` is itself deprecated.
 
 Canonicalizing a URL string can be performed using the WHATWG URL API, by
@@ -1956,6 +1956,10 @@ npx codemod@latest @nodejs/node-url-to-whatwg-url
 <!-- YAML
 added: v0.1.25
 changes:
+  - version:
+      - v24.0.0
+    pr-url: https://github.com/nodejs/node/pull/55017
+    description: Deprecated again through DEP0169.
   - version:
       - v15.13.0
       - v14.17.0
@@ -1979,6 +1983,8 @@ changes:
                  contains a hostname.
 -->
 
+> Stability: 0 - Deprecated: Use the WHATWG URL API instead.
+
 * `from` {string} The base URL to use if `to` is a relative URL.
 * `to` {string} The target URL to resolve.
 
@@ -1992,6 +1998,8 @@ url.resolve('http://example.com/', '/one');    // 'http://example.com/one'
 url.resolve('http://example.com/one', '/two'); // 'http://example.com/two'
 ```
 
+Because it invokes the deprecated [`url.parse()`][] internally, `url.resolve()` is itself deprecated.
+
 To achieve the same result using the WHATWG URL API:
 
 ```js