ci(release): resolve releaser bot user id at runtime

[altaywtf]

Summary

• Resolve uinaf-releaser bot user id at runtime for linked noreply emails
• Drop hard-coded 312581908 from release commit identity

Test plan

• CI green on this PR
• Next release attributes commits to uinaf-releaser[bot]

Review aids

Runtime lookup: gh api /users/${app-slug}[bot] --jq .id → {id}+{slug}[bot]@users.noreply.github.com

Made with Cursor

---

Summary by cubic

Resolve release and tap bot GitHub user IDs at runtime to construct correct noreply emails, linking commits to uinaf-releaser[bot] and tap bot profiles. Use a robust, quoted lookup with numeric ID validation and drop the hard-coded 312581908 from the CI workflow.

^{Written for commit a8d9b52. Summary will update on new commits.}

Summary by CodeRabbit

• Bug Fixes
  • Improved automated release and Homebrew tap commit attribution by dynamically resolving bot identity details.
  • Prevented incorrect or outdated commit email information in generated release commits.

[coderabbitai]

📝 Walkthrough

Walkthrough

The CI workflow dynamically resolves GitHub App bot user IDs for release and Homebrew tap commits. It uses these IDs in Git author and committer email values instead of a hardcoded ID.

Changes

Bot identity resolution

Layer / File(s)	Summary
Resolve and apply bot identities .github/workflows/ci.yml	The workflow queries release and tap bot user IDs through the GitHub API. Release and Homebrew tap commit emails use the resolved IDs.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• uinaf/endelito#8: Both changes configure release and Homebrew bot commit identities in the CI workflow.

Suggested reviewers: copilot

Poem

A rabbit checks the workflow trail,
Resolving bot IDs without fail.
Release commits now wear the right name,
Tap commits follow the same claim.
Hop, CI, hop—identity is clear!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
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.
Title check	✅ Passed	The title clearly and concisely describes the runtime resolution of the releaser bot user ID in CI.
Description check	✅ Passed	The description explains the change, includes verification steps, and provides a review aid, but omits several template headings.

---

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

[Copilot]

Pull request overview

This PR updates the release CI workflow to resolve GitHub App bot user IDs at runtime and use them to construct noreply emails that GitHub correctly links to the bot account, removing the previously hard-coded numeric user id.

Changes:

• Added runtime gh api /users/{app-slug}[bot] lookups to fetch bot user IDs.
• Updated GIT_AUTHOR_EMAIL / GIT_COMMITTER_EMAIL (release) and RELEASE_BOT_EMAIL (tap) to use the resolved user id instead of 312581908.
• Added a similar identity-resolution step for the tap bot, gated on new_release_published.

Suppressed comments (1)

.github/workflows/ci.yml:154

• This run: command also contains nested double quotes, which will break shell parsing and prevent tap-bot-identity from setting its output. Rewrite as a small multi-line script to capture the id and append it to $GITHUB_OUTPUT without conflicting quoting.

        run: echo "user-id=$(gh api "/users/${APP_SLUG}[bot]" --jq .id)" >> "$GITHUB_OUTPUT"

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[uinaf-releaser]

🎉 This PR is included in version 1.2.4 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