v0.34.0

Composer 0.34.0 runs on Prisma ORM 8.0.0-rc.20 and @prisma/cli-engine 0.9.0, in the prisma CLI 8.0.0-rc.26 or later.

Breaking: apps that use the auth module must sign their databases

The auth pack's contract no longer stores its Tstz type alias, so its storage hash changes from 0df0ef0989ec3dd95124dde6303fbe0572bbab08bebf00abff6a7955cadd786e to 24a0762cac2c89426d118c9a9a81876ebcf32eba11789722d7c907ba710dc60d. The tables do not change. Until you upgrade your app's copy of the auth migrations and sign each database, prisma deploy and prisma dev fail at the migration step.

In short: upgrade prisma to 8.0.0-rc.26 or later, run the ORM's type-alias script on your app, run prisma contract emit, then run prisma db sign against production, every stage and the local dev database. Sign the local database while it is still running, before your first prisma dev on 0.34.0, or start over with prisma dev --fresh. The full steps, including where to find each connection string, are in the auth module's README, section Upgrading to Composer 0.34.0.

After the upgrade, prisma migration status no longer shows the auth pack's earlier migrations as applied, although the database is up to date.

Piped commands print data lines

When stdout is a pipe or a file, prisma deploy, prisma dev stop, prisma dev url and prisma emulator list print tab-separated data lines on stdout and everything else on stderr. --json gives the full result.

$ prisma deploy module.ts | cut -f1,4
catalog.service	https://catalog.example.com
catalog.database

• deploy prints one line per deployed entity: node address, entity kind, entity id, URL. Alchemy's progress goes to stderr.
• dev stop prints one line per stopped node: address and kind.
• emulator list escapes its fields; its directory stays an absolute path.

A script that read JSON from a piped prisma deploy, prisma dev stop or prisma emulator list must pass --json. The rules and every command's fields are in Piped output.