fix(ci): use PAT for constraint update commits to trigger CI#5889
Merged
Conversation
The commit-constraint-updates workflow was using the default GITHUB_TOKEN for same-repo PR pushes. Commits pushed with GITHUB_TOKEN do not trigger subsequent workflow runs (GitHub security feature), so CI never ran after constraint updates were committed. Switch to RELEASE_PAT for both checkout and push, matching the fork PR path which already used it. Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]> Signed-off-by: Sébastien Han <[email protected]>
leseb
requested review from
bbrowning,
cdoern,
franciscojavierarceo,
mattf and
raghotham
as code owners
May 18, 2026 18:39
leseb
enabled auto-merge
May 18, 2026 18:39
franciscojavierarceo
approved these changes
May 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Fixes CI not running after the constraint-dependencies update workflow commits changes to Dependabot PRs.
The
commit-constraint-updates.ymlworkflow was usinggithub.token(the defaultGITHUB_TOKEN) for checking out and pushing to same-repo PR branches. GitHub intentionally prevents commits pushed withGITHUB_TOKENfrom triggering subsequent workflows to avoid infinite loops. This meant CI never ran on the constraint update commit, leaving PRs like #5859 without status checks.The fix switches to
RELEASE_PATfor both the checkouttoken:and thegit pushcommand on same-repo PRs, matching the fork PR path which already used it correctly.Test Plan
RELEASE_PATand works correctly, so this aligns the same-repo path