From 4efa3ee72420ed0e619a3167eafcb5bba01e6e97 Mon Sep 17 00:00:00 2001 From: Devesh-Skyflow Date: Fri, 24 Jul 2026 09:08:24 +0530 Subject: [PATCH] SK-2986 use admin service-account PAT for release version-bump push Same fix as the main branch: point the release checkout at PAT_ACTIONS (skyflow-service-it, a repo admin) so the persisted credential is reused for the automated version-bump push. Ensures beta/public releases cut from the v3 branch aren't rejected by the branch-protection ruleset, which github-actions[bot] cannot bypass. Co-Authored-By: Claude Opus 4.8 (1M context) --- .github/workflows/shared-build-and-deploy.yml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/.github/workflows/shared-build-and-deploy.yml b/.github/workflows/shared-build-and-deploy.yml index 15d9088a..900c2aef 100644 --- a/.github/workflows/shared-build-and-deploy.yml +++ b/.github/workflows/shared-build-and-deploy.yml @@ -57,6 +57,11 @@ jobs: - uses: actions/checkout@v2 with: fetch-depth: 0 + # PAT of the skyflow-service-it admin service account. Persisted by + # checkout and reused for the automated version-bump push below, so + # that push satisfies the branch-protection ruleset's repo-admin + # bypass (github-actions[bot] is not a bypass actor). See SK-2986. + token: ${{ secrets.PAT_ACTIONS }} - name: Set up maven or jfrog repository uses: actions/setup-java@v1