Adjust heading levels in release notes.

jenlampton · jenlampton · commit f74a8ffde483 · 2025-10-06T21:23:59.000-07:00
diff --git a/templates/issue-template--release--bug-fix--security.md b/templates/issue-template--release--bug-fix--security.md
@@ -23,7 +23,7 @@ Release scheduled for [Month] DD, 20xx 10am - 4pm PT
   - [ ] Include a short, descriptive summary of the release, for example:
     * "Security release for Backdrop CMS. This release fixes 1 security vulnerability:"
     * Include a list of SA's for commits to this release
-  - [ ] Include a section heading `**Notes for updating**`
+  - [ ] Include a section heading `## Notes for updating*`
     - [ ] Note if any changes were made to files outside the `core` directory, for example:
       * ``- No changes have been made to the `.htaccess`, `robots.txt` or default `settings.php` files in this release. Updating customized versions of those files is not necessary.``
       * See [this example](https://github.com/backdrop/backdrop/releases/tag/1.18.0) for updates to `.htaccess`
@@ -33,11 +33,12 @@ Release scheduled for [Month] DD, 20xx 10am - 4pm PT
       * or `**It will be necessary to run the update script** (located at /core/update.php) for this release.`
       * Note: you can use this command to see if any install files were changed:
       `ls -1 core/modules/*/*.install | while read filename; do echo "$(git log -1 --pretty="format:%ad %f" --date=format:"%F %R" -- $filename)" $filename; done|sort`
-  - [ ] Include a section heading `**Changes since version 1.xx.x** are listed below.`
+  - [ ] Include a section heading `## Changes since version 1.xx.x are listed below.`
     * Navigate to [Actions](https://github.com/backdrop/backdrop-issues/actions)
     * Select the most recent time "Release Notes Generator" has been run.
     * Download the `release-notes` artifact attached to the generator.
     * Unzip the file, and copy/pate contents into release notes draft.
+      - Move the headings to H3, add another `#` before the `##` to get `###`.
     * Remove any square brackets in the titles, and move those issues to their own section.
 - [ ] Draft Security Advisories (assign to stpaultim / klonos / jenlampton  herbdool / quicksketch)
 
diff --git a/templates/issue-template--release--bug-fix.md b/templates/issue-template--release--bug-fix.md
@@ -22,7 +22,7 @@ Release scheduled for [Month] DD, 20xx 10am - 4pm PT
 - [ ] Draft Release notes (assign to jenlampton / herbdool / quicksketch)
   - [ ] Include a short, descriptive summary of the release, for example:
     * "Maintenance release for Backdrop CMS. This update contains bug fixes and usability improvements only."
-  - [ ] Include a section heading `**Notes for updating**`
+  - [ ] Include a section heading `## Notes for updating*`
     - [ ] Note if any changes were made to files outside the `core` directory, for example:
       * ``- No changes have been made to the `.htaccess`, `robots.txt` or default `settings.php` files in this release. Updating customized versions of those files is not necessary.``
       * See [this example](https://github.com/backdrop/backdrop/releases/tag/1.18.0) for updates to `.htaccess`
@@ -32,11 +32,12 @@ Release scheduled for [Month] DD, 20xx 10am - 4pm PT
       * or `**It will be necessary to run the update script** (located at /core/update.php) for this release.`
       * Note: you can use this command to see if any install files were changed:
       `ls -1 core/modules/*/*.install | while read filename; do echo "$(git log -1 --pretty="format:%ad %f" --date=format:"%F %R" -- $filename)" $filename; done|sort`
-  - [ ] Include a section heading `**Changes since version 1.xx.x** are listed below.`
+  - [ ] Include a section heading `## Changes since version 1.xx.x are listed below.`
     * Navigate to [Actions](https://github.com/backdrop/backdrop-issues/actions)
     * Select the most recent time "Release Notes Generator" has been run.
     * Download the `release-notes` artifact attached to the generator.
     * Unzip the file, and copy/pate contents into release notes draft.
+      - Move the headings to H3, add another `#` before the `##` to get `###`.
     * Remove any square brackets in the titles, and move those issues to their own section.
 
 ## Release tasks
diff --git a/templates/issue-template--release--major.md b/templates/issue-template--release--major.md
@@ -17,7 +17,7 @@ Steps to create a MAJOR release
 - [ ] Draft Release notes (assign to jenlampton / herbdool / quicksketch)
   - [ ] Include a short, descriptive summary of the release, for example:
     * This is the preview release of Backdrop 1.16.0. Please use this version if you would like to help us test the features in the new version of Backdrop prior to the official release on January/May/September 15th, 20xx.
-  - [ ] Include a section heading `**Notes for updating**`
+  - [ ] Include a section heading `## Notes for updating*`
     - [ ] Note if any changes were made to files outside the `core` directory, for example:
       * ``- No changes have been made to the `.htaccess`, `robots.txt` or default `settings.php` files in this release. Updating customized versions of those files is not necessary.``
       * See [this example](https://github.com/backdrop/backdrop/releases/tag/1.18.0) for updates to `.htaccess`
@@ -27,11 +27,12 @@ Steps to create a MAJOR release
       * or `**It will be necessary to run the update script** (located at /core/update.php) for this release.`
       * Note: you can use this command to see if any install files were changed:
       `ls -1 core/modules/*/*.install | while read filename; do echo "$(git log -1 --pretty="format:%ad %f" --date=format:"%F %R" -- $filename)" $filename; done|sort`
-  - [ ] Include a section heading `**Changes since version 1.xx.x** are listed below.`
+  - [ ] Include a section heading `## Changes since version 1.xx.x are listed below.`
       * navigate to [Actions](https://github.com/backdrop/backdrop-issues/actions)
       * Select the most recent time "Release Notes Generator" has been run.
       * Download the `release-notes` artifact attached to the generator.
       * Unzip the file, and copy/pate contents into release notes draft.
+        - Move the headings to H3, add another `#` before the `##` to get `###`.
       * Re-word issue titles to indicate that the problems have been fixed.
 - [ ] Draft blog post (assign to tomgrandy / klonos / jenlampton / quicksketch)
 - [ ] Draft a newsletter via MailChimp (assign to facetinteractive / tomgrandy / jenlampton)
diff --git a/templates/issue-template--release--minor-preview.md b/templates/issue-template--release--minor-preview.md
@@ -22,7 +22,7 @@ Scheduled for January/May/September 1st, 20xx 10am - 4pm PT
 - [ ] Draft Release notes (assign to jenlampton / herbdool / quicksketch)
   - [ ] Include a short, descriptive summary of the release, for example:
     * This is the preview release of Backdrop 1.16.0. Please use this version if you would like to help us test the features in the new version of Backdrop prior to the official release on January/May/September 15th, 20xx.
-  - [ ] Include a section heading `**Notes for updating**`
+  - [ ] Include a section heading `## Notes for updating*`
     - [ ] Note if any changes were made to files outside the `core` directory, for example:
       * ``- No changes have been made to the `.htaccess`, `robots.txt` or default `settings.php` files in this release. Updating customized versions of those files is not necessary.``
       * See [this example](https://github.com/backdrop/backdrop/releases/tag/1.18.0) for updates to `.htaccess`
@@ -32,11 +32,12 @@ Scheduled for January/May/September 1st, 20xx 10am - 4pm PT
       * or `**It will be necessary to run the update script** (located at /core/update.php) for this release.`
       * Note: you can use this command to see if any install files were changed:
       `ls -1 core/modules/*/*.install | while read filename; do echo "$(git log -1 --pretty="format:%ad %f" --date=format:"%F %R" -- $filename)" $filename; done|sort`
-  - [ ] Include a section heading `**Changes since version 1.xx.x** are listed below.`
+  - [ ] Include a section heading `## Changes since version 1.xx.x are listed below.`
       * navigate to [Actions](https://github.com/backdrop/backdrop-issues/actions)
       * Select the most recent time "Release Notes Generator" has been run.
       * Download the `release-notes` artifact attached to the generator.
       * Unzip the file, and copy/pate contents into release notes draft.
+        - Move the headings to H3, add another `#` before the `##` to get `###`.
       * Re-word issue titles to indicate that the problems have been fixed.
 
 ## Pre-release Publicity + documentation tasks
diff --git a/templates/issue-template--release--minor.md b/templates/issue-template--release--minor.md
@@ -23,21 +23,22 @@ Scheduled for January/September/May 15, 20xx 10am - 4pm PT
   - [ ] Copy Preview release release notes, update as follows
     - [ ] Include a short, descriptive summary of the release, for example:
       * The Backdrop community is proud to release version 1.xx of Backdrop CMS, following our 4-month release cycle.
-    - [ ] Include a section heading `**Notes for updating**`
+    - [ ] Include a section heading `## Notes for updating*`
       - [ ] Note if any changes were made to files outside the `core` directory, for example:
         * ``- No changes have been made to the `.htaccess`, `robots.txt` or default `settings.php` files in this release. Updating customized versions of those files is not necessary.``
         * See [this example](https://github.com/backdrop/backdrop/releases/tag/1.18.0) for updates to `.htaccess`
         * See [this example](https://github.com/backdrop/backdrop/releases/tag/1.16.0) or [this example](https://github.com/backdrop/backdrop/releases/tag/1.14.0) for updates to `settings.php`
       - [ ] Note if updates (update.php) needs to be run, for example:
         * Use the text `The database update script does **not** need to be run.`
         * or `**It will be necessary to run the update script** (located at /core/update.php) for this release.`
-    - [ ] Include a section heading `**Changes since version 1.xx.x** are listed below.`
+    - [ ] Include a section heading `## Changes since version 1.xx.x are listed below.`
         * Note: you can use this command to see if any install files were changed:
         `ls -1 core/modules/*/*.install | while read filename; do echo "$(git log -1 --pretty="format:%ad %f" --date=format:"%F %R" -- $filename)" $filename; done|sort`
       * Navigate to [Actions](https://github.com/backdrop/backdrop-issues/actions)
       * Select the most recent time "Release Notes Generator" has been run.
       * Download the `release-notes` artifact attached to the generator.
       * Unzip the file, and copy/pate contents into release notes draft.
+        - Move the headings to H3, add another `#` before the `##` to get `###`.
       * Re-word issue titles to indicate that the problems have been fixed.
       * Note: This list can also be copied from the list on the preview release, but review closed issuses in the milestone
     - [ ] Verify the list above matches all changes since the most recent bug-fix release
