railway-app[bot]
commented
10 months ago This PR was not deployed automatically as @renovate[bot] does not have access to the Railway project.
In order to get automatic PR deploys, please add @renovate[bot] to the project inside the project settings page.
This PR contains the following updates:
5.7.1->5.9.0Release Notes
prisma/prisma (@prisma/internals)
### [`v5.9.0`](https://togithub.com/prisma/prisma/releases/tag/5.9.0) [Compare Source](https://togithub.com/prisma/prisma/compare/5.8.1...5.9.0) Today, we are excited to share the `5.9.0` stable release 🎉 🌟 **Help us spread the word about Prisma by starring the repo ☝️ or [posting on X](https://twitter.com/intent/tweet?text=Check) about the release.** This release brings a number of small improvements as we continue our work on larger features which you will hear more about in the coming weeks: - Improve the performance of relation queries by introducing JOINs (see [last release](https://togithub.com/prisma/prisma/releases/tag/5.8.0)). - Support deployment to edge functions (already available in Early Access, you can apply for trying it out by taking our [survey](https://pris.ly/survey/edge-functions-release-notes-5-9-0)). ##### Highlights ##### Optimized result sets for more efficient queries We continue our efforts of the performance of Prisma Client queries. In [`5.1.0`](https://togithub.com/prisma/prisma/releases/tag/5.1.0), we introduced the `RETURNING` keyword for several queries on PostrgeSQL and CockroachDB. We now expanded the use of `RETURNING` to SQLite and a broader range of queries for existing databases (e.g. `delete` on PostgreSQL and MongoDB). You can learn more about the optimizations of the result sets in these PRs: - [feat(qe): avoid extra select on delete queries](https://togithub.com/prisma/prisma-engines/pull/4595) - [feat(qe): enable queries with returning for sqlite](https://togithub.com/prisma/prisma-engines/pull/46) ##### SQL Server: Return proper error for unreachable database When trying migrate/introspect a SQL server instance that’s unreachable, Prisma ORM now returns the correct `P1001` error instead of failing without an error. Learn more in this PR: [SQL Server: Migrate/Introspection engine doesn't return P1001 error for unreachable url](https://togithub.com/prisma/prisma/issues/11407). ##### Fixes and improvements ##### Prisma Client - [Skip unnecessary `select` queries on create/update/delete](https://togithub.com/prisma/prisma/issues/8069) - [.prisma/client: Name can't start with a dot](https://togithub.com/prisma/prisma/issues/17685) - [Nested json is transformed to string when used “$type” key in object](https://togithub.com/prisma/prisma/issues/21454) - [Parallel execution with Promise.all causes P2024 error in version 5.8.0 due to connection limit](https://togithub.com/prisma/prisma/issues/22610) ##### Prisma Migrate - [SQL Server: Migrate/Introspection engine doesn't return P1001 error for unreachable url](https://togithub.com/prisma/prisma/issues/11407) - [Prisma errors fetching table 'CHECK_CONSTRAINTS' (which only exists in MySQL 8.0.16+) in MySQL 8.0.14](https://togithub.com/prisma/prisma/issues/19775) - [`ERROR: column "..." being dropped, try again later` when applying migrations with CRDB 23.1](https://togithub.com/prisma/prisma/issues/20851) ##### Language tools (e.g. VS Code) - [Extension wrongfully suggests Json as a valid type completion on Sqlite](https://togithub.com/prisma/language-tools/issues/1638) ##### Company news ##### Test edge functions support in Early Access Today, the only way how to use Prisma ORM in edge functions (e.g. Cloudflare Workers or Vercel Edge Functions) is by using [Prisma Accelerate](https://www.prisma.io/data-platform/accelerate). However, we are actively working on making Prisma ORM compatible with edge functions natively as well. If you want to become an early tester, you can apply for the private Early Accessing program by taking this [survey](https://pris.ly/survey/edge-functions-release-notes-5-9-0). ##### We Transitioned Prisma Accelerate to IPv6 Without Anyone Noticing Last year, AWS announced the decision to begin charging for IPv4 addresses beginning in February 2024. This move had a major impact on Prisma Accelerate, prompting us to go all-in on IPv6. [Learn more in this technical deep dive](https://www.prisma.io/blog/accelerate-ipv6-first) into how we approached our IPv6 migration, lessons learned, and the outcome for users of Prisma Accelerate. ##### Credits Huge thanks to [@laplab](https://togithub.com/laplab), [@Druue](https://togithub.com/Druue), [@anuraaga](https://togithub.com/anuraaga), [@onichandame](https://togithub.com/onichandame), [@LucianBuzzo](https://togithub.com/LucianBuzzo), [@RobertCraigie](https://togithub.com/RobertCraigie), [@almeidx](https://togithub.com/almeidx), [@victorgdb](https://togithub.com/victorgdb), [@tinola](https://togithub.com/tinola), [@sampolahtinen](https://togithub.com/sampolahtinen), [@AikoRamalho](https://togithub.com/AikoRamalho), [@petradonka](https://togithub.com/petradonka) for helping! ### [`v5.8.1`](https://togithub.com/prisma/prisma/releases/tag/5.8.1) [Compare Source](https://togithub.com/prisma/prisma/compare/5.8.0...5.8.1) Today, we are issuing the `5.8.1` patch release. ##### Fix in Prisma Client - [Parallel execution with Promise.all causes P2024 error in version 5.8.0 due to connection limit](https://togithub.com/prisma/prisma/issues/22610). ### [`v5.8.0`](https://togithub.com/prisma/prisma/releases/tag/5.8.0) [Compare Source](https://togithub.com/prisma/prisma/compare/5.7.1...5.8.0) 🌟 **Help us spread the word about Prisma by starring the repo or [posting on X](https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20@prisma%20release%20v5.8.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/5.8.0) about the release.** 🌟 ### Highlights Happy New Year from your friends at Prisma! 🎊 In the last 4 weeks, we resolved some bugs on the ORM and made some progress on some exciting features that we’re not yet ready to announce. Stay tuned for the upcoming releases, in which we’ll be announcing new features. 😉 #### `relationJoins` improvements: Relation loading strategy per query (Preview) In version [5.7.0](https://togithub.com/prisma/prisma/releases/tag/5.7.0), we released `relationJoins` into Preview. The `relationJoins` feature enables support for `JOIN`s for relation queries. This release adds support for the ability to specify the strategy used to fetch relational data per query when the Preview feature is enabled. This will enable you to choose the most efficient strategy for fetching relation data depending on your use case. You can now load relation data using either of the following strategies: - `join` — uses `JOIN`s to fetch relation data - `query` — uses separate queries to fetch relation data When the `relationJoins` Preview feature is enabled, by default, the relation fetching strategy used is `join`. You can override the default behavior by using the `relationLoadStrategy` query option. To get started, enable the Preview feature: ```tsx // schema.prisma generator client { provider = "prisma-client-js" previewFeatures = ["relationJoins"] } ``` … and specify the relation loading strategy for your query as follows: ```tsx await prisma.user.findMany({ relationLoadStrategy: 'query', include: { posts: true, }, }) ``` Try it out and [share your feedback](https://togithub.com/prisma/prisma/discussions/22288) and create a [bug report](https://togithub.com/prisma/prisma/issues/new?assignees=\&labels=kind/bug\&projects=\&template=bug_report.yml) if you encounter any issues. #### Survey: Edge functions support We’re working on bringing Edge function support to Prisma ORM and we would appreciate your input by [submitting a response to our survey](https://pris.ly/survey/edge-functions-release-notes). By filling out the survey, you will be considered for our Early Access cohort as soon as we have something for you to try out. #### Fixes and improvements ##### Prisma Client - [Log output of Node-API library engine is different](https://togithub.com/prisma/prisma/issues/9039) - [`target` and `timestamp` are undefined in `info` events in Data Proxy client](https://togithub.com/prisma/prisma/issues/18479) - [Wrong types of `timestamp` and `duration` in query events with Data Proxy](https://togithub.com/prisma/prisma/issues/18482) - [Using `citext` fields with neon database driver causes conversion error](https://togithub.com/prisma/prisma/issues/21807) - [Add FreeBSD 14 as a new platform](https://togithub.com/prisma/prisma/issues/22228) - [PostgresError { code: "54023", message: "cannot pass more than 100 arguments to a function", severity: "ERROR", detail: None, column: None, hint: None }](https://togithub.com/prisma/prisma/issues/22298) - [Int\[\] return as null](https://togithub.com/prisma/prisma/issues/22303) ##### Prisma Migrate - [Prisma Migrate errors with `Environment is non-interactive` when `VERCEL` env var is defined](https://togithub.com/prisma/prisma/issues/22380) ##### Language tools (e.g. VS Code) - [Add quickfix for `Error validating field 'id' in model 'Post': MongoDB '@default(auto())' fields must have 'ObjectId' native type.`](https://togithub.com/prisma/language-tools/issues/1548) - [Append mention of update to "preview feature not known" error message](https://togithub.com/prisma/language-tools/issues/1612) #### Credits Huge thanks to [@anuraaga](https://togithub.com/anuraaga), [@onichandame](https://togithub.com/onichandame), [@LucianBuzzo](https://togithub.com/LucianBuzzo), [@RobertCraigie](https://togithub.com/RobertCraigie), [@fqazi](https://togithub.com/fqazi), [@KhooHaoYit](https://togithub.com/KhooHaoYit), [@alencardc](https://togithub.com/alencardc), [@Oreilles](https://togithub.com/Oreilles), [@tinola](https://togithub.com/tinola), [@AikoRamalho](https://togithub.com/AikoRamalho), [@luxaritas](https://togithub.com/luxaritas) for helping! ### Company news #### 🎉 A billion queries and counting: Prisma Accelerate [Prisma Accelerate](https://pris.ly/accelerate-home-orm-release-1), our global database cache has served over 1 billion queries since its General Availability launch. We’d like to give a shoutout to our team and everyone who’s been with us on this journey. Stay tuned for some exciting products and features in the pipeline for 2024! #### 🔮 Prisma ORM Ecosystem Are you building a cool tool, extension, generator, CLI tool or anything else, for Prisma ORM? [Let us know](https://prisma-data.typeform.com/to/DYEjFIVx). We would like to learn about it and feature it on our [Ecosystem page](https://www.prisma.io/ecosystem). #### 💼 We’re hiring If you're interested in joining our growing team to help empower developers to build data-intensive applications, Prisma is the place for you. Check out our [Careers page](https://prisma.io/careers) for open positions.Configuration
📅 Schedule: Branch creation - "every weekend" in timezone Australia/Melbourne, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.