From df3d0037d5ba97e574c807690584601fca679a79 Mon Sep 17 00:00:00 2001 From: Shihyu Ho Date: Wed, 24 Jun 2026 14:18:52 +0800 Subject: [PATCH] ci: use CI App token for release-please Source release-please-action's token from the softleader CI App (actions/create-github-app-token@v3) instead of the default GITHUB_TOKEN, matching bump-spring. GITHUB_TOKEN-produced events don't trigger workflows, so a future on-release / on-push-tags listener wouldn't fire on a release. The App token re-enables those events, fixes the autorelease label quirk, and lets commitlint lint the release PR. No recursion risk: the release PR is human-merged and release-please's own commits land on the release-please-- side branch. Co-authored-by: Claude Opus 4.8 (1M context) --- .github/workflows/release-please.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/.github/workflows/release-please.yml b/.github/workflows/release-please.yml index 6dcaae9..628102c 100644 --- a/.github/workflows/release-please.yml +++ b/.github/workflows/release-please.yml @@ -25,9 +25,15 @@ jobs: tag_name: ${{ steps.rp.outputs.tag_name }} sha: ${{ steps.rp.outputs.sha }} steps: + - uses: actions/create-github-app-token@v3 + id: app-token + with: + client-id: ${{ vars.CI_APP_CLIENT_ID }} + private-key: ${{ secrets.CI_APP_PRIVATE_KEY }} - uses: googleapis/release-please-action@v5.0.0 id: rp with: + token: ${{ steps.app-token.outputs.token }} config-file: .release-please-config.json manifest-file: .release-please-manifest.json