From e61d97083aa2241b6fdc241e2df6b9cccd82db84 Mon Sep 17 00:00:00 2001 From: Joseph Mearman Date: Sun, 13 Sep 2026 17:21:01 +0100 Subject: [PATCH] chore(ci): remove the app-token identity diagnostic from the release job The echo step existed only to determine, empirically, which app-id/ private-key secret pair actually resolves to the app named in the main-protection ruleset's bypass_actors entry. That's now settled (GH_APP_ID/GH_APP_PRIVATE_KEY, confirmed by v1.3.0's real release commit and tag landing on main), so the log line serves no ongoing purpose. --- .github/workflows/ci.yml | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 87dd105..80003d7 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -125,7 +125,7 @@ jobs: pull-requests: write id-token: write steps: - # Minted before checkout, not after: @semantic-release/git's changelog commit-back needs a real `git push` against main, which the branch ruleset refuses for the workflow's own token — only the exadev App is a permitted bypasser. Generating it first lets checkout itself configure git's credentials with it. + # Minted before checkout, not after: @semantic-release/git's changelog commit-back needs a real `git push` against main, which the branch ruleset refuses for the workflow's own token — only the exadev App is a permitted bypasser. Generating it first lets checkout itself configure git's credentials with it. Uses GH_APP_ID/GH_APP_PRIVATE_KEY specifically: secrets.APP_ID/APP_PRIVATE_KEY authenticates as a different app (exaclaude) which the branch ruleset's bypass list doesn't name. - name: Generate ExaDev App token id: app-token uses: actions/create-github-app-token@v2 @@ -135,10 +135,6 @@ jobs: owner: ExaDev repositories: cc-peer - # Diagnostic: identifies which App actually authenticated the token below, since the main-protection ruleset's bypass_actors entry only recognises app ID 1008913 (slug "exadev") and a mismatched secret would authenticate fine while silently failing the later bypass check. secrets.APP_ID/APP_PRIVATE_KEY was confirmed (PR #33) to authenticate as "exaclaude" instead; trying GH_APP_ID/GH_APP_PRIVATE_KEY here to find the pair that actually resolves to "exadev". - - name: Diagnose app token identity - run: echo "authenticated as app-slug=${{ steps.app-token.outputs.app-slug }}" - - uses: actions/checkout@v5 with: token: ${{ steps.app-token.outputs.token }}