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.
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 createManyonly 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.
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.
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 createManyonly 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.
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 ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore 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 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 ` 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 ` will remove all of the ignore conditions of the specified dependency
- `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions
Bumps the minor group with 8 updates:
5.10.2
5.11.0
1.71.1
1.72.0
20.11.25
20.11.28
18.2.64
18.2.67
18.2.21
18.2.22
7.2.0
7.3.0
7.2.0
7.3.0
5.10.2
5.11.0
Updates
@prisma/client
from 5.10.2 to 5.11.0Release notes
Sourced from
@prisma/client
's releases.... (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...Updates
sass
from 1.71.1 to 1.72.0Release notes
Sourced from sass's releases.
Changelog
Sourced from sass's changelog.
Commits
ce16b35
Cut a release (#2194)9af6bbf
Properly handlepkg:
imports with args (#2193)0330491
Update to node 20 (#2192)48e2d0c
Preserve underscores inVariableExpression.toString()
(#2185)6e2d637
Allow adjacent forward slashes in plain CSS expressions (#2190)fa4d909
Bump softprops/action-gh-release from 1 to 2 (#2191)fd67fe6
[Hotfix Node Package Importer]- Handle subpath without extensions (#2184)Updates
@types/node
from 20.11.25 to 20.11.28Commits
Updates
@types/react
from 18.2.64 to 18.2.67Commits
Updates
@types/react-dom
from 18.2.21 to 18.2.22Commits
Updates
@typescript-eslint/eslint-plugin
from 7.2.0 to 7.3.0Release notes
Sourced from
@typescript-eslint/eslint-plugin
's releases.Changelog
Sourced from
@typescript-eslint/eslint-plugin
's changelog.... (truncated)
Commits
4cf8ec7
chore(release): publish 7.3.0d2995df
fix(eslint-plugin): [no-unnecessary-type-assertion] fix false negative for co...2869c68
feat(eslint-plugin): [prefer-reduce-type-parameter] supports tuple, union, in...d830364
test(eslint-plugin): [no-unnecessary-type-assertion] add tests with noUncheck...04e32d6
fix(eslint-plugin): [class-literal-property-style] ignore property assigned i...612875b
fix(eslint-plugin): [explicit-function-return-type, explicit-module-boundary-...da006b1
fix(eslint-plugin): [ban-ts-comment] more accurate handling of multiline comm...71bfb7c
chore: fix ast-spec type import snapshot errors (#8699)fb18de9
fix(eslint-plugin): [no-unused-expressions] false negatives when using assert...f7323be
fix(eslint-plugin): [no-unnecessary-qualifier] handle merge namespace with en...Updates
@typescript-eslint/parser
from 7.2.0 to 7.3.0Release notes
Sourced from
@typescript-eslint/parser
's releases.Changelog
Sourced from
@typescript-eslint/parser
's changelog.Commits
4cf8ec7
chore(release): publish 7.3.0883f220
fix: correctengines.node
constraints inpackage.json
(#8671)Updates
prisma
from 5.10.2 to 5.11.0Release notes
Sourced from prisma's releases.
... (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)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