Skip to content

web: create new repositories at the platform-resolved destination (APT-799) - #13

Draft
reoring wants to merge 1 commit into
mainfrom
feat/apt-799-repository-destination
Draft

reoring wants to merge 1 commit into
mainfrom
feat/apt-799-repository-destination

Conversation

@reoring

@reoring reoring commented Nov 12, 2026

Copy link
Copy Markdown
Contributor

Draft. Depends on appthrust/platform#6680.

Before merge:

  1. platform#6680 merged, @appthrust/api-schema 0.1.5 published (tag npm/v0.1.5).
  2. Bump web/package.json to ^0.1.5, delete the stand-in web/src/api/repository-destination.ts and the router spread in web/src/api/client.ts, drop the cast in submit.ts.

Must ship together with the platform change: the server rejects the connection assertion the current Console sends, and this Console needs the new destination routes.

Checks: bun test src (1267 pass), tsc --noEmit. Not verified in a browser.

…T-799)

The Console no longer picks a source connection or composes the image path.
It shows the destination the platform resolved, blocks creation with the
reason when none resolves, and lets a Project admin set the Project default.
Uses a local stand-in for the new API types until @appthrust/api-schema 0.1.5
is published.
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