From f44d633311d8303387ed815061b7ae8757dff28a Mon Sep 17 00:00:00 2001
From: Ludovico Magnocavallo <ludomagno@google.com>
Date: Mon, 25 May 2026 15:50:30 +0000
Subject: [PATCH] docs: update release-process skill to use H2 for breaking
 changes

---
 skills/maintenance/release-process/SKILL.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/skills/maintenance/release-process/SKILL.md b/skills/maintenance/release-process/SKILL.md
index 727d1e397..fd8a4ea74 100644
--- a/skills/maintenance/release-process/SKILL.md
+++ b/skills/maintenance/release-process/SKILL.md
@@ -109,8 +109,8 @@ BREAKING_CHANGES=$(echo "$RELEASE_NOTES" | awk '/^### BREAKING CHANGES/{flag=1;
 
 # 3. Format breaking changes
 if [ -n "$(echo "$BREAKING_CHANGES" | tr -d '[:space:]')" ]; then
-  # Convert "### BREAKING CHANGES" to "### Breaking Changes"
-  FORMATTED_BREAKING_CHANGES=$(echo "$BREAKING_CHANGES" | sed 's/^### BREAKING CHANGES/### Breaking Changes/')
+  # Convert "### BREAKING CHANGES" to "## Breaking Changes"
+  FORMATTED_BREAKING_CHANGES=$(echo "$BREAKING_CHANGES" | sed 's/^### BREAKING CHANGES/## Breaking Changes/')
   echo "$FORMATTED_BREAKING_CHANGES"
 fi
 ```
@@ -136,6 +136,6 @@ Go to the [GitHub Releases UI](https://github.com/GoogleCloudPlatform/cloud-foun
 1. **Tag:** Create a new tag matching the new version (e.g., `v56.0.0`).
 2. **Title:** Use the exact same version string as the tag.
 3. **Release Notes:** Click the **"Generate release notes"** button.
-4. **Breaking Changes:** If the `CHANGELOG.md` contains a "BREAKING CHANGES" section for this release, copy it, paste it at the **top** of the generated release notes, and change the heading to "Breaking Changes".
+4. **Breaking Changes:** If the `CHANGELOG.md` contains a "BREAKING CHANGES" section for this release, copy it, paste it at the **top** of the generated release notes, and change the heading to "## Breaking Changes".
 
 Click **Publish release**.