fix: Dispatcher heading in release notes now shows its component name

[hatayama]

Summary

• The dispatcher section of release PR bodies now gets a labeled changelog heading like the other components.

User Impact

• Before: in release PRs, the Unity package and project runner sections showed headings like Unity Package 3.0.0-beta.49 / uloop Project Runner 3.0.0-beta.47, but the dispatcher section showed only a bare 3.0.1-beta.13 with no component name (visible in chore: release v3-beta #1693).
• After: the dispatcher heading reads Dispatcher 3.0.1-beta.13, consistent with the other components.

Changes

• Add the missing dispatcher entry to the release PR body clarifier's component display-name map.
• Extend the heading-clarification test with a dispatcher section.

Verification

• go test ./internal/automation/ in cli/release-automation (the new assertion fails without the fix)
• scripts/check-go-cli.sh passes (fmt, vet, lint, tests, builds)

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 787c34e4-da73-4373-8b05-35854e04900d

📥 Commits

Reviewing files that changed from the base of the PR and between fe0e6db and 1cf0d8c.

📒 Files selected for processing (2)

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

---

📝 Walkthrough

Walkthrough

The release PR heading formatter now recognizes dispatcher as Dispatcher, with test coverage for its clarified heading output and version link.

Changes

Release check heading clarification

Layer / File(s)	Summary
Add dispatcher heading mapping and coverage cli/release-automation/internal/automation/release_pr_body.go, cli/release-automation/internal/automation/release_pr_checks_test.go	The formatter maps the dispatcher component to Dispatcher, and the test verifies the clarified heading, version, compare URL, and date.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

• hatayama/unity-cli-loop#1451: Updates related release PR component-heading clarification logic.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: adding a Dispatcher component name to release-note headings.
Description check	✅ Passed	The description matches the change set by explaining the Dispatcher heading fix, test update, and verification.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/release-pr-dispatcher-heading-label

---

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.}