Commit dec0213
authored
doc: add known issue to v24.11.0 release notes
PR-URL: #60467
Refs: nodejs/nodejs.org#8280
Reviewed-By: Zeyu "Alex" Yang <himself65@outlook.com>
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
Reviewed-By: Filip Skokan <panva.ip@gmail.com>
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Reviewed-By: Mohammed Keyvanzadeh <mohammadkeyvanzade94@gmail.com>1 parent 4e9e5a1 commit dec0213
1 file changed
Lines changed: 9 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -70,6 +70,15 @@ the end of April 2028. | |||
| 70 | 70 | Other than updating metadata, such as the `process.release` object, to reflect | |
| 71 | 71 | that the release is LTS, no further changes from Node.js 24.10.0 are included. | |
| 72 | 72 | ||
| 73 | + ### Known issue | ||
| 74 | + | ||
| 75 | + An issue has been identified in the Node.js 24.x line with `Buffer.allocUnsafe` | ||
| 76 | + unintentionally returning zero-filled buffers. This API is | ||
| 77 | + [documented to return uninitialized memory](https://nodejs.org/docs/latest-v24.x/api/buffer.html#static-method-bufferallocunsafesize). | ||
| 78 | + The documented behavior will be restored in the next Node.js 24.x LTS release to bring | ||
| 79 | + it back in line with previous releases. For more information, see | ||
| 80 | + [#60423](https://github.com/nodejs/node/issues/60423). | ||
| 81 | + | ||
| 73 | 82 | <a id="24.10.0"></a> | |
| 74 | 83 | ||
| 75 | 84 | ## 2025-10-08, Version 24.10.0 (Current), @RafaelGSS | |
0 commit comments