From acd74cb562423f66387da4c753759df56ccda81a Mon Sep 17 00:00:00 2001
From: Mark Johnson <739719+virgofx@users.noreply.github.com>
Date: Mon, 2 Jun 2025 02:50:19 +0000
Subject: [PATCH] fix: clarify usage of H3 headers in changelog section
 structure

This should help ensure release notes generated using gpt-4.1 are
more closely aligned with the instructions.
---
 .github/scripts/changelog.js | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/scripts/changelog.js b/.github/scripts/changelog.js
index b4875e4..5e0baed 100644
--- a/.github/scripts/changelog.js
+++ b/.github/scripts/changelog.js
@@ -75,7 +75,7 @@ Content Priority (High to Low):
 6. Build/CI changes - generally omit unless they affect end users
 
 Section Structure:
-Use H3 headers only when you have substantial content. Organize logically under these sections:
+Always use H3 headers (###) for the section titles below, but only include a section if it contains relevant entries. Do not render empty sections. Organize logically under these categories:
 - 🚨 Breaking Changes (always first if present)
 - ✨ New Features 
 - 🐛 Bug Fixes