Skip to content

Auto-update OpenAPI spec from vast@4b30d7ba - #905

Closed
Gobind-Vast wants to merge 1 commit into
mainfrom
auto/openapi-update-4b30d7ba
Closed

Auto-update OpenAPI spec from vast@4b30d7ba#905
Gobind-Vast wants to merge 1 commit into
mainfrom
auto/openapi-update-4b30d7ba

Conversation

@Gobind-Vast

Copy link
Copy Markdown
Collaborator

Automated update of the OpenAPI spec from the vast backend.

Auto-generated split files are under api-reference/openapi/yaml/auto_*.yaml; openapi.yaml is the build.py-aggregated result.

Source commit: https://bitbucket.org/vastai/vast/commits/4b30d7ba714e2cc69bfd7723b40184525454cb99

Mintlify will deploy a preview — check the preview URL to verify the API reference renders correctly before merging.


⚠️ Hand-curated docs review needed

Curated documentation lives in vast:scripts/openapi_overrides.json and is merged over the auto-generated spec on every regeneration. The checks below flag places where it may have drifted from the code.

Parameters with placeholder descriptions

Newly introspected parameters with no curated description — they render as "The " until documented in param_docs:

  • PUT /api/v0/commands/rsync/dst_id, src_id

@mintlify

mintlify Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
vastai-80aa3a82 🟢 Ready View Preview Aug 5, 2026, 11:04 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@Gobind-Vast

Copy link
Copy Markdown
Collaborator Author

Closing as part of a bulk cleanup of auto-generated OpenAPI PRs.

These were opened by the step-openapi-docs-preview and step-openapi-push-to-docs Bitbucket Pipelines steps in vastai/vast. Because the bootstrap docs PR (#163) was never merged, every run regenerated the entire cutover diff against main (~272 files, +24697/-20171) instead of a small per-merge delta -- so these PRs are all near-identical, mutually conflicting, and not individually reviewable.

Those two pipeline steps have now been removed (vastai/vast PR #5269, merged 2026-08-06), so no further auto PRs will be opened against this repo.

No documentation change is being lost. The API reference is generated from the vast backend and can be regenerated at any time from a fresh baseline. The publishing steps will be re-landed only once a regenerated baseline has landed on main and per-merge diffs are small enough to review.

Closed by an automated cleanup; no action needed from reviewers.

@Gobind-Vast Gobind-Vast closed this Aug 7, 2026
@Gobind-Vast
Gobind-Vast deleted the auto/openapi-update-4b30d7ba branch August 7, 2026 00:18
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