Summary
The app command group was removed in the rc line (deploys now come from git push / Console / Composer), but 8.0.0-rc.4 still tells users to run it, and it no longer resolves:
prisma-cli project create my-app --json
# nextActions: [{ "kind": "run-command", "label": "prisma-cli app deploy", "command": "prisma-cli app deploy" }]
prisma-cli app deploy
# CLI.UNKNOWN_COMMAND: No command registered for `app`, did you mean `lsp`?
Reproduced on 8.0.0-rc.4 (repo-built, since the published CLI currently crashes at startup — see #202).
Known stale references at HEAD (fef263e)
nextSteps/notice strings that emit a nonexistent command:
packages/cli/src/lib/project/resolution.ts:276
packages/cli/src/lib/project/setup.ts:90
packages/cli/src/commands/project/presentation.ts:12-13
packages/cli/src/controllers/app-env.ts:374
packages/cli/src/lib/app/env-file.ts:39
Docs and examples:
packages/prisma/README.md (npx prisma app deploy; also claims "The package binary is prisma-cli, not prisma" while the manifest declares prisma)
packages/cli/README.md, root README.md (app deploy flows)
examples/hello-world/README.md, examples/next-smoke/README.md (pre-S8 spellings: app list-env, app list-deploys, app show-deploy, app update-env; hello-world also claims deploy bootstraps a prisma.config.ts project pin, contradicting .prisma/local.json)
docs/product/command-spec.md app deploy/app build/app run sections; docs/product/resource-model.md uses the app noun throughout; docs/architecture/overview.md:54 says the linked project id lives in prisma.config.ts
docs/reference/glossary.md still says the beta ships on the latest dist-tag, contradicting docs/oss/versioning.md (rc on next)
Dead code:
packages/cli/src/lib/app/compute-config.ts: mergeComputeDeployInputs / mergeComputeLocalInputs are only referenced by tests now that app deploy/app build/app run are gone.
Found while validating the docs against rc.4 (prisma/web#8151).
🤖 Filed with Claude Code on behalf of datta@prisma.io
Summary
The
appcommand group was removed in the rc line (deploys now come from git push / Console / Composer), but 8.0.0-rc.4 still tells users to run it, and it no longer resolves:Reproduced on 8.0.0-rc.4 (repo-built, since the published CLI currently crashes at startup — see #202).
Known stale references at HEAD (fef263e)
nextSteps/notice strings that emit a nonexistent command:packages/cli/src/lib/project/resolution.ts:276packages/cli/src/lib/project/setup.ts:90packages/cli/src/commands/project/presentation.ts:12-13packages/cli/src/controllers/app-env.ts:374packages/cli/src/lib/app/env-file.ts:39Docs and examples:
packages/prisma/README.md(npx prisma app deploy; also claims "The package binary is prisma-cli, not prisma" while the manifest declaresprisma)packages/cli/README.md, rootREADME.md(app deployflows)examples/hello-world/README.md,examples/next-smoke/README.md(pre-S8 spellings:app list-env,app list-deploys,app show-deploy,app update-env; hello-world also claims deploy bootstraps aprisma.config.tsproject pin, contradicting.prisma/local.json)docs/product/command-spec.mdapp deploy/app build/app runsections;docs/product/resource-model.mduses theappnoun throughout;docs/architecture/overview.md:54says the linked project id lives inprisma.config.tsdocs/reference/glossary.mdstill says the beta ships on thelatestdist-tag, contradictingdocs/oss/versioning.md(rc onnext)Dead code:
packages/cli/src/lib/app/compute-config.ts:mergeComputeDeployInputs/mergeComputeLocalInputsare only referenced by tests now thatapp deploy/app build/app runare gone.Found while validating the docs against rc.4 (prisma/web#8151).
🤖 Filed with Claude Code on behalf of datta@prisma.io