chore(spec): review production API contract update - #3
Closed
github-actions[bot] wants to merge 1 commit into
Closed
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
justinwlin
added a commit
that referenced
this pull request
Sep 24, 2026
* chore: resync the production spec and document the two generators Pulls the production OpenAPI and regenerates src/generated/schema.ts, which is byte-identical to the daily automation branch (automation/production-spec, PR #3). The upstream additions are cursor pagination on the list endpoints and the account-secrets paths, both additive. Adds the changeset the automation deliberately does not write: without one, a merged spec update never reaches npm, so a consumer pinning this package cannot take up the new types. Documents the relationship with runpod-mcp in docs/development.md. Both repos generate from the same spec — this one emits types, the MCP server emits tool definitions — and the MCP server's hand-written tools call this SDK, so an upstream change has to be taken up in both, in order. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * docs: drop em dashes from the generators section * ci: release the daily spec update when its PR merges The update PR now carries a minor version bump and changelog entry, and the release workflow accepts a merge from automation/production-spec as a release. * ci: publish a merged spec PR even with other changesets pending Also dates the automated changelog entry and links its validation run, and documents how to force a larger bump than minor. --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Refresh the vendored production OpenAPI document and regenerate SDK types.
Source: https://api.runpod.io/v2/openapi.json
Validation run: https://github.com/runpod/typescript-api-sdk/actions/runs/35981987687
Generation, contract tests, typechecking, runtime tests, packed consumers,
and mocked examples passed on Node 24 before this PR was updated.
The SDK checks workflow is also dispatched on this branch for Node 20/22/24.
Check those results before merging.
Review removed or changed operations, request/response types, and compatibility.
Classify the eventual version bump explicitly; a spec diff is not necessarily a patch.
This branch is regenerated from the default branch: put durable fixes there,
rather than editing the bot branch.
No automatic merge, version bump, tag, GitHub release, or npm publication.