Update prisma monorepo to v2.30.3 (minor) #263

renovate · 2021-07-19T15:35:27Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@prisma/client (source)	`2.16.1` -> `2.30.3`
prisma (source)	`2.16.1` -> `2.30.3`

Release Notes

prisma/prisma

`v2.30.3`

Compare Source

Today, we are issuing the 2.30.3 patch release.

Improvements

Prisma CLI

Adapt CLI update notifier for major upgrade #9061

Fixes

Prisma Studio

npx prisma studio throws spawn undefined\System32\WindowsPowerShell\v1.0\powershell ENOENT error on windows

`v2.30.2`

Today, we are issuing the 2.30.2 patch release.

Fixes

Prisma Client

A NOT within a NOT creates a SQL query with only a single NOT in 2.30.0

`v2.30.0`

Compare Source

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

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

New features & improvements

Full-Text Search for PostgreSQL is now in Preview 🚀

We're excited to announce that Prisma Client now has preview support for Full-Text Search on PostgreSQL.

You can give this a whirl in 2.30.0 by enabling the fullTextSearch preview flag:

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["fullTextSearch"]
}

model Post {
  id     Int    @&#8203;id @&#8203;default(autoincrement())
  title  String @&#8203;unique
  body   String
  status Status
}

enum Status {
  Draft
  Published
}

After you regenerate your client, you'll see a new search field on your String fields that you can query on. Here are a few examples:

// returns all posts that contain the words cat *or* dog.
const result = await prisma.post.findMany({
  where: {
    body: {
      search: 'cat | dog',
    },
  },
})

// All drafts that contain the words cat *and* dog.
const result = await prisma.posts.findMany({
  where: {
    status: "Draft",
    body: {
      search: 'cat & dog',
    },
  },
})

You can learn more about how the query format works in our documentation. We would love to know your feedback! If you have any comments or run into any problems we're available in this in this Github issue.

Validation errors for referential action cycles on Microsoft SQL Server ℹ

Microsoft SQL Server has validation rules for your schema migrations that reject schema changes that introduce referential action cycles.
These scenarios tend to show up often for developers using the referentialActions preview feature, which will become the default. The database error you get is not really helpful, so to provide a better experience, Prisma now checks for referential cycle actions when it validates your schema file and shows you the exact location of the cycle in your schema.

To learn more, check out the documentation.

`prisma introspect` is being deprecated in favor of `prisma db pull` 👋🏻

The prisma introspect command is an alias for prisma db pull so they are the same command. However, prisma db pull is more intuitive since it pulls the schema from the database into your local schema.prisma file. This naming also works as the counterpart of prisma db push.

Starting with this release, you will get a warning that encourages you to use prisma db pull instead of prisma introspect.

Prisma Adopts Semantic Versioning (SemVer)

As previously announced, we are adjusting our release policy to adhere more strictly to Semantic Versioning.

In the future, breaking changes in the stable development surface i.e. General Availability will only be rolled out with major version increments.

You can learn more about the change in the announcement blog post.

Fixes and improvements

Prisma Client

Prisma Migrate

Language tools (e.g. VS Code)

@prisma/engines npm package

Cannot find namespace 'debug' in 2.29.0

Credits

Huge thanks to @saintmalik for helping!

📺 Join us for another "What's new in Prisma" livestream

Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" livestream.

The stream takes place on Youtube on Thursday, August 26 at 5pm Berlin | 8am San Francisco.

`v2.29.1`

Compare Source

Today, we are issuing the 2.29.1 patch release.

Fixes

Prisma Client

`v2.29.0`

Compare Source

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

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

Major improvements & new features

Interactive Transactions are now in Preview

Today we’re introducing Interactive Transactions – one of our most debated feature requests.

Interactive Transactions are a double-edged sword. While they allow you to ignore a class of errors that could otherwise occur with concurrent database access, they impose constraints on performance and scalability.

While we believe there are better alternative approaches, we certainly want to ensure people who absolutely need them have the option available.

You can opt-in to Interactive Transactions by setting the interactiveTransactions preview feature in your Prisma Schema:

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["interactiveTransactions"]
}

Note that the interactive transactions API does not support controlling isolation levels or locking for now.

You can find out more about implementing use cases with transactions in the docs, and share your feedback.

Named Constraints are now in Preview

