Prisma is updating its release policy to strictly follow Semantic Versioning (SemVer). Previously, Prisma used SemVer notation but sometimes introduced breaking changes in minor version increments. Going forward, breaking changes to the stable General Availability surface will only occur in major version increments. Preview and Early Access features can still have breaking changes in minor versions, but only when explicitly opted into. This change aims to make upgrades more predictable and compatible with dependency automation tools like Renovate and Dependabot. An upcoming release will introduce breaking changes and will be versioned as 3.x.x.

4m read timeFrom prisma.io
Post cover image
Table of contents
TL;DRPrisma releases adopt SemVerWhat this means for you?Why we are adopting SemVer semanticsOne of Prisma's upcoming releases will have breaking changes