Skip to content

chore: sync infra OpenAPI specs#520

Open
e2b-generated-code-auto-fixer[bot] wants to merge 1 commit into
mainfrom
chore/sync-infra-specs
Open

chore: sync infra OpenAPI specs#520
e2b-generated-code-auto-fixer[bot] wants to merge 1 commit into
mainfrom
chore/sync-infra-specs

Conversation

@e2b-generated-code-auto-fixer

Copy link
Copy Markdown
Contributor

This PR syncs OpenAPI specs from e2b-dev/infra:

  • spec/openapi.infra.yaml
  • spec/openapi.dashboard-api.yaml

It also regenerates dependent TypeScript API types and applies formatting/lint autofixes.


This PR was automatically created by the sync-infra-specs workflow.

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant