ci: restore sdk regen pr creation#81
Merged
Merged
Conversation
podonos-eunseo
approved these changes
Jul 14, 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.
Summary
actions/checkout@v7from persisting the GitHub App credential beforecreate-pull-requestrunspeter-evans/create-pull-requestfrom v6 to Node 24-based v8Root cause
The prod regeneration completed generation and tests, then failed while opening the PR. Checkout v7 persisted its credential through Git's include-file configuration, while create-pull-request v6 added another local authorization header. Git 2.54 sent both headers and GitHub rejected the request with HTTP 400.
Validation
actionlint .github/workflows/regen.ymlgit diff origin/main...HEAD --checkmake lintmake test(305 passed)Follow-up after merge
The stranded prod spec
0b38b5c071f4b97f634faed780611d52969ea716will be regenerated through a manual workflow dispatch. The stale waiting PyPI 0.10.0 promotion will be cancelled; only the resulting 0.11.0 release will be promoted.