Repository navigation
chore(openapi): refresh public API snapshot for v0.2.882 - #64
Merged
Merged
Conversation
…napi-v0.2.882 Co-authored-by: Darren <68653294+DarrenBaldwin07@users.noreply.github.com>
cooper-gadd
approved these changes
Oct 29, 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
Refreshes the committed source schema (
openapi/openapi.json) withnpm run schema:fetch, following the API release v0.2.882. In that run (attempt 2),deploy-prod / deploy-api / apiand every otherdeploy-prod /job completed successfully. The snapshot is byte-for-byte identical to the one in tembo/mcp#30. This completes the schema update for release PR #63 (release: 0.17.1).No endpoints were added or removed, so
scalar.config.jsonmappings and tests are unchanged. Generated code and version bumps come from the Scalar build.Schema changes (these change generated types)
GETandPATCH /v1/organizations/{organizationId}/settingsadd the booleanfallbackToApiOnSubscriptionLimit. It is required in responses and optional on update.gpt-6.1-terra(GET /v1/models,PATCH /v1/models/{modelName},GET /v1/runtimes, and related organization settings fields).updateOrganizationSettingsandforkSession.Scalar
npm run schema:fetchandnpm run schema:prepare.scalar document validate(@scalar/cli@2.1.0, Node 24) passes.tembo/tembo-eight-pr-verificationas2.0.40795558182with--no-current. The registry's current version is still2.0.1792000868.0.5.12on that API version and built it (hDsTKySncvMQ78bFDgIGS). The hosted config wasn't changed: version0.5.12carries the same config as0.5.11, and its endpoint mappings match this repo'sscalar.config.jsonexactly.0.5.12(XwPT9q2IDJ2wIG5MGOuNF). It produced the same output. Scalar generated488b8d5, synced it intoscalar-next(c7cfdf9), and refreshed release PR release: 0.17.1 #63. The same build synced tembo/tembo-rs (release PR release: 0.5.1 tembo-rs#8) and tembo/sdk-python (release PR release: 0.6.1 sdk-python#9).This branch includes 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: 38 passed, 0 failed, 1 skipped (the dev live test, which needs credentials)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.