GeezerVison is showing github.com — doc: update security release process · nodejs/node@ff8e1b8
File tree
Expand file treeCollapse file tree
Open diff view settings
Expand file treeCollapse file tree
Open diff view settings
Collapse file
Copy file name to clipboardExpand all lines: doc/contributing/security-release-process.md +5-3Lines changed: 5 additions & 3 deletions - Display the source diff
- Display the rich diff
| Original file line number | Diff line number | Diff line change |
|---|
@@ -120,7 +120,8 @@ The google groups UI does not support adding a CC, until we figure |
120 | 120 | out a better way, forward the email you receive to |
121 | 121 | |
122 | 122 |
|
123 | | -* [ ] 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: |
238 | 240 | [H1 CVE requests]: https://hackerone.com/nodejs/cve_requests |
239 | 241 | [docker-node]: https://github.com/nodejs/docker-node/issues |
240 | 242 | [email]: https://groups.google.com/forum/#!forum/nodejs-sec |
| 243 | +[nodejs-social channel]: https://openjs-foundation.slack.com/archives/C0142A39BNE |
241 | 244 | [nodejs/build]: https://github.com/nodejs/build/issues |
242 | | -[nodejs/tweet]: https://github.com/nodejs/tweet/issues |
|