# Prisma 3.0.1 — Release & Upgrade Intelligence
- **Product:** Prisma (https://prisma.io)
- **Version:** 3.0.1
- **Released:** Sep 07, 2021
- **Impact Score:** 7/10
- **Breaking Changes:** Source flagged
- **Canonical Analysis:** https://changelogs.us/prisma/updates/3.0.1/

## Executive Summary (TL;DR)
Prisma 3.0.1. Source highlight: Today, we are excited to share the `3.0.1` stable release 🎉

## Breaking Changes & Deprecations
- [As previously announced](https://www.prisma.io/blog/prisma-adopts-semver-strictly), Prisma has adopted SemVer strictly and this is the first major release which means it has some breaking changes.
- For all the breaking changes, there are guides and documentation to assist you with the upgrade.
- We recommend that you read through the breaking changes below carefully and make sure that you've correctly upgraded your application.
- 🚨 **Please note** that the defaults change in this release. In some cases, this can lead to queries behaving differently in Prisma 3.x compared to Prisma 2.x, since the database will be enforcing referential actions, and not Prisma Client anymore. This means that if you only update your client without changing your Prisma schema, you will lose Prisma-level protections against cascading deletes. Read more in the Breaking Changes section below and the [upgrade guide](https://www.prisma.io/docs/concepts/components/prisma-schema/relations/referential-actions#upgrade-paths) for a detailed explanati
- 🚨 **Please note** that you will have to make conscious decisions about constraint names when you upgrade to Prisma 3. Prisma will help you with the upgrade process using introspection with  `prisma db pull` and Prisma Migrate. Read more in the Breaking Changes section below and the [upgrade guide](https://prisma.io/docs/guides/upgrade-guides/upgrading-versions/upgrading-to-prisma-3/named-constraints) for a detailed explanation and steps to follow. 🚨
- 🚨 **Please note** that if you already have a seed script that worked created in versions prior, you will need to add the script to `prisma.seed` in your `package.json` and adapt the script to the new API. Read more in the Breaking Changes section below and the [seeding docs](https://www.prisma.io/docs/guides/database/seed-database) for a complete explanation and walkthroughs of common use cases.
- Breaking Changes Some of the features above introduce breaking changes. In this section, we cover the breaking changes in more detail with links to upgrade guides in the documentation. We recommend that you read through the breaking changes carefully and make sure that you've upgraded and tested your application.
- Some of the features above introduce breaking changes. In this section, we cover the breaking changes in more detail with links to upgrade guides in the documentation. We recommend that you read through the breaking changes carefully and make sure that you've upgraded and tested your application.

## New Features
- Add the script to `prisma.seed` in your `package.json`
- Introspection adds an extra space to map properties in enums in prisma.schema
- EPIC: re-design of `db seed` feature
- Add runtime check to `$queryRaw("...")` to throw for JS calls

## Improvements
- Microsoft SQL Server and Azure SQL Connector
- Seeding with `prisma db seed` has been revamped
- Order by Aggregate in Group By
- Select Relation Count

## Upgrade Command
```bash
npm install --save-dev --save-exact prisma@3.0.1
```