Skip to content

doc: ping nodejs/tsc for each security pull request #57309

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
nodejs-github-bot merged 2 commits into from
Mar 6, 2025
Merged

doc: ping nodejs/tsc for each security pull request #57309

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7ed5b14
doc: ping nodejs/tsc for each security pull request
RafaelGSS Mar 4, 2025
abdd435
fixup! doc: ping nodejs/tsc for each security pull request
RafaelGSS Mar 4, 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
Prev Previous commit
fixup! doc: ping nodejs/tsc for each security pull request
  • Loading branch information
@RafaelGSS
RafaelGSS committed Mar 4, 2025
commit abdd435f49fd1639461c794fc71cb5aa19b4fdad
2 changes: 1 addition & 1 deletion doc/contributing/security-release-process.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ The current security stewards are documented in the main Node.js
* `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.
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
Expand Down