ci(release): resolve releaser bot user id at runtime - #52
Merged
Conversation
Avoid hardcoding the bot numeric id so noreply commit emails stay linked if the App is recreated.
There was a problem hiding this comment.
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-idinGIT_AUTHOR_EMAIL/GIT_COMMITTER_EMAILfor the semantic-release step.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
All reported issues were addressed across 1 file
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/users/{app-slug}[bot]Test plan
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./users/{app-slug}%5Bbot%5D), and emituser_id; use it inGIT_AUTHOR_EMAILandGIT_COMMITTER_EMAIL.user_id, and wiring tocommit_email.Written for commit 9c9de1f. Summary will update on new commits.