From 883dfae0a9b4cf5a6206c82c01b26dd822d1ddb4 Mon Sep 17 00:00:00 2001 From: Eric Viana Date: Mon, 3 Aug 2026 21:33:37 -0300 Subject: [PATCH] chore(ci): run release-please and the release merge with the PAT A push made with GITHUB_TOKEN starts no workflow, so 3.1.1's release PR merged onto main and then nothing published: the run that creates the release and uploads to PyPI never started. The PAT the sync flow already uses keeps the chain alive, and it also lets CI run on the release PR. Claude-Session: https://claude.ai/code/session_01F1stiNzuNtJXoXtiW9ZCbs --- .github/workflows/publish.yaml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/.github/workflows/publish.yaml b/.github/workflows/publish.yaml index 3ae9300..b42d380 100644 --- a/.github/workflows/publish.yaml +++ b/.github/workflows/publish.yaml @@ -23,10 +23,13 @@ jobs: release_created: ${{ steps.release.outputs.release_created }} tag_name: ${{ steps.release.outputs.tag_name }} steps: + # A push made with GITHUB_TOKEN does not start any workflow, so a release + # PR merged with it lands on main and then nothing publishes. Using the + # PAT keeps the chain alive and also lets CI run on the release PR. - uses: googleapis/release-please-action@v4 id: release with: - token: ${{ secrets.GITHUB_TOKEN }} + token: ${{ secrets.SDK_SYNC_PAT }} release-type: python config-file: release-please-config.json manifest-file: .release-please-manifest.json @@ -38,7 +41,7 @@ jobs: # would wait forever. - name: Merge the release PR env: - GH_TOKEN: ${{ secrets.GITHUB_TOKEN }} + GH_TOKEN: ${{ secrets.SDK_SYNC_PAT }} RELEASE_PR: ${{ steps.release.outputs.pr }} run: | # The action's own output is authoritative and immediate. Listing by