Named Constraints allow you to represent (when using introspection) and specify (when using Prisma Migrate) the names of constraints of the underlying database schema in your Prisma schema.

Before this release, you could only specify the underlying database constraint names for @@unique and @@index. This meant that you didn't have control over all constraint names in the database schema. In projects that adopted Prisma with introspection, some constraint names from the database were not represented in the Prisma schema. This could lead to the database schema across environments getting out of sync when one environment was introspected, and another was created with Prisma Migrate and had different constraint names.

Starting with this release, you can specify the underlying database constraint names for @id, @@id, @unique, and @relation constraints.

You can opt-in to Named Constraints by adding the namedConstraints preview feature to your Prisma Schema:

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["namedConstraints"]
}

After enabling the namedConstraints preview flag, you can specify the names of constraints in the database schema using the map attribute:

@id(map: "custom_primary_key_constraint_name")
@@id([field1, field2], map: "custom_compound_primary_key_name")
@unique(map: "custom_unique_constraint_name")
@@unique([field1, field2], map: "custom_compound_unique_constraint_name")
@@index([field1, field2], map: "custom_index_name")
@relation(fields: [fieldId], references: [id], map: "custom_foreign_key_name")

After specifying the map attribute, Prisma Migrate will use it when creating migrations.

When using prisma db pull with namedConstraints, these names will be automatically populated in your Prisma schema unless they match our default naming convention (which follows the Postgres convention). When handwriting a Prisma schema, these names are optional and will alternatively be filled with the default names by Prisma under the hood.

The `name` argument in `@@unique` and `@@id`

In addition to the map argument, the @@unique and the @@id attributes have the name argument (optional) that Prisma uses to generate the WhereUnique argument in the Prisma Client API.

Note: You can use both name and map together, e.g. @@unique([firstName, lastName], name: "NameOfWhereUniqueArg", map: "NameOfUniqueConstraintInDB")

For example, given the following model:

model User {
  firstName String
  lastName  String

  @&#8203;@&#8203;id([firstName, lastName])
}

The following Prisma Client query is valid:

const user = await prisma.user.findUnique({
  where: {
    // firstName_lastName is the default `name`
    firstName_lastName: {
      firstName: 'Ada',
      lastName: 'Lovelace',
    },
  },
})

By adding the name argument to the @@id attribute:

model User {
  firstName String
  lastName  String

-  @&#8203;@&#8203;id([firstName, lastName])
+  @&#8203;@&#8203;id([firstName, lastName], name: "fullname")
}

The following query is valid:

const user = await prisma.user.findUnique({
  where: {
    // fullname comes from the name argument
    fullname: {
      firstName: 'Ada',
      lastName: 'Lovelace',
    },
  },
})

Note: For the @@unique attribute this functionality was already available in previous releases. For @@id this is new.

You can learn more about namedConstraints in our documentation.

Please check our upgrade guide before enabling the preview flag and running migrate operations for the first time. It explains what to do if you either want to keep the existing names in your database or want to switch to the default names for a cleaner Prisma schema.

Prisma Adopts Semantic Versioning (SemVer)

As previously announced, we are adjusting our release policy to adhere more strictly to Semantic Versioning.

In the future, breaking changes in the stable development surface i.e. General Availability will only be rolled out with major version increments.

You can learn more about the change in the announcement blog post.

Fixes and improvements

Prisma Client

Prisma Migrate

Credits

Huge thanks to @benkenawell for helping!

📺 Join us for another "What's new in Prisma" livestream

Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" livestream.

The stream takes place on Youtube on Thursday, March 04 at 5pm Berlin | 8am San Francisco.

`v2.28.0`

Compare Source

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

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

MongoDB improvements 🚀

Thanks to your feedback, we fixed a handful of bugs reported on the MongoDB connector (Preview):

Concurrent findUnique queries leading to an error #8276
Filtering by relations wasn't working properly #7057
Filtering on an array of IDs #6998

Please keep reporting issues to our team and help to bring MongoDB support closer to GA!

Prisma Adopts Semantic Versioning (SemVer)

We are adjusting our release policy to adhere more strictly to Semantic Versioning.

In the future, breaking changes in the stable development surface i.e. General Availability will only be rolled out with major version increments.

You can learn more about the change in the announcement blog post.

Create new Prisma projects in under 3 minutes ⏳

The latest release of the Prisma Data Platform enables you to create new Prisma projects and provision a database in under 3 minutes.

