Bump prisma from 3.13.0 to 3.14.0

[dependabot]

Bumps prisma from 3.13.0 to 3.14.0.

Release notes

Sourced from prisma's releases.

3.14.0

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

Major improvements

CockroachDB connector is now Generally Available!

We are proud to announce the CockroachDB connector is now stable and Generally Available. The connector was built in joined efforts with the team at Cockroach Labs and comes with full Prisma Client and Prisma Migrate support.

If you're upgrading from Prisma version 3.9.0+ or the PostgreSQL connector, you can now run npx prisma db pull and review the changes to your schema. To learn more about CockroachDB-specific native types we support, refer to our docs.

To learn more about the connector and how it differs from PostgreSQL, head to our documentation.

PostgreSQL GIN, GiST, SP-GiST, and BRIN indexes support (Preview)

We introduced the extendedIndexes Preview feature in version 3.5.0, and we have been adding new configuration options for indexes. We've expanded index type support with the GIN, GiST, SP-GiST, and BRIN indexes in this release.

To make use of an index type, you can update your Prisma schema by providing the type argument to the @@index attribute:

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}
generator client {
provider        = "prisma-client-js"
previewFeatures = ["extendedIndexes"]
}
model Post {
id      Int     @​id
title   String
content String?
tags    Json?
@@​index([tags], type: Gin)
}

The following SQL will be generated in your migration when you run prisma migrate dev:

CREATE TABLE "Post" (
    "id" INTEGER NOT NULL,
    "title" TEXT NOT NULL,
    "content" TEXT,
    "tags" JSONB,
    CONSTRAINT "Post_pkey" PRIMARY KEY ("id")
);
CREATE INDEX "Post_tags_idx" ON "Post" USING GIN ("tags");
</tr></table>

... (truncated)

Commits

• c896178 chore(deps): update engines to 3.14.0-36.2b0c12756921c891fec4f68d9444e18c7d5d...
• 7c32ecc chore(deps): update engines to 3.14.0-35.b139d939b80290fb7fb7a0455a577fcf02fa...
• 197f919 fix(client): Fix package path in generate output (#13031)
• 9bc80fb chore(deps): update engines to 3.14.0-34.5cf26752c9aac4cf41ddca31b999a4a4906f...
• 8b663d2 chore(deps): update engines to 3.14.0-33.656da0566481bafc47a8a1f135ab368779db...
• f67fe45 chore(deps): update jest
• 4ae6ae9 chore(deps): update engines to 3.14.0-32.13d12f1fc9655c2d6bbd8f772677f0dc1e66...
• 9b3eb5b chore(deps): update engines to 3.14.0-31.bdec961782f52c38a7daf86dc155e89e6405...
• b856420 chore(deps): update engines to 3.14.0-30.17e2b313119d2b13299393860d690564a3ec...
• aff1b11 chore(deps): update engines to 3.14.0-28.7065cb28b6b34148da7ce0e72533104aab97...
• 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)