Skip to content

fix(ci): use GitHub App token for semantic-release#4

Merged
polaz merged 1 commit into
mainfrom
fix/use-github-app-token-for-semantic-release
May 6, 2026
Merged

fix(ci): use GitHub App token for semantic-release#4
polaz merged 1 commit into
mainfrom
fix/use-github-app-token-for-semantic-release

Conversation

@polaz
Copy link
Copy Markdown
Contributor

@polaz polaz commented May 6, 2026

Run Release workflow failed with @semantic-release/github: Variable \$owner of type String! was provided invalid value — default GITHUB_TOKEN can't write to default branch (protected by ruleset main-protection).

Switch to GitHub App installation token via actions/create-github-app-token@v3 — same pattern as structured-world/gitlab-mcp release-please.yml.

Requires org secrets (already configured): RELEASER_APP_ID, RELEASER_APP_PRIVATE_KEY.

Test plan

  • After merge: next push triggers Release workflow which:
    • mints app token
    • semantic-release pushes chore(release): commit + tag through ruleset
    • npm publish via OIDC succeeds

… pattern)

Default GITHUB_TOKEN can't write to default branch (protected by
ruleset 'main-protection'). Use GitHub App installation token —
same pattern as structured-world/gitlab-mcp release-please.yml.

Requires org secrets: RELEASER_APP_ID + RELEASER_APP_PRIVATE_KEY
(already configured org-wide for releases).
@polaz polaz merged commit d657fdf into main May 6, 2026
1 check passed
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.

1 participant