-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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.
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
doc: fix process.ppid 'added in' info #29772
Conversation
Probably overkill to run all the tests (been a while since I've used the CI system 😅), but I assume the test failures are unrelated? 🤔 |
For documentation-only changes, you can run node-test-pull-request-lite-pipeline which runs only a linting job and a single (very fast) host for tests. |
The |
@nodejs/tooling @nodejs/releasers it would be great if we could somehow add this information when preparing a new release. We'd need a tool that parses the difference between two That way such PRs would become obsolete in the future. Right now this information is almost always missing. |
Landed in a006465 |
PR-URL: #29772 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
PR-URL: #29772 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
The PR #16839 originally landed in v9.2.0 but was later backported to v8.10.0 and 6.13.0.
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes