chore(deps): bump the prisma group in /web with 3 updates

[dependabot]

Bumps the prisma group in /web with 3 updates: @prisma/adapter-neon, @prisma/client and prisma.

Updates @prisma/adapter-neon from 5.10.2 to 5.11.0

Release notes

Sourced from @​prisma/adapter-neon's releases.

5.11.0

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

🌟 Help us spread the word about Prisma by starring the repo ☝️ or posting on X about the release.

Highlights

Edge function support for Cloudflare and Vercel (Preview)

We’re thrilled to announce that support for edge function deployments with Prisma ORM is now in Preview 🥳 As of this release, you can deploy your apps that are using Prisma ORM to:

• Vercel Edge Functions and Vercel Edge Middleware
• Cloudflare Workers and Cloudflare Pages

In order to deploy to an edge function, you’ll need to use a compatible database driver (along with its Prisma driver adapter):

• Neon Serverless Driver (for PostgreSQL databases hosted via Neon)
• PlanetScale Serverless Driver (for MySQL databases hosted via PlanetScale)
• pg driver (for traditional PostgreSQL databases)
• @libsql/client driver (for SQLite databases hosted via Turso)

Check out our documentation to learn how you can deploy an edge function using any combination of supported edge function provider and database.

You can also read more about it in the announcement blog post!

Performance improvements in nested create operations

With Prisma ORM, you can create multiple new records in nested queries, for example:

const user = await prisma.user.update({
  where: { id: 9 },
  data: {
    name: 'Elliott',
    posts: {
      create: {
        data: [{ title: 'My first post' }, { title: 'My second post' }],
      },
    },
  },
})

In previous versions, Prisma ORM would translate this into multiple SQL INSERT queries, each requiring its own roundtrip to the database. As of this release, these nested create queries are optimized and the INSERT queries are sent to the database in bulk in a single roundtrip. These optimizations apply to one-to-many as well as many-to-many relations.

With this change, using the nested create option to create multiple records effectively becomes equivalent to using a nested createMany operation (except that createMany only works with one-to-many relations, whereas create works both with one-to-many and many-to-many).

Note: Only the deepest nested operation is optimized. If a user specified create (1) -> create (2) -> create (3) in their query, only create (3) will be optimized.

Fixes and improvements

... (truncated)

Commits

