Repository navigation
chore(openapi): refresh snapshot for v0.2.891 and map new endpoints - #78
Merged
Merged
Conversation
Co-authored-by: tembo[bot] <208362400+tembo-io[bot]@users.noreply.github.com>
…napi-v0.2.891 Co-authored-by: Cooper <126418690+cooper-gadd@users.noreply.github.com>
Co-authored-by: tembo[bot] <208362400+tembo-io[bot]@users.noreply.github.com>
Contributor
Author
|
Requesting review from @cooper-gadd who has experience with the following files modified in this PR:
|
cooper-gadd
approved these changes
Nov 11, 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 public OpenAPI snapshot (
openapi/openapi.json) from the production spec deployed by release v0.2.891 and maps the 11 new endpoints. The snapshot is byte-identical to the MCP snapshot in tembo/mcp#38.Spec changes:
GET/POST /v1/folders,PATCH/DELETE /v1/folders/{folderId}.GET /v1/sessionsaddsfolderIdandinFolderfilters.GET/POST /v1/organizations/{organizationId}/roles,GET/PATCH/DELETE /v1/organizations/{organizationId}/roles/{roleId}. Archiving a role (DELETE) requires areplacementRoleIdbody.roleis replaced byroleIdon create (required) and update (optional). This is a breaking SDK change, so the release is a minor bump (pre-1.0).GET /v1/artifacts/assets/{assetId}(retrieve a signed asset URL) andGET /v1/projects/defaults.No endpoints were removed.
Mapping
scalar.config.jsonadds these sharedresources(used by the TypeScript, Rust, and Python targets):folders:list,create,update,delete(new top-level resource)organizations.roles:list,create,retrieve,update,delete.deleteis anhttpmethod withbodyParamName: "body"for the required replacement role.artifacts.retrieve_asset_url(followsintegrations.retrieve_sync_status)projects.retrieve_defaults(next toupdate_defaults)tests/schema-contract.test.mjsadds a test that the mappings cover the new routes and keep their request bodies, including the roleDELETEbody. It fails without the mappings.tests/sdk.test.mjs: Scalar's manifest names the new artifact operationretrieveAssetUrl, but the TypeScript emitter writesclient.artifacts.retrieveAssetURL(likeassetID). The contract test now resolves thatURLcasing when it checks that each manifest operation exists on the client. Without this, the release PR'scontractscheck would fail once this snapshot lands.Generated code and version bumps are left to Scalar.
Scalar
tembo/tembo-eight-pr-verificationas non-current version2.0.42923047796. Scalar auto-built it as SDK0.5.20with the existing mappings (buildvhHc4MqvrjOYbgRMTFO88).resourcesmappings changed. All other hosted settings, including thetypescript,rust, andpythontargets, are unchanged.0.5.21was built (buildSIhAFMcV0C69P0vi7nVeI) and synced intoscalar-nextasfeat(api): add operation organizations.roles.list (+10 more changes). It refreshed release PR release: 0.23.0 #77 (release: 0.23.0), release: 0.11.0 tembo-rs#18, and release: 0.12.0 sdk-python#17.scalar-nextso the generated manifest includes the new operations.Testing
npx --package=@scalar/cli@2.1.0 scalar document validate openapi/scalar.openapi.json: valid (OpenAPI 3.1)npm run typechecknpm test, with and withoutALLOW_PENDING_SCALAR_MAPPINGS: 40 passed, 0 failednpm pack --dry-runnode scripts/refresh-schema.mjs: mappings cover production, public contract unchangedbiome format: no changes