fix: use kernel-internal app token for release workflow #2
+13
−7
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
GITHUB_TOKENto kernel-internal GitHub App tokenChanges
actions/create-github-app-token@v1step to generate app tokensecrets.GITHUB_TOKENreferences with the app token for release creation and asset uploadsNote
Medium Risk
Changes the authentication mechanism used to create releases and upload assets; misconfigured App secrets/permissions could break releases or alter automation trigger behavior.
Overview
Updates
.github/workflows/release.yamlto generate a GitHub App installation token viaactions/create-github-app-token@v1and use it foractions/create-release@v1plus allactions/upload-release-asset@v1steps.Replaces all
secrets.GITHUB_TOKENusage with the app token (sourced fromADMIN_APP_ID/ADMIN_APP_PRIVATE_KEY) so releases and uploaded artifacts are attributed to—and can trigger workflows as—the GitHub App.Written by Cursor Bugbot for commit f356574. This will update automatically on new commits. Configure here.