Repository navigation
chore(openapi): refresh public API snapshot for v0.2.879 - #60
Merged
Merged
Conversation
Co-authored-by: tembo[bot] <208362400+tembo-io[bot]@users.noreply.github.com>
…napi-v0.2.879 Co-authored-by: Cooper <126418690+cooper-gadd@users.noreply.github.com>
cooper-gadd
approved these changes
Oct 23, 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
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
Syncs the committed production OpenAPI snapshot (
openapi/openapi.json) for API release v0.2.879. In that run,deploy-prod / deploy-api / apiand every otherdeploy-prod /job completed successfully. This is the same spec as tembo/mcp#28. It completes the schema update for release PR #59 (release: 0.16.0).Endpoints
None added or removed, so
scalar.config.jsonand the mapping tests are unchanged. The hosted resource mappings already match the committed config.Generated type changes from the spec on existing endpoints:
agents(AgentOptions/AgentOptionsInput): optionalultracodeboolean.runtimes.list: runtime capabilities gain a requiredultracodeModelsstring array.pullRequests.list: optionalincludeStacksquery parameter.billing.usage: optionalcreatedAfter,createdBefore,createdBy, andmodelsquery parameters.Scalar
npm run schema:fetchandnpm run schema:prepare.scalar document validatepasses (OpenAPI 3.1). The snapshot is byte-identical to chore(openapi): refresh public API snapshot for v0.2.879 mcp#28.tembo/tembo-eight-pr-verificationas2.0.39978863369with--no-current. The current version is still2.0.1792000868.tembo/tembo-sdkwas left as is. The upload auto-created SDK version0.5.9on API2.0.39978863369. Its config is identical to0.5.8, and all hosted settings, including thetypescript,rust, andpythontargets, are unchanged.0.5.9(KWZNDosMx3pEP5x8hTZid) for all three targets. It synced intoscalar-next(f8c12db) and opened release PR release: 0.16.0 #59. The same build synced tembo/tembo-rs (release PR release: 0.4.0 tembo-rs#5) and tembo/sdk-python (release PR release: 0.5.0 sdk-python#7).This branch merges the updated
scalar-next, so the snapshot, manifest, and mappings match.Verification
On this branch (generated
scalar-next+ refreshed snapshot), with Node 24:npm run typecheck: passesnpm test: 37 passed, 0 failed, 1 skipped (the dev live test, which needs credentials). Strict schema/manifest/mapping parity passes withoutALLOW_PENDING_SCALAR_MAPPINGS.node scripts/refresh-schema.mjs: public contract unchanged against productionnpm pack --dry-runandbiome format .: passThe release PR was not merged and the version was not promoted.