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
This commit add the contents that should go into the docker-node and
build issues when doing a security release.
PR-URL: #39215
Reviewed-By: Richard Lau <rlau@redhat.com>
Copy file name to clipboardExpand all lines: doc/guides/security-release-process.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,9 +63,19 @@ information described.
63
63
*[ ] Request releaser(s) to start integrating the PRs to be released.
64
64
65
65
*[ ] Notify [docker-node][] of upcoming security release date: ***LINK***
66
+
```text
67
+
Heads up of Node.js security releases Day Month Year
68
+
69
+
As per the Node.js security release process this is the FYI that there is going to be a security release Day Month Year
70
+
```
66
71
67
72
*[ ] Notify build-wg of upcoming security release date by opening an issue
68
73
in [nodejs/build][] to request WG members are available to fix any CI issues.
74
+
```text
75
+
Heads up of Node.js security releases Day Month Year
76
+
77
+
As per security release process this is a heads up that there will be security releases Day Month Year and we'll need people from build to lock/unlock ci and to support and build issues we see.
0 commit comments