Commit 6a7210e
doc: add note to releases.md
PR-URL: #16507
Refs: nodejs/nodejs.org#1425
Reviewed-By: Anatoli Papirovski <apapirovski@mac.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Yuta Hiroto <hello@about-hiroppy.com>
Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>1 parent 737239a commit 6a7210e
1 file changed
Lines changed: 3 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -134,6 +134,9 @@ The new entry should take the following form: | |||
| 134 | 134 | ||
| 135 | 135 | The release type should be either Current, LTS, or Maintenance, depending on the type of release being produced. | |
| 136 | 136 | ||
| 137 | + Be sure that the `<a>` tag, as well as the two headings, are not | ||
| 138 | + indented at all. | ||
| 139 | + | ||
| 137 | 140 | At the top of each `CHANGELOG_*.md` file, and in the root `CHANGELOG.md` file, | |
| 138 | 141 | there is a table indexing all releases in each major release line. A link to | |
| 139 | 142 | the new release needs to be added to each. Follow the existing examples and be | |
0 commit comments