Commit 3fe80c3
doc: include CVE to EOL lines as sec release process
Refs: nodejs/security-wg#1401
PR-URL: #56520
Reviewed-By: Richard Lau <rlau@redhat.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Ulises Gascón <ulisesgascongonzalez@gmail.com>1 parent c85b386 commit 3fe80c3
1 file changed
Lines changed: 2 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -65,6 +65,8 @@ The current security stewards are documented in the main Node.js | |||
| 65 | 65 | * [ ] 4\. **Requesting CVEs:** | |
| 66 | 66 | * Request CVEs for the reports with `git node security --request-cve`. | |
| 67 | 67 | * Make sure to have a green CI before requesting a CVE. | |
| 68 | + * Check if there is a need to issue a CVE for any version that became | ||
| 69 | + EOL after the last security release through [this issue](https://github.com/nodejs/security-wg/issues/1419). | ||
| 68 | 70 | ||
| 69 | 71 | * [ ] 5\. **Choosing or Updating Release Date:** | |
| 70 | 72 | * Get agreement on the planned date for the release. | |
0 commit comments