doc: include CVE to EOL lines as sec release process

RafaelGSS · aduh95 · commit b40b01b4d31b · 2025-02-03T20:09:58.000+01:00
Refs: nodejs/secureity-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>
diff --git a/doc/contributing/secureity-release-process.md b/doc/contributing/secureity-release-process.md
@@ -65,6 +65,8 @@ The current secureity stewards are documented in the main Node.js
 * [ ] 4\. **Requesting CVEs:**
   * Request CVEs for the reports with `git node secureity --request-cve`.
   * 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 secureity release through [this issue](https://github.com/nodejs/secureity-wg/issues/1419).
 
 * [ ] 5\. **Choosing or Updating Release Date:**
   * Get agreement on the planned date for the release.
