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
Copy file name to clipboardexpand all lines: doc/releases.md
+3
Original file line number
Diff line number
Diff line change
@@ -269,6 +269,9 @@ Merge your release proposal branch into the stable branch that you are releasing
269
269
270
270
Cherry-pick the release commit to `master`. After cherry-picking, edit `src/node_version.h` to ensure the version macros contain whatever values were previously on `master`. `NODE_VERSION_IS_RELEASE` should be `0`.
271
271
272
+
Run `make lint-md-build; make lint` before pushing to `master`, to make sure the
273
+
Changelog formatting passes the lint rules on `master`.
274
+
272
275
### 12. Promote and Sign the Release Builds
273
276
274
277
**It is important that the same individual who signed the release tag be the one to promote the builds as the SHASUMS256.txt file needs to be signed with the same GPG key!**
0 commit comments