The Prisma Data Platform already allows you to:

Explore data in the database using the data browser.
Add other users to it, such as your teammates or your clients.
Assign users one of four roles: Admin, Developer, Collaborator, Viewer.
View and edit your data collaboratively online.

The new onboarding flow makes it possible to get started with Prisma quickly for new Prisma projects! 🚀

When creating a new Prisma project, the Prisma Data Platform allows you to:

Choose a Prisma schema from a selection of our templates.
Create a free PostgreSQL database on Heroku.
Populate the database with seed data.

If you already have a Prisma project, you can continue to import it from GitHub and connect it to your database.

This whole process now takes less than 3 minutes to set up, so we’re looking forward to seeing how you will use this feature for your prototyping and production needs.

If you have any issues or questions, let us know by opening a GitHub issue.

Quick overview

If you have a Heroku account, we can create a free Postgres database for you:

Start your project with a schema from our templates:

Interested in Prisma’s upcoming Data Proxy for serverless backends? Get notified! 👀

Database connection management in serverless backends is challenging: taming the number of database connections, additional query latencies for setting up connections, etc.

At Prisma, we are working on a Prisma Data Proxy that makes integrating traditional relational and NoSQL databases in serverless Prisma-backed applications a breeze. If you are interested, you can sign up to get notified of our upcoming Early Access Program here:

https://pris.ly/prisma-data-proxy

Fixes and improvements

Prisma Client

Prisma Migrate

Using render.com database for migrate dev leads to error message ERROR: cannot drop view pg_buffercache because extension pg_buffercache requires it HINT: You can drop extension pg_buffercache instead.

Prisma Studio

Credits

Huge thanks to @ShubhankarKG, @hehex9 for helping!

📺 Join us for another "What's new in Prisma" livestream

Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" livestream.

The stream takes place on Youtube on Thursday, July 15 at 5pm Berlin | 8am San Francisco.

`v2.27.0`

Compare Source

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

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

Major improvements & new features

MongoDB is Now in Preview 🎉

We're thrilled to announce that Prisma now has Preview support for MongoDB. Here's how to get started:

Inside your schema.prisma file, you'll need to set the database provider to mongodb. You'll also need to add mongoDb to the previewFeatures property in the generator block:

// Set the database provider to "mongodb"
datasource db {
  provider = "mongodb"
  url      = env("DATABASE_URL")
}

// We want to generate a Prisma Client
// Since mongodb is a preview feature, we need to enable it.
generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["mongoDb"]
}

// Create our Post model which will be mapped to a collection in the database.
// All posts have a required `title`, `slug` and `body` fields.
// The id attributes tell Prisma it's a primary key and to generate 
// object ids by default when inserting posts.
model Post {
  id    String @&#8203;id @&#8203;default(dbgenerated()) @&#8203;map("_id") @&#8203;db.ObjectId
  slug  String @&#8203;unique
  title String
  body  String
}

Next, you'll need to add a database connection string to your .env file. We recommend using MongoDB Atlas to spin up a MongoDB database for free. Set the DATABASE_URL to the connection string you got from MongoDB Atlas, it should be similar to the following string:

DATABASE_URL="mongodb+srv://admin:<password>@&#8203;cluster0.quvqo.mongodb.net/myFirstDatabase?retryWrites=true&w=majority"

❗️ Don't forget to include the username and password you set while creating the database in the connection string, otherwise you won't be able to connect to it.

Then you can run npx prisma generate to generate a MongoDB-compatible Prisma Client. The Prisma Client API is the same for Mongo as it is for other supported relational databases (PostgreSQL, MySQL, SQLite and Microsoft SQL Server).

To test that everything works, you can run the following script:

import { PrismaClient } from "@&#8203;prisma/client"
const prisma = new PrismaClient()

async function main() {
  // Create the first post
  await prisma.post.create({
    data: {
      title: "Prisma <3 MongoDB",
      slug: "prisma-loves-mongodb",
      body: "This is my first post. Isn't MongoDB + Prisma awesome?!",
    },
  })
  // Log our posts showing nested structures
  console.dir(posts, { depth: Infinity })
}

main()
  .catch(console.error)
  .finally(() => prisma.$disconnect())

You should see a new post created and added to your database! You can use Prisma Studio to view the record you just added by running npx prisma studio.

