Skip to content

chore: regenerate warpcache-ts-sdk from the current spec - #6

Draft
janakiram7755 wants to merge 1 commit into
fix/vulnsfrom
chore/refresh-sdk
Draft

chore: regenerate warpcache-ts-sdk from the current spec#6
janakiram7755 wants to merge 1 commit into
fix/vulnsfrom
chore/refresh-sdk

Conversation

@janakiram7755

Copy link
Copy Markdown
Collaborator

Stacked on #5. The vendored SDK was generated Oct 2024; backend-cache's docs/swagger.json last moved Jan 2026.

Regenerated with the pinned generator (7.4.0, via the openapitools/openapi-generator-cli docker image since it needs a JVM), running both passes the pipeline does — typescript-axios then openapi-typescript-codegen for schemas/.

CommonsAzureBlobReserveCacheResponse gains blob_name and container_name, which the service returns and our types did not have. /ping and /v1/instrumentation/operation drop out of the api — both carry x-internal: true, which the generator honours, and the annotation postdates the vendored copy. Neither is called from our source. No model files added or removed.

Verified: 63/63 tests, build clean, cacheHttpClient.js compiles byte-identical, and cache versions still match published 1.4.13 across all 10 combinations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant