chore: sync infra OpenAPI specs#520
Conversation
There was a problem hiding this comment.
LGTM — mechanical OpenAPI spec sync with no dashboard code changes.
Extended reasoning...
Overview
This is an auto-generated PR from the sync-infra-specs workflow. It renames four workspace-admin endpoint paths from /admin/v1/... to /v1/management/... in spec/openapi.dashboard-api.yaml and appends "(v1)" to their summaries, with the corresponding regenerated TypeScript types in dashboard-api.types.ts. Only these two files changed.
Security risks
None. This is a path rename in the OpenAPI contract mirroring an upstream change in e2b-dev/infra; no auth logic, schemas, or request/response shapes changed. The endpoints remain gated behind AdminJWTAuth.
Level of scrutiny
Low. I grepped the dashboard codebase for any references to the old /admin/v1/projects, /admin/v1/users paths or the associated operation IDs (upsertProject, deleteProject, upsertProjectMember, deleteProjectMember, upsertProjectLimits, purgeUser) and found matches only inside the two changed files themselves — no client code in this repo calls these workspace-admin routes, so the rename has no runtime effect on the dashboard app.
Other factors
The types file is auto-generated ("Do not make direct changes to the file") and the diff is consistent with a mechanical regeneration. No outstanding review comments on this PR.
This PR syncs OpenAPI specs from e2b-dev/infra:
spec/openapi.infra.yamlspec/openapi.dashboard-api.yamlIt also regenerates dependent TypeScript API types and applies formatting/lint autofixes.
This PR was automatically created by the sync-infra-specs workflow.