This is just the tip of the iceberg. Learn more in our Getting Started Guide.

We would love to know your feedback! If you have any comments or run into any problems we're available in this issue. You can also browse existing issues that have the MongoDB label.

Prisma native support for M1 Macs 🚀

This one's for our Mac users. Prisma now runs natively on the new M1 chips. Best of all, there's nothing to configure, it just works. Enjoy the speed bump!

Fixes and improvements

Prisma Client

Prisma Migrate

📺 Join us for another "What's new in Prisma" livestream

Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" livestream.

The stream takes place on Youtube on Thursday, July 15 at 5pm Berlin | 8am San Francisco.

`v2.26.0`

Compare Source

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

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

Major improvements & new features

Referential Actions now enable cascading deletes and updates (Preview)

In this release we are introducing a new feature in Preview which enables fine-grained control over referential actions ON DELETE and ON UPDATE for the foreign keys supporting relations in Prisma models.

Current behavior

Until now, Prisma created a foreign key for each relation between Prisma models with the following defaults: ON DELETE CASCADE ON UPDATE CASCADE. In addition, when invoking the delete() or deleteAll() methods, Prisma Client performs runtime checks and will prevent the deletion of records on required relations if there are related objects referencing it, effectively preventing the cascade delete behavior. When using raw SQL queries for deletion, Prisma Client won't perform any checks, and deleting a referenced object will effectively cause the deletion of the referencing objects.

Example:

model User {
  id    String @&#8203;id
  posts Post[]
}

model Post {
  id       String @&#8203;id
  authorId String
  author   User   @&#8203;relation(fields: [authorId])
}

prisma.user.delete(...) and prisma.user.deleteAll() will fail if the user has posts.

Using raw SQL, e.g. using $queryRaw() to delete the user will trigger the deletion of its posts.

New behavior

⚠️ Turning on this feature could, when using delete() and deleteMany() operations, delete more data than before under certain circumstances. Make sure you read down below to understand why and anticipate these changes.

The feature can be enabled by setting the preview feature flag referentialActions in the generator block of Prisma Client in your Prisma schema file:

generator client {
  provider = "prisma-client-js"
  previewFeatures = ["referentialActions"]
}

With the feature enabled, the behavior is now the following:

It's possible to choose specific referential actions for the foreign keys in relations. Prisma Migrate, prisma db push, and introspection will set these in the database schema, e.g. @relation(... onDelete: SetNull) will set translate to ON DELETE SET NULL on the corresponding foreign key. See Syntax section below.
When the onDelete or onUpdate attributes in @relation are not present, default values are used:
- ON DELETE RESTRICT (NO ACTION on SQL Server) for required relations
- ON DELETE SET NULL for optional relations
- ON UPDATE CASCADE for all relations regardless if optional or required.
Prisma Migrate, prisma db push, and introspection will rely on the syntax and default values above to keep the referential actions between Prisma schema and database schema in sync.
Prisma Client no longer performs any checks before deleting records when invoking delete() or deleteAll() methods. Deleting referenced objects will succeed or not depending on the underlying foreign keys of relations, e.g. by default deletion will be prevented by the database because it's set to ON DELETE RESTRICT, but will succeed if set to ON DELETE CASCADE.
Upgrade path: If developers don't specify custom onDelete or onUpdate attributes in the Prisma schema, the next time the database is updated with Prisma Migrate or prisma db push, the database schema will be updated to use the default values on all foreign keys, ON DELETE RESTRICT ON UPDATE CASCADE (ON DELETE NO ACTION ON UPDATE CASCADE on SQL Server).
Please note that until then, if the database schema is managed using Prisma Migrate or prisma db push, the existing defaults are probably in place (ON DELETE CASCADE ON UPDATE CASCADE), and this could lead to deletion of records in conditions where a deletion was previously prevented by Prisma Client until the foreign key constraints are updated.

Syntax

The semantics of onDelete and onUpdate are almost exactly how SQL expresses ON UPDATE and ON DELETE. For the example below:

If the related author (User) of a Post is deleted (onDelete), delete all Post rows that are referencing the deleted User (Cascade).
If the id field of the related User is updated, also update authorId of all Posts that reference that User.

model User {
  id    String @&#8203;id
  posts Post[]
}

model Post {
  id       String @&#8203;id
  authorId String
  author   User   @&#8203;relation(fields: [authorId], onDelete: Cascade, onUpdate: Cascade)
}

