Skip to content

SK-2986 use admin service-account PAT for release version-bump push (v3)#372

Merged
Devesh-Skyflow merged 1 commit into
v3from
devesh/SK-2986-release-bypass-token-v3
Jul 24, 2026
Merged

SK-2986 use admin service-account PAT for release version-bump push (v3)#372
Devesh-Skyflow merged 1 commit into
v3from
devesh/SK-2986-release-bypass-token-v3

Conversation

@Devesh-Skyflow

Copy link
Copy Markdown
Collaborator

Same fix as #371, applied to the v3 branch's copy of shared-build-and-deploy.yml.

Why

Branch protection now enforces PR + approval + the Test check on main/v1/v3. Beta/public releases resolve the tag's branch and push the version-bump commit directly to it as github-actions[bot], which is not a ruleset bypass actor — so the push would be rejected.

What

Release actions/checkout now uses PAT_ACTIONS (skyflow-service-it, a repo admin). The persisted credential is reused for the bump push, satisfying the ruleset's Repository Admin bypass.

⚠️ Verify before merge

Requires PAT_ACTIONS to be owned by a repo-admin account with Contents: write. See #371 for details.

Ref: SK-2986

🤖 Generated with Claude Code

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) <noreply@anthropic.com>
Devesh-Skyflow added a commit that referenced this pull request Jul 24, 2026
…v1) (#373)

Same fix as #371 (main) / #372 (v3), applied to the v1 branch's copy of
shared-build-and-deploy.yml. The v1 release pipeline (release-v1.yml)
pushes the version-bump commit directly to the protected v1 branch
(git push origin HEAD:v1) as github-actions[bot], which is not a ruleset
bypass actor, so the push would be rejected.

Point the release checkout at PAT_ACTIONS (skyflow-service-it, a repo
admin) so its credential is persisted and reused for the push, which
then satisfies the ruleset's repo-admin bypass.

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@Devesh-Skyflow
Devesh-Skyflow merged commit ceae600 into v3 Jul 24, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant