Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^3.212.0
->^3.226.0
^1.1.4
->^1.1.5
^1.1.5
->^1.1.6
^4.6.1
->^4.7.1
^1.2.0
->^1.2.2
^18.11.9
->^18.11.11
^2.4.1
->^2.4.2
^0.46.5
->^0.47.5
^0.25.2
->^0.25.6
^9.5.0
->^9.6.0
^1.0.16
->^1.0.22
^9.5.0
->^9.6.0
^9.5.0
->^9.6.0
^4.2.5
->^4.2.6
^1.3.12
->^1.4.0
^8.27.0
->^8.29.0
^3.7.2
->^3.7.3
^13.0.3
->^13.1.0
^0.6.1
->^0.7.2
^0.29.1
->^0.30.0
^1.19.2
->^1.19.4
^2.0.23
->^2.0.27
7.16.1
->7.18.1
>=7.16.1
->>=7.18.1
>=7.16.1
->>=7.18.1
^4.5.0
->^4.5.1
1.0.4
->1.2.2
1.0.4
->1.2.1
^4.9.3
->^4.9.4
^1.0.1
->^1.0.2
^1.0.1
->^1.0.2
^0.5.0
->^0.6.2
^0.46.5
->^0.47.5
^0.11.4
->^0.12.0
^0.11.4
->^0.12.0
^0.22.9
->^0.22.11
^0.22.9
->^0.22.11
^3.2.4
->^3.2.5
^0.7.8
->^0.7.9
^0.7.8
->^0.7.9
^0.21.2
->^0.22.0
^0.21.2
->^0.22.0
1.0.0-alpha.29
->1.0.0-alpha.30
1.0.0-alpha.29
->1.0.0-alpha.30
^0.25.2
->^0.25.6
^0.25.2
->^0.25.6
^1.0.9
->^1.0.11
^1.0.9
->^1.0.11
Release Notes
aws/aws-sdk-js-v3
v3.226.0
Compare Source
Note: Version bump only for package @aws-sdk/client-dynamodb
v3.225.0
Compare Source
Features
v3.224.0
Compare Source
Note: Version bump only for package @aws-sdk/client-dynamodb
v3.223.0
Compare Source
Bug Fixes
v3.222.0
Compare Source
Note: Version bump only for package @aws-sdk/client-dynamodb
v3.218.0
Compare Source
Note: Version bump only for package @aws-sdk/client-dynamodb
v3.216.0
Compare Source
Note: Version bump only for package @aws-sdk/client-dynamodb
v3.215.0
Compare Source
Note: Version bump only for package @aws-sdk/client-dynamodb
v3.214.0
Compare Source
Note: Version bump only for package @aws-sdk/client-dynamodb
v3.213.0
Compare Source
Note: Version bump only for package @aws-sdk/client-dynamodb
prisma/prisma
v4.7.1
Compare Source
Today, we are issuing the
4.7.1
patch release.Fixes in Prisma Client
clientExtensions
preview feature is usedconsole.log
outputs incorrect value whenresult
extensions are usedfindUniqueOrThrow
args
isundefined
v4.7.0
Compare Source
🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟
Highlights
Interactive transactions are now Generally Available
After an extensive Preview phase and lots of great feedback from our community, we're excited to announce that
interactiveTransactions
is now Generally Available and production ready! 🚀Interactive transactions allow you to pass an async function into a
$transaction
, and execute any code you like between the individual Prisma Client queries. Once the application reaches the end of the function, the transaction is committed to the database. If your application encounters an error as the transaction is being executed, the function will throw an exception and automatically rollback the transaction.Here are some of the feature highlights we've built:
4.2.0
4.6.0
Here's an example of an interactive transaction with a
Serializable
isolation level:You can now remove the
interactiveTransactions
Preview feature in your schema.Relation mode is Generally Available
This release marks
relationMode="prisma"
as stable for our users working with databases that don't rely on foreign keys to manage relations. 🎉Prisma’s relation mode started as a way to support PlanetScale which does not allow you to create foreign keys for better online migration support. We transformed that into our Referential Integrity Emulation in
3.1.1
when we realised that more users could benefit from it, and then integrated it as the default mode for MongoDB, which generally does not have foreign keys. Prisma needed to use emulation to give the same guarantees.We then realized the feature was more than just referential integrity and affected how relations work. To reflect this, we renamed the feature to relation mode and the
datasource
property torelationMode
in4.5.0
Index warnings for
relationMode = "prisma"
In this release, we've added a warning to our Prisma schema validation that informs you that the lack of foreign keys might result in slower performance — and that you should add an
@@​index
manually to your schema to counter that. This ensures your queries are equally fast in relation modeprisma
as they are with foreign keys.We also added a fix to our VS Code extension to help adding the suggested index with minimal effort:
If you are currently using the Preview feature flag to enable relation mode, you can now remove
referentialIntegrity
from thepreviewFeatures
in yourgenerator client
block in your Prisma schema.For more information, check out our updated relation mode documentation.
Prisma Client Extensions (Preview)
This release adds Preview support for Prisma Client Extensions. This feature introduces new capabilities to customize and extend Prisma Client. Today we are opening up four areas for extending Prisma Client:
model
: add custom methods or fields to your modelsclient
: add client-level methods to Prisma Clientresult
: add custom fields to your query resultsquery
: create custom Prisma Client queriesPrisma Client Extensions are self-contained scripts that can tweak the behavior of models, queries, results, and the client (Prisma Client) as a whole. You can associate a single or multiple extensions with an extended client to mix and match Prisma to your needs.
Prisma Client Extensions enables many use cases such as defining virtual fields, custom validation, and custom queries.
It also enables you to share your client extensions with others and import client extensions developed by others into your project.
For example, given the following schema:
You can create a computed field called
fullName
as follows:We're excited to see what you build with them! For more information, check out our docs and let us know what you think in this GitHub issue.
Multi-schema support for PostgreSQL (Preview)
We're pleased to announce that this release adds support for multi-schema support for PostgreSQL. The ability to query and manage multiple database schemas has been a long-standing feature request from our community.
This release adds support for the following:
If you already have a PostgreSQL database using multiple schemas, you can quickly get up and running using
prisma db pull
— on enabling the Preview feature and specifying the schemas in thedatasource
block similar to the example below.You can get started with defining multiple schemas in your Prisma schema as follows:
Then generate and apply the changes to your database with
prisma migrate dev
.We want to thank all our users for helping us design the feature since the early proposal on GitHub up to our current Preview release.
For further details, refer to our documentation and let us know what you think in this GitHub issue.
Request for feedback
Our Product team is currently running a survey for designing Database Views support for Prisma and we would appreciate your feedback.
Fixes and improvements
Prisma Client
RangeError: Invalid count value
duringnpx prisma generate
withDEBUG=*
on integration buildreferentialIntegrity
binary
engineerror
eventPrisma.TransactionClient
todefault-index.d.ts
findMany
errors withPANIC: index out of bounds: the len is 0 but the index is 0
upsert()
with nested selection errors withcalled
Option::unwrap()on a
Nonevalue
in 4.6.0findUnique
concurrently with different key order causes one of them to return nullfindUniqueOrThrow
via middlewareprisma
/ Reproduction test for prisma#16390Prisma
referentialIntegrity
(renamed torelationMode
)db pull
withmultiSchema
error on schema with 2 models with the same table name but in a different schemarelationMode
: make feature GASetDefault
validation error with warnings whenprovider = "mysql"
andrelationMode = "foreignKeys" | default
relationMode
validation warning messagesprisma validate
&prisma format
Prisma Migrate
prisma migrate dev
Language tools (e.g. VS Code)
@@​ignore
d and fields that are@ignore
dreferentialIntegrity = "prisma"
extensions
whenpostgresqlExtensions
preview feature is setrelationMode
GA - remove preview feature conditionrelationMode="prisma"
, for@relation
: add a warning if there is no index on the field(s)relationMode
: missing foreign keys' indexesPrisma Engines
Credits
Huge thanks to @cmd-johnson, @jsoref, @miguelgargallo for helping!
Prisma Data Platform
We're working on the Prisma Data Platform — a collaborative environment for connecting apps to databases. It includes the following:
Try it out. Let us know what you think!
📺 Join us for another "What's new in Prisma" live stream
Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" live stream.
The stream takes place on YouTube on Thursday, December 1 at 5 pm Berlin | 8 am San Francisco.
tauri-apps/tauri
v1.2.2
: tauri v1.2.2Compare Source
Updating crates.io index
Cargo Audit
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.