From d91543a7316f1746240174fa88beaa4f462301de Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ren=C3=A9?= <contact.9a5d6388@renegade334.me.uk>
Date: Thu, 8 Jan 2026 21:34:57 +0000
Subject: [PATCH 1/3] doc: add sqlite session disposal method

PR-URL: https://github.com/nodejs/node/pull/61273
Refs: https://github.com/nodejs/node/pull/58378
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
---
 doc/api/sqlite.md | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/doc/api/sqlite.md b/doc/api/sqlite.md
index 186e70784b94d0..ce6db6186c3396 100644
--- a/doc/api/sqlite.md
+++ b/doc/api/sqlite.md
@@ -735,11 +735,19 @@ Similar to the method above, but generates a more compact patchset. See [Changes
 in the documentation of SQLite. An exception is thrown if the database or the session is not open. This method is a
 wrapper around [`sqlite3session_patchset()`][].
 
-### `session.close()`.
+### `session.close()`
 
 Closes the session. An exception is thrown if the database or the session is not open. This method is a
 wrapper around [`sqlite3session_delete()`][].
 
+### `session[Symbol.dispose]()`
+
+<!-- YAML
+added: v24.9.0
+-->
+
+Closes the session. If the session is already closed, does nothing.
+
 ## Class: `StatementSync`
 
 <!-- YAML

From 3bb0135783bbbb9b25ac44be8dc24c36ca254a09 Mon Sep 17 00:00:00 2001
From: Alireza Ebrahimkhani
 <46849584+AlirezaEbrahimkhani@users.noreply.github.com>
Date: Fri, 9 Jan 2026 04:50:08 +0100
Subject: [PATCH 2/3] doc: add documentation for process.traceProcessWarnings

resolves #53514

PR-URL: https://github.com/nodejs/node/pull/53641
Reviewed-By: Aviv Keller <me@aviv.sh>
---
 doc/api/process.md | 23 +++++++++++++++++++++++
 1 file changed, 23 insertions(+)

diff --git a/doc/api/process.md b/doc/api/process.md
index 04ca0eff9c55d4..a48879338b6015 100644
--- a/doc/api/process.md
+++ b/doc/api/process.md
@@ -4276,6 +4276,29 @@ documentation for the [`'warning'` event][process_warning] and the
 [`emitWarning()` method][process_emit_warning] for more information about this
 flag's behavior.
 
+## `process.traceProcessWarnings`
+
+<!-- YAML
+added: v6.10.0
+-->
+
+* {boolean}
+
+The `process.traceProcessWarnings` property indicates whether the `--trace-warnings` flag
+is set on the current Node.js process. This property allows programmatic control over the
+tracing of warnings, enabling or disabling stack traces for warnings at runtime.
+
+```js
+// Enable trace warnings
+process.traceProcessWarnings = true;
+
+// Emit a warning with a stack trace
+process.emitWarning('Warning with stack trace');
+
+// Disable trace warnings
+process.traceProcessWarnings = false;
+```
+
 ## `process.umask()`
 
 <!-- YAML

From a327288cc6747cf5e07656a1c45fe2f19e0926ae Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ren=C3=A9?= <contact.9a5d6388@renegade334.me.uk>
Date: Fri, 9 Jan 2026 04:12:19 +0000
Subject: [PATCH 3/3] doc: correct description of `error.stack` accessor
 behavior

PR-URL: https://github.com/nodejs/node/pull/61090
Refs: https://github.com/nodejs/node/issues/60862
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Chengzhong Wu <legendecas@gmail.com>
---
 doc/api/errors.md | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/doc/api/errors.md b/doc/api/errors.md
index d92521755e4e6a..a63fb28ab8933d 100644
--- a/doc/api/errors.md
+++ b/doc/api/errors.md
@@ -379,13 +379,17 @@ The location information will be one of:
   represents a call in a user program (using ES module system), or
   its dependencies.
 
-The string representing the stack trace is lazily generated when the
-`error.stack` property is **accessed**.
-
 The number of frames captured by the stack trace is bounded by the smaller of
 `Error.stackTraceLimit` or the number of available frames on the current event
 loop tick.
 
+`error.stack` is a getter/setter for a hidden internal property which is only
+present on builtin `Error` objects (those for which [`Error.isError`][] returns
+true). If `error` is not a builtin error object, then the `error.stack` getter
+will always return `undefined`, and the setter will do nothing. This can occur
+if the accessor is manually invoked with a `this` value that is not a builtin
+error object, such as a {Proxy}.
+
 ## Class: `AssertionError`
 
 * Extends: {errors.Error}
@@ -4381,6 +4385,7 @@ An error occurred trying to allocate memory. This should never happen.
 [`ERR_MISSING_MESSAGE_PORT_IN_TRANSFER_LIST`]: #err_missing_message_port_in_transfer_list
 [`ERR_MISSING_TRANSFERABLE_IN_TRANSFER_LIST`]: #err_missing_transferable_in_transfer_list
 [`ERR_REQUIRE_ASYNC_MODULE`]: #err_require_async_module
+[`Error.isError`]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/isError
 [`EventEmitter`]: events.md#class-eventemitter
 [`MessagePort`]: worker_threads.md#class-messageport
 [`Object.getPrototypeOf`]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/getPrototypeOf