Skip to content

Use RELEASE_PAT to bypass ruleset in release workflow#2913

Merged
adamtheturtle merged 1 commit intomainfrom
fix-release-ruleset-bypass
Feb 15, 2026
Merged

Use RELEASE_PAT to bypass ruleset in release workflow#2913
adamtheturtle merged 1 commit intomainfrom
fix-release-ruleset-bypass

Conversation

@adamtheturtle
Copy link
Member

@adamtheturtle adamtheturtle commented Feb 15, 2026

The release workflow fails because git-auto-commit-action cannot push the CHANGELOG bump commit directly to main — the repository ruleset requires 3 status checks to pass, and the default GITHUB_TOKEN cannot bypass rulesets.

Use the existing RELEASE_PAT organization secret (a PAT with admin bypass privileges) in the checkout step so that the push succeeds.


Note

Medium Risk
Changes the credentials used by the release pipeline to an elevated PAT; misconfiguration or leakage could increase repository write access, though the change is small and isolated to the workflow.

Overview
Updates the Release GitHub Actions workflow to checkout with a dedicated RELEASE_PAT (instead of the default GITHUB_TOKEN) so the git-auto-commit-action changelog bump commit can push to main even when repository rulesets require status checks.

Written by Cursor Bugbot for commit 35b3e9f. This will update automatically on new commits. Configure here.

@adamtheturtle adamtheturtle merged commit a6f8e1d into main Feb 15, 2026
10 of 13 checks passed
@adamtheturtle adamtheturtle deleted the fix-release-ruleset-bypass branch February 15, 2026 08:41
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