ci: switch SDK generation from PR mode to direct mode#280
Conversation
Generation PRs were never auto-merged (PR #163 has been open since Apr 22 and no release has shipped since v0.4.1). Direct mode commits the regenerated SDK straight to main; the SDK_MERGE_PAT push then triggers the publish workflow via its RELEASES.md path filter.
![perry-the-pr-reviewer[bot]](https://avatars.githubusercontent.com/in/3222961?s=60&v=4){kind=small}
There was a problem hiding this comment.
Perry's Review
Switches SDK generation from rolling-PR mode to direct-commit mode so that daily spec updates ship to main and trigger the publish workflow automatically, unblocking releases that have been stalled since v0.4.1 on Apr 21.
Verdict: 💬 Comments / questions — code is clean (LGTM); APPROVE not posted because the maintainer app does not have pull_requests:write on OpenRouterTeam
Details
Risk: 🟢 Low — CI workflow config change; no Go source, no auth logic, no user-facing API changes
CI: no checks reported (0 runs on this PR head)
Findings: none
Codex (HEAVY_SECONDARY_MODEL): skipped — trivial tier
Research: skipped — trivial tier
Security: no concerns — SDK_MERGE_PAT credential handling unchanged; secret remains a repo secret, passed identically to the Speakeasy action
Test coverage: N/A — workflow config only
Unresolved threads: none
Scope: first review (full)
Review: tier=trivial · model=claude-sonnet-latest · score=0.1
1 participant
Summary
Switches SDK generation from
mode: prtomode: direct. Same issue as OpenRouterTeam/python-sdk#315: OpenAPI spec updates land onmainautomatically, the generator opens a rolling PR, and nothing ever merges it.Current state of this repo:
With
mode: direct, the regenerated SDK commits straight tomain, and that push triggers the Publish workflow via itsRELEASES.mdpath filter to tag a release.Test plan
workflow_dispatch)mainand the Publish workflow tags a new release