Skip to content

doc: mention the request-cves label in the security release process #67306

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

Draft
UlisesGascon wants to merge 1 commit into
base: main
Choose a base branch
from
+6 −1
Draft

doc: mention the request-cves label in the security release process #67306

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
7 changes: 6 additions & 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 @@ -75,7 +75,12 @@ The current security stewards are documented in the main Node.js
`vulnerabilities.json`.

* [ ] 4\. **Requesting CVEs:**
* Request CVEs for the reports with `git node security --request-cve`.
* Request CVEs for the reports with `git node security --request-cve`, or
add the `request-cves` label to the security release pull request in the
[security-release][] repository. The label does the same from the
repository, no local credentials needed, and reports the result as a
comment. On failure, remove the `request-cves-failed` label and add
`request-cves` again to retry.
* Make sure to have a green CI before requesting a CVE.
* Check if there is a need to issue a CVE for any version that became
EOL after the last security release through [this issue](https://github.com/nodejs/security-wg/issues/1419).
Expand Down