Skip to content

web: template path never pairs with a marketplace definition - #5

Merged
reoring merged 1 commit into
mainfrom
fix/template-skips-marketplace-definitions
Nov 9, 2026
Merged

reoring merged 1 commit into
mainfrom
fix/template-skips-marketplace-definitions

Conversation

@reoring

@reoring reoring commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

resolveCreateCatalog picked the first ApplicationStackDefinition with the
template's component count. Marketplace apps are ApplicationStackDefinitions
too (catalogSource set, AppCatalogSource-owned); on Craftsman the first
two-component definition was builder-console, so creating a Next.js app would
deploy the console image under the user's app name. Only platform-shipped
definitions (no catalogSource) are candidates. Mirrors platform #6481.

resolveCreateCatalog picked the first ApplicationStackDefinition with the
template's component count. Marketplace apps are ApplicationStackDefinitions
too (catalogSource set, AppCatalogSource-owned); on Craftsman the first
two-component definition was builder-console, so creating a Next.js app would
deploy the console image under the user's app name. Only platform-shipped
definitions (no catalogSource) are candidates. Mirrors platform #6481.
@reoring
reoring merged commit fb403a9 into main Nov 9, 2026
3 checks passed
@reoring
reoring deleted the fix/template-skips-marketplace-definitions branch November 9, 2026 09:25
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