Possible keywords for onDelete and onUpdate are: Cascade, Restrict (except SQL Server), NoAction, SetNull, SetDefault.

If you run into any questions or have any feedback, we're available in this issue.

Limitations

Certain combinations of referential actions and required/optional relations are incompatible. Example: Using SetNull on a required relation will lead to database errors when deleting referenced records because the non-nullable constraint would be violated.
Referential actions can not be specified on relations in implicit many-to-many relations. This limitation can be worked around by switching to explicit many-to-many relations and specifying the referential actions on the relations in the relations table.

`prisma init` now accepts a `--datasource-provider` argument

The prisma init command now accepts a --datasource-provider argument that lets you configure the default provider for the initially generated datasource block in your Prisma schema. The possible values for this argument are equivalent to the allowed values for the provider field on datasource blocks:

postgresql (default)
mysql
sqlite
sqlserver (Preview, needs the microsoftSqlServer preview feature flag)

Here's an example that shows how to configure the initial Prisma schema skeleton with a SQLite database:

npx prisma init --datasource-provider sqlite

Node-API Improvements

The Prisma Client currently communicates to Prisma's Query Engine over either HTTP or Unix domain sockets. After some experimentation, we realized we can improve this communication overhead by using Node-API, which provides direct memory access across processes.

We've been working the last couple of weeks to get ready to make Node-API the default way we communicate with the Query Engine. To prepare for this change, we fixed a bunch of bugs and we'd love for you to give it another try:

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["nApi"]
}

Right now we're still compiling benchmarks, but you should see a nice speed boost by opting into Node-API. You can reach us in this issue if you run into anything!

Fixes and improvements

Prisma Client

Prisma Migrate

Prisma

Credits

Huge thanks to @B2o5T for helping!

🌎 Prisma Day is happening today!

Prisma Day is a two-day event of talks and workshops by members of the Prisma community, on modern application development and databases. It's taking place June 29-30th and is entirely online.

June 29th: Workshops
June 30th: Talks

We look forward to seeing you there!

📺 Join us for another "What's new in Prisma" livestream

Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" livestream.

The stream takes place on Youtube on Thursday, July 01 at 5pm Berlin | 8am San Francisco.

`v2.25.0`

Compare Source

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

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

Major improvements & new features

Human-readable drift diagnostics for `prisma migrate dev`

Database schema drift occurs when your database schema is out of sync with your migration history, i.e. the database schema has drifted away from the source of truth.

With this release, we improve the way how the drift is printed to the console when detected in the prisma migrate dev command. While this is the only command that uses this notation in today's release, we plan to use it in other places where it would be useful for debugging in the future.

Here is an example of how the drift is presented with the new format:

[*] Changed the `Color` enum
  [+] Added variant `TRANSPARENT`
  [-] Removed variant `RED`

[*] Changed the `Cat` table
  [-] Removed column `color`
  [+] Added column `vaccinated`

[*] Changed the `Dog` table
  [-] Dropped the primary key on columns (id)
  [-] Removed column `name`
  [+] Added column `weight`
  [*] Altered column `isGoodDog` (arity changed from Nullable to Required, default changed from `None` to `Some(Value(Boolean(true)))`)
  [+] Added unique index on columns (weight)

Support for `.env` files in Prisma Client Go

You can now use a .env file with Prisma Client Go. This makes it easier to keep database credentials outside your Prisma schema and potentially work with multiple clients at the same time:

example/
├── .env
├── main.go
└── schema.prisma

Learn more about using the .env file in our documentation.

Breaking change

Dropping support for Node.js v10

Node.js v10 reached End of Life on April 30th 2021. Many of our dependencies have already dropped support for Node.js v10 so staying up-to-date requires us to drop Node.js v10, too.

We recommend upgrading to Node.js v14 or greater for long-term support. You can learn more about Node.js releases on this page.

Fixes and improvements

Prisma Client

Prisma Migrate

Prisma Studio

Credits

Huge thanks to @82600417, @SuryaElavazhagan, @psavan1655 for helping!

📺 Join us for another "What's new in Prisma" livestream

Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" livestream.

The stream takes place on Youtube on Thursday, June 17 at 5pm Berlin | 8am San Francisco.

🌎 Prisma Day is coming

