Bump prisma from 3.12.0 to 3.13.0

[dependabot[bot]]

⚠️ Dependabot is rebasing this PR ⚠️

Rebasing might not happen immediately, so don't worry if this takes some time.

Note: if you make any changes to this PR yourself, they will take precedence over the rebase.

---

Bumps prisma from 3.12.0 to 3.13.0.

Release notes

Sourced from prisma's releases.

3.13.0

Today, we are excited to share the 3.13.0 stable release 🎉

🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

Major improvements

migrate diff and db execute are now Generally Available!

We released two new Preview CLI commands in version 3.9.0 – prisma migrate diff and prisma db execute – to enable our users to create and understand migrations and build their workflows using the commands.

We're proud to announce that the commands are now Generally Available and can now be used without the --preview-feature flag. 🎉

The prisma migrate diff command creates a diff of your database schema, Prisma schema file, or the migration history. All you have to do is feed the command with a schema from state and a schema to state to get an SQL script or human-readable diff.

In addition to prisma migrate diff, prisma db execute is used to execute SQL scripts against a database. You can directly execute prisma migrate diff's output using prisma db execute --stdin.

Both commands are non-interactive, so it's possible to build many new workflows such as forward and backward migrations with some automation tooling. Take a look at our documentation to learn some of the popular workflows these commands unlock:

• Fixing failed migrations
• Squashing migrations
• Generating down migrations
• Command reference for migrate diff and db execute

Let us know what tools, automation, and scripts you build using these commands.

SQL Server index clustering (Preview)

In version 3.5.0, we introduced the extendedIndexes Preview feature which we have constantly been adding new configuration options for indexes. In this release, we added support for enabling or disabling index/constraint clustering in SQL Server.

By default, indexes will be clustered by default. You can update this in your schema as follows to disable index clustering:

datasource db {
  provider = "sqlserver"
  url      = env("DATABASE_URL")
}
generator client {
provider        = "prisma-client-js"
previewFeatures = ["extendedIndexes"]
}
model Post {
id      Int     @​default(autoincrement()) @​id(clustered: false)
title   String
content String?
}

... (truncated)

Commits

• 613d71a chore(deps): update engines to 3.13.0-17.efdf9b1183dddfd4258cd181a72125755215...
• 2ebee34 chore(deps): update engines to 3.13.0-16.de7bded1dc27d9284a92dd683eec5b14e998...
• f80bf95 chore(deps): update engines to 3.13.0-15.43bd4848184c8c71b97db4b935c67945ff1a...
• bd8bd57 test(client): new test client setup (#12560)
• 2121276 chore(deps): update engines to 3.13.0-12.b5d46f43717ef745f00f8edb9cfec1d24772...
• 22f6f51 chore(migrate): remove sqlite check now performed engine-side (#12770)
• 2bbe4eb chore(cli): refactor checkpoint call and sanitize options (#12908)
• e1c9cf9 chore(deps): update engines to 3.13.0-11.07815b335736eb128666b4a5a86e94e19656...
• 97b14f0 chore(deps): update engines to 3.13.0-10.f738c2de40b0514b47c5cdbf75f8bb06929d...
• 3047855 chore: Rename prisma/e2e-tests to ecosystem-tests (#12480)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)