You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- update security release process to reflect current way to
ask for tweet to amplify security release blog posts.
Signed-off-by: Michael Dawson <[email protected]>
PR-URL: #50166
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Rafael Gonzaga <[email protected]>
*[ ] Send a message to `#nodejs-social` in OpenJS Foundation slack
123
+
*[ ] Post in the [nodejs-social channel][]
124
+
in the OpenJS slack asking for amplication of the blog post.
124
125
125
126
```text
126
127
Security release pre-alert:
@@ -179,7 +180,8 @@ out a better way, forward the email you receive to
179
180
For more information see: https://nodejs.org/en/blog/vulnerability/month-year-security-releases/
180
181
```
181
182
182
-
*[ ] Create a new issue in [nodejs/tweet][]
183
+
*[ ] Post in the [nodejs-social channel][]
184
+
in the OpenJS slack asking for amplication of the blog post.
183
185
```text
184
186
Security release:
185
187
@@ -238,5 +240,5 @@ The steps to correct CVE information are:
0 commit comments