Today we are excited to share the 2.7.0 stable release.

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

Major improvements

Prisma Studio is stable 🎉

We are more than excited to share that Prisma Studio has moved out of its experimental state and is promoted to stable with today's release! Prisma Studio is the perfect companion for developers who work with databases in their daily workflows, to quickly get an overview of the state of their database as well as to view and modify the data in it. An announcement blog post will be coming soon!

To use Prisma Studio in your Prisma project, you can now run the prisma studio command without the previously required --experimental flag:

npx prisma studio

Join the #prisma-studio channel in the Prisma Slack and let us know how you like Prisma Studio! 🙌

Configure Prisma schema location via package.json for more flexibility

Previously, your schema.prisma file needed to be available at a specific location when running Prisma CLI commands or provided via the --schema option when invoking a Prisma CLI command.

With this release, you can configure the location of your Prisma schema via a prisma property in your package.json:

{
  "prisma": {
    "schema": "path/to/schema.prisma"
  }
}

The provided location in package.json will be the default location of the Prisma schema file for any Prisma CLI command you invoke. Note that you can still override this default location by manually specifying the --schema option when invoking a Prisma CLI command.

📚 Documentation: Prisma schema file location

Already existing preview features from previous releases

Just a quick reminder:

• In version 2.6.0 we introduced one preview feature, namely atomicNumberOperations.
• In version 2.5.0 we introduced one preview feature, namely insensitiveFilters.
• In version 2.1.0 we introduced two preview features, namely connectOrCreate and transactionApi.

In case they're useful for you, please give them a try and share your feedback! These features remain in preview in this release.

Feedback wanted: How does introspection work for you?

In the last few releases we improved Prisma's database introspection, most notably with "More robust introspection by keeping manual changes in the Prisma schema file" but also many smaller bug fixes. We think it is pretty stable now, and would love to hear from you, our users, how you have been using prisma introspect recently!

If you have used introspection in the past, whether it worked well or not so well with your database, please let us know by sharing your feedback on GitHub!

🌟 Help us spread the word about Prisma

To help spread the word about Prisma, we'd very much appreciate if you would star this repo 🌟 And if you're excited about the features in this week's release, then help us and share it on Twitter.

Fixes and improvements

prisma

• Add ability to configure custom schema location instead of requiring --schema arg
• Running prisma init with unknown parameter just outputs null
• Use dotenv-expand instead of dotenv package to allow variable expressions in the env file
• Update denylist in engines and client
• Engine panics when schema.prisma is empty, we could make it an error.
• Schema parser errors shouldn't be reported to error reporting
• Loss of precision on Float fields with many digits
• 2.6.0 Broke some of my update queries
• Log Prisma client version being generated
• Broken set on nested update on 2.6.0
• Multiple many-many relationships appears to cause an introspection failure.
• Query validation error updating Date field
• Error: [libs/datamodel/core/src/dml/model.rs:166:14] We assume an internally valid datamodel before mutating.
• While using PM2 on a prisma related project popus up prisma client cmd terminal on windows
• Separate command and GH action workflow to run integration tests
• The introspect command in v2.6.x does not remember cuid() defaults for a field and user-defined @relation name property
• Do not run GitHub Action Workflows on fork of example repository
• Do not build binaries for FreeBSD 12 any more
• introspect --force does not work

prisma-client-js

• PANIC: invalid or out-of-range date
• aggregateApi and sum returns null if no record

migrate

• Unable to run prisma migrate with dotenv-cli
• Error when running initial migration with a schema in DATABASE_URL

language-tools

• Add vsix bundle to releases
• Create a local release with .vsix file and publish from that
• E2E tests run on every PR should use local LSP
• Abnormal CPU usage
• Change of client/index.d.ts should not show a notification
• This version is built from commit undefined. This is for Prisma CLI ...
• Reorganize READMEs

studio

• Stuck at "Getting things ready" when Studio is open in multiple places
• Filtering issue (not/equals/contains/startsWith) when "" empty string field Value
• Error when opening certain relations
• Tab dirtyness should be cancelled out when it is returned to its original state
• Cannot edit a relation that is null
• Allow typing in partial dates in table cells
• Allow typing in partial dates in filters
• Very slow to load for large Postgres schemas
• When changing a relation, the scalar that constitutes it does not change
• Unable to change relations & relation lists in an uncommitted record
• If you type in an arbitrary id in a scalar that is part of a relation, Save Changes will always fail
• Oopsies: filter UI is broken
• Deleting a model with unsaved changes open in a tab might result in a fatal error

prisma-engines

• Improve error for nonexistent column in SQLite
• Native types: allow specifying unsigned integer types on MySQL
• Validate that prisma enums have at least one variant/value
• Parser must error if native types are used but feature flag is not enabled
• Trigger binary builds via square brackets in commit message

Credits

Huge thanks to @bre7, @rahul3v, @jasonkuhrt and @Weakky for helping!