Skip to content

ci: dispatch the SDK regen on openapi releases - #2231

Merged
mogita merged 2 commits into
mainfrom
ci/cha-5758-sdk-regen-dispatch
Nov 4, 2026
Merged

mogita merged 2 commits into
mainfrom
ci/cha-5758-sdk-regen-dispatch

Conversation

@mogita

@mogita mogita commented Nov 4, 2026

Copy link
Copy Markdown
Contributor

Ticket

https://linear.app/stream/issue/CHA-5758

Problem

The server-side SDKs regenerate only when someone runs generate.sh by hand, so each new spec waits for a person.

Solution

Publishing an openapi-v* release sends repository_dispatch (type openapi-release, the tag in the payload) to getstream-go, whose Regenerate workflow (GetStream/getstream-go#188) regenerates the client and merges the regen PR. The getstream-sdk-bot App key lives only in this repo's sdk-bot environment, which deploys only from openapi-v* tags.

How to verify

  1. Merge after ci: regenerate the client on every protocol release getstream-go#188.
  2. On the next chat production release, the SDK regen run here succeeds and a Regenerate run starts in getstream-go with the same tag.

Publishing an openapi-v* release sends repository_dispatch with the tag to getstream-go, using the getstream-sdk-bot App key from the sdk-bot environment.
@mogita
mogita merged commit 935048b into main Nov 4, 2026
5 checks passed
@mogita
mogita deleted the ci/cha-5758-sdk-regen-dispatch branch November 4, 2026 15:30
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.

2 participants