Save the date for Prisma Day 2021 and join us for two days of talks and workshops by the most exciting members of the Prisma community.

June 29th: Workshops
June 30th: Talks

We look forward to seeing you there!

`v2.24.1`

Compare Source

Today, we are issuing the 2.24.1 patch release.

Fixes

Prisma Client

`v2.24.0`

Compare Source

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

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

Major improvements & new features

MongoDB gets `Json` and `Enum` Support

We just added Json and enum support to the MongoDB provider for Prisma Client. Here's an example with both:

datasource db {
  provider = "mongodb"
  url      = env("DATABASE_URL")
}

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["mongodb"]
}

model Log {
  id      String @&#8203;id @&#8203;default(dbgenerated()) @&#8203;map("_id") @&#8203;db.ObjectId
  message String
  level   Level  @&#8203;default(Info)
  meta    Json
}

enum Level {
  Info
  Warn
  Error
}

You can then use the generated client like this:

await prisma.log.create({
  data: {
    level: "info",
    message: "User signed in",
    meta: { user_id: 1 },
  },
})

As a reminder, the mongodb provider is still in Early Access. If you'd like to use MongoDB with Prisma, please fill out this 2-minute Typeform and we'll get you an invite to our Getting Started Guide and private Slack channel right away!

New features for the Prisma Data Platform

The Prisma Data Platform (PDP) helps developers collaborate better in projects that are using the open-source tools. One of its main features today is an online data browser.

View schema

You can now view your project's schema in order to better understand your application or collaborate with your colleagues. The only roles that can view it are: Admin and Developer

Expand for a screenshot of the new schema view

##### Delete & edit your project

You can now delete your project from your settings.

Expand for a screenshot of the new settings

You can also edit your Project's URL, so you can now correct any mistakes you might have made while creating your project.

Static IPs are now supported

If your database is behind a proxy and you need a static IP to allowlist in order to give access to it, you can now get in touch with us by creating an issue or sending an email at [email protected] and we'll enable it for you.

Please note that while this feature is freely available now, it will be offered as part of a paid plan in the future (towards the end of '21 or beginning of '22).

Fixes and improvements

Prisma Client

Prisma Migrate

Prisma Studio

Prisma Engines

Credits

Huge thanks to @Sytten for helping!

📺 Join us for another "What's new in Prisma" livestream

Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" livestream.

The stream takes place on Youtube on Thursday, June 3rd at 5pm Berlin | 8am San Francisco.

🌎 Prisma Day is coming

Save the date for Prisma Day 2021 and join us for two days of talks and workshops by the most exciting members of the Prisma community.

June 29th: Workshops
June 30th: Talks

We look forward to seeing you there!

