Add Composer build-and-deploy plugin for desktop preview - #7
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
Prepare a focused desktop-local Prisma plugin so a user can select Prisma, ask to build and deploy an app, and have the agent handle setup, local verification, and deployment. This is a reviewable local preview; first-time onboarding and public distribution remain gated below.
Changes
0.4.0-dev.4portable plugin underplugins/prisma, with approved Prisma branding and new/existing-app starter prompts. Add an opt-inprisma-previewmarketplace underplugins/; preserve the existing root marketplace and installer routes until the complete public bundle and onboarding are ready.0.21.0reference. Keep dependency pins, managed browser login, and narrowly verified recovery commands in one supporting reference.Why
Composer owns its API reference; the plugin owns completing the user journey. This avoids another starter or duplicated API guidance while requiring observable local persistence and live functionality. Browser signup alone cannot establish a connection: the workflow requires CLI completion, authenticated identity, and remote workspace access before provisioning.
Validation
67b50e78fbb6cafd00bb99b0e56fe8a49e4a7190219474bf1b9be933f08bbcbb.docs/validation.md.Before publication
auth login --ui-context prisma-plugin(implemented in Add plugin-specific login completion guidance prisma-cli#281; coordinated release PR Bump to version 8.0.0-rc.16 prisma-cli#282 remains unmerged). The reference explicitly blocks using that option with the retained8.0.0-rc.15baseline.