Skip to content

Commit 247d0d0

Browse files
committed
fix(ci): use GitHub App token for release-please
Release-please was using GITHUB_TOKEN to create and update PR #130. GitHub suppresses pull_request events for pushes made with GITHUB_TOKEN (to prevent recursive workflows), so the CI workflow never triggered and the CI Gate required status check never appeared, permanently blocking the release PR. Switch to the attune-release-bot GitHub App token so release-please PR pushes generate real pull_request events that trigger CI. Signed-off-by: Sebastien Tardif <sebtardif@ncf.ca>
1 parent 89ae79d commit 247d0d0

1 file changed

Lines changed: 9 additions & 0 deletions

File tree

.github/workflows/release.yaml

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -38,11 +38,20 @@ jobs:
3838
- uses: step-security/harden-runner@9af89fc71515a100421586dfdb3dc9c984fbf411 # v2.19.4
3939
with:
4040
egress-policy: audit
41+
# Use the GitHub App token so that release-please PR pushes
42+
# trigger pull_request events (GITHUB_TOKEN suppresses them,
43+
# which prevents the CI Gate status check from appearing).
44+
- uses: actions/create-github-app-token@bcd2ba49218906704ab6c1aa796996da409d3eb1 # v3.2.0
45+
id: app-token
46+
with:
47+
app-id: ${{ secrets.APP_ID }}
48+
private-key: ${{ secrets.APP_PRIVATE_KEY }}
4149
- uses: googleapis/release-please-action@5c625bfb5d1ff62eadeeb3772007f7f66fdcf071 # v4
4250
id: release
4351
with:
4452
config-file: release-please-config.json
4553
manifest-file: .release-please-manifest.json
54+
token: ${{ steps.app-token.outputs.token }}
4655

4756
release:
4857
name: Release

0 commit comments

Comments
 (0)