From 8407b9e4a9d4a7b8983c6b03d995b02b372f7228 Mon Sep 17 00:00:00 2001 From: callumalpass Date: Thu, 3 Sep 2026 17:17:01 +1000 Subject: [PATCH] Use GitHub App client ID for release updates --- .github/workflows/update-connect-release.yml | 2 +- README.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/update-connect-release.yml b/.github/workflows/update-connect-release.yml index 16940ce..4fbf0e1 100644 --- a/.github/workflows/update-connect-release.yml +++ b/.github/workflows/update-connect-release.yml @@ -106,7 +106,7 @@ jobs: id: app-token uses: actions/create-github-app-token@bcd2ba49218906704ab6c1aa796996da409d3eb1 # v3.2.0 with: - app-id: ${{ vars.RELEASE_AUTOMATION_APP_ID }} + client-id: ${{ vars.RELEASE_AUTOMATION_CLIENT_ID }} private-key: ${{ secrets.RELEASE_AUTOMATION_APP_PRIVATE_KEY }} owner: mdbase-dev repositories: mdbase.dev diff --git a/README.md b/README.md index 439528a..017f3c4 100644 --- a/README.md +++ b/README.md @@ -50,7 +50,7 @@ normal pull request. It never deploys or pushes `main` directly. The same workflow can be run manually with a tag to recover from a delayed npm publication or failed dispatch. -The workflow uses a GitHub App configured as `RELEASE_AUTOMATION_APP_ID` and +The workflow uses a GitHub App configured as `RELEASE_AUTOMATION_CLIENT_ID` and `RELEASE_AUTOMATION_APP_PRIVATE_KEY`. Its installation on this repository needs only `contents: write` and `pull requests: write`. The App token ensures the resulting pull request triggers the ordinary protected `Site checks` workflow.