Skip to content

ci(sdk-regen): use SDK_REGEN_GITHUB_PAT for TS regen so downstream CI fires#941

Open
leggetter wants to merge 1 commit into
mainfrom
ci/sdk-regen-pat
Open

ci(sdk-regen): use SDK_REGEN_GITHUB_PAT for TS regen so downstream CI fires#941
leggetter wants to merge 1 commit into
mainfrom
ci/sdk-regen-pat

Conversation

@leggetter
Copy link
Copy Markdown
Collaborator

Closes #939.

What

Two-site swap of secrets.GITHUB_TOKENsecrets.SDK_REGEN_GITHUB_PAT in the TS SDK regen workflow chain. Go and Python keep GITHUB_TOKEN (their bot PRs aren't gated by a TS-only test suite).

File Change
.github/workflows/sdk_generation_outpost_ts.yaml The standalone TS dispatcher
.github/workflows/sdk-generate-on-release.yml Only the generate-ts job (Go and Python jobs unchanged)

Why

GitHub Actions deliberately suppresses workflow triggers for PRs opened with GITHUB_TOKEN. Empirically confirmed today: Go (#935) and Python (#937) v1.4.0 bot PRs merged without spec-sdk-tests.yml (#925) or spec-sdk-tests-vs-release.yml (#927) firing — the whole point of those workflows was to gate exactly that scenario.

By swapping to a PAT, PR events look like they came from a user and trigger downstream workflows normally.

Required before merge

Create the SDK_REGEN_GITHUB_PAT repo secret. Fine-grained PAT on hookdeck/outpost with:

  • Contents: read + write (push branches)
  • Pull requests: read + write (open PRs)
  • Workflows: read + write (in case Speakeasy ever modifies workflow files)

Test plan

  • PAT secret configured.
  • After this lands, dispatch sdk_generation_outpost_ts.yaml and confirm the resulting bot PR triggers spec-sdk-tests.yml.
  • Next natural TS regen (post-Outpost-release) also triggers it.

🤖 Generated with Claude Code

… fires

Closes #939.

GitHub Actions suppresses workflow triggers for PRs opened with
GITHUB_TOKEN. The TS SDK regen was opening its PR with GITHUB_TOKEN,
so spec-sdk-tests.yml (#925) and spec-sdk-tests-vs-release.yml (#927)
never fired on the bot's PR.

Swap to a PAT in the two sites that open TS regen PRs:
  * sdk_generation_outpost_ts.yaml (manual dispatcher)
  * sdk-generate-on-release.yml (generate-ts job)

Requires SDK_REGEN_GITHUB_PAT repo secret with Contents, Pull requests,
and Workflows read+write.
Copilot AI review requested due to automatic review settings May 29, 2026 19:19
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Swaps the default GITHUB_TOKEN for a user-provided PAT (SDK_REGEN_GITHUB_PAT) in the two TypeScript SDK generation entry points, so that bot-opened SDK regen PRs trigger downstream pull_request workflows (spec-sdk-tests.yml, spec-sdk-tests-vs-release.yml). GitHub Actions intentionally suppresses workflow runs for PRs opened with GITHUB_TOKEN; using a PAT makes the PR look user-authored and re-enables the gates.

Changes:

  • TS manual dispatch workflow now passes SDK_REGEN_GITHUB_PAT as github_access_token.
  • Release-triggered TS regen job in sdk-generate-on-release.yml likewise swapped to the PAT.
  • Go and Python generation paths intentionally left on GITHUB_TOKEN.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
.github/workflows/sdk_generation_outpost_ts.yaml Manual TS dispatcher now uses the PAT secret for the reusable generator call.
.github/workflows/sdk-generate-on-release.yml generate-ts job uses the PAT; generate-go/generate-python unchanged.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

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.

ci: bot-opened SDK regen PRs don't trigger spec-sdk-tests (GITHUB_TOKEN limitation)

2 participants