chore(spec): review production API contract update - #3
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
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/35502470366
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.