Skip to content

doc: add known issue to v24.11.0 release notes #60467

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 28, 2025
Merged

doc: add known issue to v24.11.0 release notes #60467

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
83e4abd
doc: add known issue to v24.11.0 release notes
richardlau Oct 28, 2025
dae3db3
fixup! doc: add known issue to v24.11.0 release notes
richardlau Oct 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions doc/changelogs/CHANGELOG_V24.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -70,6 +70,10 @@ the end of April 2028.
Other than updating metadata, such as the `process.release` object, to reflect
that the release is LTS, no further changes from Node.js 24.10.0 are included.

### Known issue

An issue has been identified in the Node.js 24.x line with `Buffer.allocUnsafe` unintentionally returning zero-filled buffers. This API is [documented to return uninitialized memory](https://nodejs.org/docs/latest-v24.x/api/buffer.html#static-method-bufferallocunsafesize). The documented behavior will be restored in the next Node.js 24.x LTS release to bring it back in line with previous releases. For more information, see [#60423](https://github.com/nodejs/node/issues/60423).

<a id="24.10.0"></a>

## 2025-10-08, Version 24.10.0 (Current), @RafaelGSS
Expand Down
Loading