fix(ci): generate docs from the dispatched SDK release

[cooper-gadd]

Summary

• Honor the sdk-published version payload instead of re-reading npm latest.
• Require an explicit stable version for manual runs.
• Retry the exact npm version for up to two minutes, then fail rather than silently using an older release.
• Preserve the existing single PR branch, validation, and scoped credentials.

Validation

• Workflow lint and diff checks pass.
• Exercised exact-version success, invalid version rejection, stale version rejection, and delayed availability retry.
• Existing docs docs(api): update SDK examples to 0.4.0 #761 was regenerated for 0.4.0; examples and Mintlify checks passed.

Rollout

Merge this before the companion SDK notifier fix. No content, layout, generated SDK code, or credential changes.

Want tembo to make any changes? Add a comment with @tembo and i'll get back to work!

    

---

Note

Low Risk
Changes are limited to a docs CI workflow; no runtime, auth, or generated content logic in this diff.

Overview
The Update released SDK examples workflow no longer resolves @tembo-io/sdk from npm’s latest tag. It now documents the exact version from the sdk-published dispatch payload (client_payload.version) or from a new required workflow_dispatch input.

Before generating examples, CI validates semver, then polls npm for that specific release (up to ~2 minutes). If the package never appears, the job fails with an error instead of falling back to an older release.

^{Reviewed by Cursor Bugbot for commit 53483c0. Bugbot is set up for automated code reviews on this repo. Configure here.}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
tembo	🟢 Ready	View Preview	Sep 15, 2026, 2:16 PM

💡 Tip: Enable Automations to automatically generate PRs for you.