Skip to content

ci: authenticate release-please via GitHub App token - #292

Merged
Cafe137 merged 1 commit into
masterfrom
ci/release-please-via-app-token
May 19, 2026
Merged

ci: authenticate release-please via GitHub App token#292
Cafe137 merged 1 commit into
masterfrom
ci/release-please-via-app-token

Conversation

@darkobas2

Copy link
Copy Markdown
Contributor

Problem

release.yaml calls googleapis/release-please-action@v4 with secrets.REPO_GHA_PAT, last rotated 2021-11-09. The token now returns Bad credentials from the GitHub API (failing run), so no release PRs are being created.

Fix

Generate a fresh GitHub App token at workflow runtime using actions/create-github-app-token@v1 with the org-level BEE_RUNNER_CLIENT_ID + BEE_RUNNER_KEY secrets, and pass that into release-please. Same pattern as ethersphere/create-swarm-app#13.

Prerequisite

BEE_RUNNER_KEY is currently shared at the org level only with selected repos. An org admin needs to add bee-factory to its repository allowlist (Settings → Secrets and variables → Actions → BEE_RUNNER_KEY → repository access). BEE_RUNNER_CLIENT_ID is already visible to this repo.

After that grant, the next push to master should run release-please successfully.

🤖 Generated with Claude Code

REPO_GHA_PAT was last rotated in 2021 and now returns 'Bad
credentials', blocking release PR creation. Switch to the org-level
GitHub App (BEE_RUNNER_CLIENT_ID + BEE_RUNNER_KEY) using
actions/create-github-app-token so release-please runs on a token
that doesn't need manual rotation.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@Cafe137

Cafe137 commented May 19, 2026

Copy link
Copy Markdown
Collaborator

@darkobas / @darkobas2 please let me know when this repository is on the allowlist, I'll merge after that

@darkobas2

Copy link
Copy Markdown
Contributor Author

Yeah its done. Lets try it

@Cafe137
Cafe137 merged commit d12880c into master May 19, 2026
1 check passed
@Cafe137
Cafe137 deleted the ci/release-please-via-app-token branch May 19, 2026 10:48
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.

3 participants