Skip to content

fix: Dispatcher release heading now carries the uloop prefix like the project runner#1695

Merged
hatayama merged 1 commit into
v3-betafrom
fix/uloop-dispatcher-display-name
Jul 11, 2026
Merged

fix: Dispatcher release heading now carries the uloop prefix like the project runner#1695
hatayama merged 1 commit into
v3-betafrom
fix/uloop-dispatcher-display-name

Conversation

@hatayama

@hatayama hatayama commented Jul 11, 2026

Copy link
Copy Markdown
Owner

Summary

  • Release PR headings for the two native binaries now share the same naming style.

User Impact

  • Before: the project runner section was headed uloop Project Runner 3.0.0-beta.47 while the dispatcher section was headed just Dispatcher 3.0.1-beta.13.
  • After: the dispatcher heading reads uloop Dispatcher 3.0.1-beta.13, matching the project runner style.

Changes

  • Update the dispatcher entry in the release PR body clarifier's display-name map from Dispatcher to uloop Dispatcher, and adjust the heading test expectation.

Verification

  • go test ./internal/automation/ in cli/release-automation (expectation updated first and confirmed failing, then green)
  • scripts/check-go-cli.sh passes

Review in cubic

Release PR headings labeled the components inconsistently: the project
runner read "uloop Project Runner" while the dispatcher read only
"Dispatcher". Both native binaries now carry the uloop prefix.
@coderabbitai

coderabbitai Bot commented Jul 11, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

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: 40156d5b-721a-45c6-b326-89934671b920

📥 Commits

Reviewing files that changed from the base of the PR and between 1472f1b and 0992dc5.

📒 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 dispatcher component now renders as “uloop Dispatcher” in clarified release PR headings, with the corresponding test expectation updated.

Changes

Dispatcher heading clarification

Layer / File(s) Summary
Update dispatcher display name and expectation
cli/release-automation/internal/automation/release_pr_body.go, cli/release-automation/internal/automation/release_pr_checks_test.go
The dispatcher display-name mapping and its clarified heading test now use “uloop Dispatcher”.

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

Possibly related PRs

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 50.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly reflects the main change: adding the uloop prefix to the dispatcher release heading for consistency.
Description check ✅ Passed The description accurately summarizes the heading rename, test update, and verification, all matching the changeset.
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/uloop-dispatcher-display-name

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

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

@hatayama hatayama merged commit e7b2624 into v3-beta Jul 11, 2026
10 checks passed
@hatayama hatayama deleted the fix/uloop-dispatcher-display-name branch July 11, 2026 15:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant