Skip to content
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

Jump to bottom

Blog: add #28630 to "notable" section of v12.7.0 release #2353

Merged
merged 2 commits into from
Jul 27, 2019
Merged

Blog: add #28630 to "notable" section of v12.7.0 release #2353

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f6344de
Blog: add #28630 to "notable" section of v12.7.0 release
boneskull Jul 25, 2019
3f6d3e1
Update v12.7.0.md
targos Jul 27, 2019
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
2 changes: 2 additions & 0 deletions locale/en/blog/release/v12.7.0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,8 @@ author: Michaël Zasso
* **readline,tty**:
* Exposed stream API from various methods which write characters (cjihrig) [#28674](https://github.com/nodejs/node/pull/28674),
[#28721](https://github.com/nodejs/node/pull/28721).
* **report**:
* Modify `process.report.getReport()` to return an `Object` instead of a JSON string (Christopher Hiller) [#28630](https://github.com/nodejs/node/pull/28630).
* **src**:
* Use cgroups to get memory limits. This improves the way we set the memory ceiling for a Node.js process. Previously
we would use the physical memory size to estimate the necessary V8 heap sizes. The physical memory size
Expand Down