Repository navigation
fix(release): open release PRs as altertable-release[bot] - #109
Merged
Merged
Conversation
Use a repository-scoped GitHub App installation token for Release Please and release branch pushes so automation no longer impersonates a maintainer while still triggering CI. Require app credentials instead of falling back to a personal token or GITHUB_TOKEN. Validation: workflow lint, shellcheck, formatting, Markdown lint, and git diff --check.
redox
approved these changes
Oct 20, 2026
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
2 participants
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.
Release Please currently uses my personal access token from the organization’s
RELEASE_PLEASE_TOKENsecret. As a result, automated release PRs, labels, and releases are attributed to my account.Switch the workflow to the new organization-owned
altertable-releaseGitHub App. Generate a short-lived installation token scoped to this repository and use it for both Release Please and release branch lockfile pushes. This gives release PRs the bot’s identity while preserving automatic CI triggers.The app is installed on
data-app, its repository Actions credentials are configured, and authentication has been verified. Remove the personal-token fallback and the release job’s unnecessaryGITHUB_TOKENwrite permissions, and document the app setup.