[tembo]

Summary

Syncs the committed production OpenAPI snapshot (openapi/openapi.json) for API release v0.2.881 and updates the endpoint mappings for the operations that were added and removed. This is the same spec as tembo/mcp#29. It completes the schema update for release PR #61 (release: 0.17.0).

Endpoints

scalar.config.json changes (shared by the TypeScript, Rust, and Python targets):

Change	Operation	SDK method
Added	GET /v1/users/{userId}/environment-variables	users.environmentVariables.list
Added	POST /v1/users/{userId}/environment-variables	users.environmentVariables.create (body param body)
Added	DELETE /v1/users/{userId}/environment-variables/{environmentVariableId}	users.environmentVariables.delete
Removed	DELETE /v1/users/{userId}	users.delete
Removed	POST /v1/users/{userId}/subscriptions/reset	users.subscriptions.reset
Removed	POST /v1/organizations/{organizationId}/subscriptions/reset	organizations.subscriptions.reset

tests/schema-contract.test.mjs adds a test that the new users.environment_variables mappings cover these routes and keep the create request body. The existing users and subscription mapping tests now drop the removed routes and assert the old methods are no longer mapped.

Other generated type changes from the spec: projects gain resourceSettings (create/update) and warmPoolSchedule (update), with sizes now optional. Sessions gain automaticSizing (create) and memoryMb (update). Billing usage items become a session | warm-pool union. Artifacts list items add assetUrl. Project/snapshot/build responses drop includeDeps/includeSkills. See tembo/mcp#29 for details.

Scalar

• Ran npm run schema:fetch and npm run schema:prepare. scalar document validate passes. The snapshot is byte-identical to chore(openapi): refresh public API snapshot for v0.2.881 mcp#29.
• Uploaded the prepared schema to tembo/tembo-eight-pr-verification as 2.0.40595111176 with --no-current. The registry's current version is still 2.0.1792000868.
• The upload auto-created SDK version 0.5.10, and Scalar built it (oVyn1k00ZNOl5HtvCahlE) with the previous mappings. That build synced the field changes and dropped the three removed operations (e4d7412).
• Applied only the shared endpoint mapping changes above to the hosted config of tembo/tembo-sdk, creating SDK version 0.5.11 on API 2.0.40595111176. All other hosted settings, including the typescript, rust, and python targets, are unchanged. Before the edit, the hosted resources matched this repo's committed mappings exactly, and afterward they match this PR's scalar.config.json.
• Started the build for 0.5.11 (bhJ3d7hxEAbmoY8QsmiqX). Scalar generated e23c1cb (adds users.environmentVariables.list/create/delete), synced it into scalar-next (2e8b4ef), and refreshed release PR release: 0.17.0 #61. The same build synced tembo/tembo-rs (release PR release: 0.5.0 tembo-rs#6) and tembo/sdk-python (release PR release: 0.6.0 sdk-python#8).

This branch includes the updated scalar-next, so the snapshot, manifest, and mappings match. Release PR #61's contracts check currently fails only on this snapshot/manifest parity (the manifest has the new operations but scalar-next still has the old snapshot). It should pass once this PR is merged into scalar-next.

Verification

On this branch (generated scalar-next + refreshed snapshot + mappings), with Node 24:

• npm run typecheck: passes
• npm test: 38 passed, 0 failed, 1 skipped (the dev live test, which needs credentials). Strict schema/manifest/mapping parity passes without ALLOW_PENDING_SCALAR_MAPPINGS.
• node scripts/refresh-schema.mjs: public contract unchanged against production
• npm pack --dry-run and biome format .: pass

The release PR was not merged and the version was not promoted.

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

      

[tembo]

Requesting review from @cooper-gadd who has experience with the following files modified in this PR:

• openapi/openapi.json