Version 6.6.0 introduces a breaking change despite being tagged as a minor version

[SmashingQuasar]

Bug description

Hello,

We just upgraded to version 6.6.0 and noticed that all of our builds and development environments fell apart.
This is due to the change (that is actually flagged as a breaking change in the patch note of version 6.6.0) regarding the preview feature for prisma schema folders.

While it is fine to introduce breaking change, it would be preferable to follow the SemVer standard. This is especially true in JavaScript environments where most of the time, your package manager will upgrade to the next minor version without explicit approval.

As per SemVer, all breaking changes must trigger a major version.

It may seem like a small problem but this can have dire cascading effects on production environments, which is why there is a standard to prevent this kind of problem. Since Prisma is backed by a company with complete development cycles, it would be much appreciated to have a better tracking of breaking changes in regard to SemVer.

I used the bug flag here as this creates major disruption in existing pipelines and builds. It could recategorised differently but I don't feel like it is a feature request.

Severity

⚠️ Major: Breaks core functionality (e.g., migrations fail)

Reproduction

Setting your version to ^6.5.0 in your package.json and running pnpm install or yarn install will trigger the automatic installation of version 6.6.0 which will break existing schema structure.

Note that ^6.5.0 is the default syntax used by package managers when doing pnpm install or yarn install.

Expected vs. Actual Behavior

Version 6.6.0 should be tagged version 7.0.0 regardless of commercial concerns as this is a technical library for technical purposes.

Frequency

Consistently reproducible

Does this occur in development or production?

Both development and production

Is this a regression?

N/A

Workaround

N/A

Prisma Schema & Queries

The following prisma folder structure will break between version 6.5.0 and 6.6.0:

prisma/
├── migrations/
│   └── any-migration.sql
└── schema/
    └── schema.prisma

Prisma Config

// Add your `prisma.config.ts`

Logs & Debug Info

// Debug logs here

Environment & Setup

• OS: Debian 12
• Database: PostgreSQL
• Node.js version: 22.x

Prisma Version

6.6.0