• 7563f2b chore(deps): update devdependencies patch (non-major) (#23375)
• 5246dd9 chore(deps): update devdependencies patch (non-major) (#23216)
• 4be64fd chore(deps): update dependency @​neondatabase/serverless to v0.9.0 (#23305)
• See full diff in compare view

Updates @prisma/client from 5.10.2 to 5.11.0

Release notes

Sourced from @​prisma/client's releases.

5.11.0

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

🌟 Help us spread the word about Prisma by starring the repo ☝️ or posting on X about the release.

Highlights

Edge function support for Cloudflare and Vercel (Preview)

We’re thrilled to announce that support for edge function deployments with Prisma ORM is now in Preview 🥳 As of this release, you can deploy your apps that are using Prisma ORM to:

• Vercel Edge Functions and Vercel Edge Middleware
• Cloudflare Workers and Cloudflare Pages

In order to deploy to an edge function, you’ll need to use a compatible database driver (along with its Prisma driver adapter):

• Neon Serverless Driver (for PostgreSQL databases hosted via Neon)
• PlanetScale Serverless Driver (for MySQL databases hosted via PlanetScale)
• pg driver (for traditional PostgreSQL databases)
• @libsql/client driver (for SQLite databases hosted via Turso)

Check out our documentation to learn how you can deploy an edge function using any combination of supported edge function provider and database.

You can also read more about it in the announcement blog post!

Performance improvements in nested create operations

With Prisma ORM, you can create multiple new records in nested queries, for example:

const user = await prisma.user.update({
  where: { id: 9 },
  data: {
    name: 'Elliott',
    posts: {
      create: {
        data: [{ title: 'My first post' }, { title: 'My second post' }],
      },
    },
  },
})

In previous versions, Prisma ORM would translate this into multiple SQL INSERT queries, each requiring its own roundtrip to the database. As of this release, these nested create queries are optimized and the INSERT queries are sent to the database in bulk in a single roundtrip. These optimizations apply to one-to-many as well as many-to-many relations.

With this change, using the nested create option to create multiple records effectively becomes equivalent to using a nested createMany operation (except that createMany only works with one-to-many relations, whereas create works both with one-to-many and many-to-many).

Note: Only the deepest nested operation is optimized. If a user specified create (1) -> create (2) -> create (3) in their query, only create (3) will be optimized.

Fixes and improvements

... (truncated)

Commits

• 3b45747 fix(client): fix runtime.prettyName (#23446)
• 894eef9 fix(client): runtimeDescription is not defined #23153 (#23164)
• a211ad7 chore(deps): update engines to 5.11.0-15.efd2449663b3d73d637ea1fd226bafbcf45b...
• 69abf11 chore(deps): update dependency @​types/node to v16.18.86 (#23374)
• 009563e chore(deps): update engines to 5.11.0-9.3d9a0d64e7107d8985df64fce153a82e7821a...
• ff59f63 chore(deps): update dependency @​inquirer/prompts to v4.2.1 (#23414)
• ff2d725 chore(deps): update dependency wrangler to v3.32.0 (#23404)
• 9b90143 fix(client): engine loading on vercel & improved custom output dx (#22958)
• 63c4535 chore(deps): update engines to 5.11.0-7.ea1d441684437cb0347ae41a974507fb424a3...
• 4aee142 chore(deps): update engines to 5.11.0-6.6795ad985c527cdaf71c052574c604901054b...
• Additional commits viewable in compare view

Updates prisma from 5.10.2 to 5.11.0

Release notes

Sourced from prisma's releases.

5.11.0

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

🌟 Help us spread the word about Prisma by starring the repo ☝️ or posting on X about the release.

Highlights

Edge function support for Cloudflare and Vercel (Preview)

We’re thrilled to announce that support for edge function deployments with Prisma ORM is now in Preview 🥳 As of this release, you can deploy your apps that are using Prisma ORM to:

• Vercel Edge Functions and Vercel Edge Middleware
• Cloudflare Workers and Cloudflare Pages

In order to deploy to an edge function, you’ll need to use a compatible database driver (along with its Prisma driver adapter):

• Neon Serverless Driver (for PostgreSQL databases hosted via Neon)
• PlanetScale Serverless Driver (for MySQL databases hosted via PlanetScale)
• pg driver (for traditional PostgreSQL databases)
• @libsql/client driver (for SQLite databases hosted via Turso)

Check out our documentation to learn how you can deploy an edge function using any combination of supported edge function provider and database.

You can also read more about it in the announcement blog post!

Performance improvements in nested create operations

With Prisma ORM, you can create multiple new records in nested queries, for example:

const user = await prisma.user.update({
  where: { id: 9 },
  data: {
    name: 'Elliott',
    posts: {
      create: {
        data: [{ title: 'My first post' }, { title: 'My second post' }],
      },
    },
  },
})

In previous versions, Prisma ORM would translate this into multiple SQL INSERT queries, each requiring its own roundtrip to the database. As of this release, these nested create queries are optimized and the INSERT queries are sent to the database in bulk in a single roundtrip. These optimizations apply to one-to-many as well as many-to-many relations.

With this change, using the nested create option to create multiple records effectively becomes equivalent to using a nested createMany operation (except that createMany only works with one-to-many relations, whereas create works both with one-to-many and many-to-many).

Note: Only the deepest nested operation is optimized. If a user specified create (1) -> create (2) -> create (3) in their query, only create (3) will be optimized.

Fixes and improvements

... (truncated)

Commits

• 9b90143 fix(client): engine loading on vercel & improved custom output dx (#22958)
• 7563f2b chore(deps): update devdependencies patch (non-major) (#23375)
• 4cd66c6 chore(deps): update definitelytyped (#23304)
• 5246dd9 chore(deps): update devdependencies patch (non-major) (#23216)
• 5e2838a chore(deps): update dependency esbuild to v0.20.1 (#23214)
• a4ca09f fix(cli): studio when used with non-ascii chars (#23229)
• See full diff 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
stats	✅ Ready (Inspect)	Visit Preview	Mar 13, 2024 0:23am

[olros]

@dependabot squash and merge