fix: Release note headings now match the collapsible summary labels

[hatayama]

Summary

• Inside each collapsible release section, the top changelog heading now uses the exact same label as the summary row.

User Impact

• Before: the summary row and the heading inside it named the same component in two styles, e.g. uloop-project-runner: 3.0.0-beta.47 wrapping uloop Project Runner 3.0.0-beta.47 (and likewise for unity-package / uloop-dispatcher).
• After: all three components read identically in both places, e.g. uloop-project-runner: 3.0.0-beta.47 wrapping ## uloop-project-runner: 3.0.0-beta.47.

Changes

• The release PR body clarifier now stamps one display slug on both the summary and the heading, replacing the separate human-readable display-name map.
• No change to release-please component ids, tags, or the label-sync tag resolution (summary slugs are unchanged from fix: Dispatcher release summary now carries the uloop prefix #1696).

Verification

• go test ./internal/automation/ in cli/release-automation (updated expectations fail without the fix)
• sh scripts/test-sync-published-release-pr-labels.sh passes unchanged
• scripts/check-go-cli.sh passes

[coderabbitai]

Warning

Review limit reached

@hatayama, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 10 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 65ef2707-54a3-4d8b-91f8-d653afdf3f7d

📥 Commits

Reviewing files that changed from the base of the PR and between 39ea99e and f4018ad.

📒 Files selected for processing (2)

• cli/release-automation/internal/automation/release_pr_body.go
• cli/release-automation/internal/automation/release_pr_checks_test.go

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/release-heading-matches-summary

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}