what stackpulse tracks
Prisma releases from GitHub
StackPulse watches Prisma release notes and keeps the original source link close to every summary.
#stacks/
loading releases…
releases
breaking
security
deprecated
migrations
Next-generation Node.js and TypeScript ORM StackPulse turns upstream changelogs into scannable summaries with risky changes, deprecations, migration notes, and source links.
what stackpulse tracks
StackPulse watches Prisma release notes and keeps the original source link close to every summary.
upgrade risk
Risky changes are separated from normal feature notes so you can scan upgrade impact before changing production dependencies.
migration notes
Migration steps and recommended actions are only shown when the upstream release notes support them.
This release introduces significant changes including Postgres full-text search, prepared ORM reads, and schema file splitting. It also includes several breaking changes requiring careful migration.
Projects using Prisma ORM, especially those with custom configurations or relying on `dbgenerated` defaults, are affected by these changes.
Follow the provided upgrade recipes for detailed migration steps.
This release completes the rename from Prisma Next to Prisma 8, introduces named model and result types, and adds attribute completion to the language server. It includes breaking changes for environment variables and contract types.
Users relying on `PRISMA_NEXT_*` environment variables or needing to update contract types for to-one relations are affected.
Update environment variables and run `prisma contract emit` to ensure compatibility with the new contract format.
This release finalizes the transition from the old ORM config to the consolidated `prisma` CLI stack. Projects created before rc.2 require a config migration, while those scaffolded by rc.2+ `init` are unaffected. Two fixes address issues with `contract emit` and `init` scaffolding.
Projects created before rc.2 are affected and require a config migration.
Follow the [user recipe](https://github.com/prisma/prisma/tree/v8.0.0-rc.4/skills/prisma-next-upgrade/upgrades/8.0.0-rc.3-to-8.0.0-rc.4/) for the exact migration steps.
This release introduces significant changes, including retiring the `prisma-next` binary in favor of the unified `prisma` CLI, reverting default aggregates to plain JavaScript numbers, and making CHECK constraints a declared part of the contract. Almost every application will need to re-emit its contract and rename its config file.
Almost every application using Prisma will need to re-emit its contract and rename its config file.
Follow the provided upgrade recipes to migrate to the new version.
This release introduces significant changes to Prisma's package structure, error handling, and database facade dependencies. It also enhances relation-loading, SQL index naming, and migration contract storage.
This release affects all Prisma users due to significant package restructuring and error handling changes.
Follow the 0.16-to-0.17 upgrade recipe to migrate your application.