[`v2.23.0`](https://togithub.com/prisma/pris

Configuration

📅 Schedule: "before 7am on Tuesday" in timezone Australia/Sydney.

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

changeset-bot · 2021-07-19T15:35:31Z

⚠️ No Changeset found

Latest commit: 949cdaa

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

renovate · 2021-09-30T03:59:28Z

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will now ignore this update (2.30.3). You will still receive a PR once a newer version is released, so if you wish to permanently ignore this dependency, please add it to the ignoreDeps array of your renovate config.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.

renovate bot force-pushed the renovate/prisma-monorepo branch from 857cff9 to 3377d93 Compare July 26, 2021 14:35

renovate bot force-pushed the renovate/prisma-monorepo branch from 3377d93 to 3da9e98 Compare August 2, 2021 14:38

renovate bot changed the title ~~Update prisma monorepo to v2.27.0 (minor)~~ Update prisma monorepo to v2.28.0 (minor) Aug 2, 2021

renovate bot force-pushed the renovate/prisma-monorepo branch from 3da9e98 to 95f2cd9 Compare August 16, 2021 14:18

renovate bot changed the title ~~Update prisma monorepo to v2.28.0 (minor)~~ Update prisma monorepo to v2.29.1 (minor) Aug 16, 2021

renovate bot force-pushed the renovate/prisma-monorepo branch from 95f2cd9 to f0b1993 Compare August 30, 2021 15:01

renovate bot changed the title ~~Update prisma monorepo to v2.29.1 (minor)~~ Update prisma monorepo (minor) Aug 30, 2021

renovate bot force-pushed the renovate/prisma-monorepo branch from f0b1993 to 84490a8 Compare August 30, 2021 16:03

renovate bot changed the title ~~Update prisma monorepo (minor)~~ Update prisma monorepo to v2.30.1 (minor) Aug 30, 2021

renovate bot force-pushed the renovate/prisma-monorepo branch from 84490a8 to f901a23 Compare August 30, 2021 17:01

renovate bot changed the title ~~Update prisma monorepo to v2.30.1 (minor)~~ Update prisma monorepo to v2.30.2 (minor) Aug 30, 2021

Update prisma monorepo to v2.30.3

949cdaa

renovate bot force-pushed the renovate/prisma-monorepo branch from f901a23 to 949cdaa Compare September 6, 2021 14:20

renovate bot changed the title ~~Update prisma monorepo to v2.30.2 (minor)~~ Update prisma monorepo to v2.30.3 (minor) Sep 6, 2021

bladey closed this Sep 30, 2021

renovate bot deleted the renovate/prisma-monorepo branch September 30, 2021 03:59

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update prisma monorepo to v2.30.3 (minor) #263

Update prisma monorepo to v2.30.3 (minor) #263

renovate bot commented Jul 19, 2021 •

edited

Loading

changeset-bot bot commented Jul 19, 2021 •

edited

Loading

renovate bot commented Sep 30, 2021

Update prisma monorepo to v2.30.3 (minor) #263

Update prisma monorepo to v2.30.3 (minor) #263

Conversation

renovate bot commented Jul 19, 2021 • edited Loading

Release Notes

Improvements

Prisma CLI

Fixes

Prisma Studio

Fixes

Prisma Client

New features & improvements

Full-Text Search for PostgreSQL is now in Preview 🚀

Validation errors for referential action cycles on Microsoft SQL Server ℹ

prisma introspect is being deprecated in favor of prisma db pull 👋🏻

Prisma Adopts Semantic Versioning (SemVer)

Fixes and improvements

Prisma Client

Prisma Migrate

Language tools (e.g. VS Code)

@​prisma/engines npm package

Credits

📺 Join us for another "What's new in Prisma" livestream

Fixes

Prisma Client

Major improvements & new features

Interactive Transactions are now in Preview

Named Constraints are now in Preview

The name argument in @@&#8203;unique and @@&#8203;id

Prisma Adopts Semantic Versioning (SemVer)

Fixes and improvements

Prisma Client

Prisma Migrate

Credits

📺 Join us for another "What's new in Prisma" livestream

MongoDB improvements 🚀

Prisma Adopts Semantic Versioning (SemVer)

Create new Prisma projects in under 3 minutes ⏳

Quick overview

Interested in Prisma’s upcoming Data Proxy for serverless backends? Get notified! 👀

Fixes and improvements

Prisma Client

Prisma Migrate

Prisma Studio

Credits

📺 Join us for another "What's new in Prisma" livestream

Major improvements & new features

MongoDB is Now in Preview 🎉

Prisma native support for M1 Macs 🚀

Fixes and improvements

Prisma Client

Prisma Migrate

📺 Join us for another "What's new in Prisma" livestream

Major improvements & new features

Referential Actions now enable cascading deletes and updates (Preview)

Current behavior

New behavior

Syntax

Limitations

prisma init now accepts a --datasource-provider argument

Node-API Improvements

Fixes and improvements

Prisma Client

Prisma Migrate

Prisma

Credits

🌎 Prisma Day is happening today!

📺 Join us for another "What's new in Prisma" livestream

Major improvements & new features

Human-readable drift diagnostics for prisma migrate dev

Support for .env files in Prisma Client Go

Breaking change

Dropping support for Node.js v10

Fixes and improvements

Prisma Client

Prisma Migrate

Prisma Studio

Credits

📺 Join us for another "What's new in Prisma" livestream

🌎 Prisma Day is coming

renovate bot commented Jul 19, 2021 •

edited

Loading

`prisma introspect` is being deprecated in favor of `prisma db pull` 👋🏻

@prisma/engines npm package

The `name` argument in `@@unique` and `@@id`

`prisma init` now accepts a `--datasource-provider` argument

Human-readable drift diagnostics for `prisma migrate dev`

Support for `.env` files in Prisma Client Go

MongoDB gets `Json` and `Enum` Support

[`v2.23.0`](https://togithub.com/prisma/pris

changeset-bot bot commented Jul 19, 2021 •

edited

Loading