Skip to content

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

Merged
altaywtf merged 2 commits into
mainfrom
ci/runtime-release-bot-identity
Aug 3, 2026
Merged

ci(release): resolve releaser bot user id at runtime#52
altaywtf merged 2 commits into
mainfrom
ci/runtime-release-bot-identity

Conversation

@altaywtf

@altaywtf altaywtf commented Aug 3, 2026

Copy link
Copy Markdown
Member

Summary

  • Resolve the release bot numeric user id at runtime via /users/{app-slug}[bot]
  • Use that id in noreply commit emails instead of a hardcoded value

Test plan

  • CI green on this PR
  • Next release commit email links to putio-releaser[bot]

Review aids

Before: 283001373+${{ steps.release-bot.outputs.app-slug }}[bot]@…
After: ${{ steps.release-bot-identity.outputs.user-id }}+${{ steps.release-bot.outputs.app-slug }}[bot]@…

Made with Cursor


Summary by cubic

Resolve the release bot’s numeric user ID at runtime and use it in noreply commit emails. Harden the lookup and apply the same fix to the Homebrew releaser so commits stay linked to putio-releaser[bot] even if the GitHub App is recreated.

  • Bug Fixes
    • Resolve bot user ID via GitHub API using an explicit bash shell and URL-encoded path (/users/{app-slug}%5Bbot%5D), and emit user_id; use it in GIT_AUTHOR_EMAIL and GIT_COMMITTER_EMAIL.
    • Mirror the change for the Homebrew tap: URL-encoded lookup, bash shell, output name user_id, and wiring to commit_email.

Written for commit 9c9de1f. Summary will update on new commits.

Avoid hardcoding the bot numeric id so noreply commit emails stay linked if the App is recreated.
Copilot AI review requested due to automatic review settings August 3, 2026 19:19

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR improves the release workflow’s commit authorship by resolving the GitHub App bot account’s numeric user ID at runtime (via the GitHub API) and using it in the users.noreply.github.com commit email format, avoiding reliance on a hardcoded ID.

Changes:

  • Add a “Resolve release bot identity” step that fetches /users/{app-slug}[bot] and extracts the numeric .id.
  • Export the resolved ID as a workflow step output (user-id).
  • Use the resolved user-id in GIT_AUTHOR_EMAIL / GIT_COMMITTER_EMAIL for the semantic-release step.

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

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All reported issues were addressed across 1 file

Reply with feedback, questions, or to request a fix.

Re-trigger cubic

Comment thread .github/workflows/ci.yml Outdated
Use an explicit bash shell, URL-encode the [bot] path segment, and emit user_id so Actions expressions do not treat the output name as subtraction.
@altaywtf
altaywtf merged commit 2897e77 into main Aug 3, 2026
7 checks passed
@altaywtf
altaywtf deleted the ci/runtime-release-bot-identity branch August 3, 2026 19:36
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.

2 participants