You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
rc.4 still points users at the removed app deploy: nextActions, READMEs, examples, and dead merge code #203
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).
docs/product/command-spec.mdapp 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).
Activity
No published surface points at the removed app command group (#211)