From ded4eca42532f4be049f75d7170449938a8e70e1 Mon Sep 17 00:00:00 2001 From: Rafael Gonzaga Date: Thu, 6 Mar 2025 09:52:04 -0300 Subject: [PATCH] doc: ping nodejs/tsc for each security pull request Refs: https://github.com/nodejs/TSC/issues/1687 PR-URL: https://github.com/nodejs/node/pull/57309 Reviewed-By: James M Snell Reviewed-By: Luigi Pinca Reviewed-By: Michael Dawson Reviewed-By: Marco Ippolito --- doc/contributing/security-release-process.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/doc/contributing/security-release-process.md b/doc/contributing/security-release-process.md index 9ea616f6de2298..0932dfb7b63c1d 100644 --- a/doc/contributing/security-release-process.md +++ b/doc/contributing/security-release-process.md @@ -56,6 +56,9 @@ The current security stewards are documented in the main Node.js * Use the "summary" feature in HackerOne. Example [2038134](https://hackerone.com/reports/2038134) * `git node security --add-report=report_id` * `git node security --remove-report=report_id` + * Ensure to ping the Node.js TSC team for review of the PRs prior to the release date. + * Adding individuals with expertise in the report topic is also a viable option if + communicated properly with nodejs/security and TSC. * [ ] 3\. **Assigning Severity and Writing Team Summary:** * [ ] Assign a severity and write a team summary on HackerOne for the reports