Skip to content

feat: improve Prisma deployment completion - #55

Merged
AmanVarshney01 merged 6 commits into
aman/create-prisma-nextfrom
codex/improve-prisma-8-completion
Aug 19, 2026
Merged

feat: improve Prisma deployment completion#55
AmanVarshney01 merged 6 commits into
aman/create-prisma-nextfrom
codex/improve-prisma-8-completion

Conversation

@AmanVarshney01

@AmanVarshney01 AmanVarshney01 commented Aug 19, 2026

Copy link
Copy Markdown
Member

What changed

  • upgrade @clack/prompts to 1.7 and use documented spinner states and native note layout
  • keep Clack keyboard instructions visible
  • consume composer deploy --json instead of scraping human output
  • show the exact workspace, project, deployed app URL, and Console link after deployment
  • convert Management API resource IDs to the raw IDs required by Console routes
  • show progress immediately while checking Prisma authentication and workspace state
  • prompt for a deployment workspace when multiple saved Prisma workspace sessions exist
  • support deterministic agent/CI usage with --yes --deploy --workspace <id-or-name>; unattended runs without the flag use the active workspace
  • use the official auth workspace list/use --json commands, including environment-credential safeguards
  • keep metadata enrichment best-effort so it cannot fail a successful deployment
  • declare Node types in every generated framework tsconfig; keep standard process.env config access
  • make the scaffold-only ending consistent and concise

Verification

  • bun run typecheck
  • bun run test:unit (22 passed)
  • bun run format:check
  • bun run lint
  • bun run build
  • built CLI help exposes --workspace [string]
  • real prisma@next auth whoami/workspace list --json --no-interactive contracts verified
  • real prisma@next project show --project my-app-uoo --json --no-interactive lookup verified
  • framework E2E build passed; the Composer dev E2E remains blocked by the known upstream local emulator port collision

Targets the Prisma 8 PR branch only. This PR does not merge or publish @next.

@coderabbitai

coderabbitai Bot commented Aug 19, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: f021713d-c67d-4ec5-aa63-4cbddb60e07e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Comment @coderabbitai help to get the list of available commands.

@github-actions

github-actions Bot commented Aug 19, 2026

Copy link
Copy Markdown

@next preview published

  • Version: 0.4.2-next.55.211.1
  • Tag: next
  • Trigger: PR has the release:next label, so this is available as create-prisma@next
  • Run with Bun: bunx create-prisma@next
  • Run with npm: npx create-prisma@next
  • Run with Yarn: yarn dlx create-prisma@next
  • Run with pnpm: pnpm dlx create-prisma@next
  • Run with Deno: deno run -A npm:create-prisma@next
  • Workflow run: https://github.com/prisma/create-prisma/actions/runs/32232889903

@AmanVarshney01 AmanVarshney01 added the release:next Publish this PR preview to the npm next dist-tag label Aug 19, 2026
@AmanVarshney01
AmanVarshney01 merged commit 0be6e74 into aman/create-prisma-next Aug 19, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release:next Publish this PR preview to the npm next dist-tag

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant