[Snyk] Upgrade @prisma/client from 6.0.1 to 6.2.1 #8

nwikeodigwe · 2025-01-30T05:19:42Z

Snyk has created this PR to upgrade @prisma/client from 6.0.1 to 6.2.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 69 versions ahead of your current version.
The recommended version was released 22 days ago.

Release notes

Package name: @prisma/client

6.2.1 - 2025-01-08
Today we are releasing the 6.2.1 patch release to address an issue with some of the omitApi preview feature checks having been accidentally omitted when making the feature GA. Now it is fully functional without the preview feature flag.

Changes
- #25997
6.2.1-dev.2 - 2025-01-08
6.2.1-dev.1 - 2025-01-08
6.2.0 - 2025-01-07
Today we're releasing Prisma ORM version 6.2.0 🎉

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

We have a number of new features in this version, including support for json and enum fields in SQLite, a new updateManyAndReturn function, support for ULID values, as well as the promotion of the omit feature from Preview to Generally Availability.

Highlights

Excluding fields via omit is now production-ready

Our number one requested feature is out of Preview and Generally Available. In 6.2.0, you no longer need to add omitApi to your list of Preview features:
```
generator client {
  provider        = "prisma-client-js"
- previewFeatures = ["omitApi"]
}
```
As a refresher: omit allows you to exclude certain fields from being returned in the results of your Prisma Client queries.

You can either do this locally, on a per-query level:
```
const result = await prisma.user.findMany({
  omit: {
    password: true,
  },
});
```
Or globally, to ensure a field is excluded from all queries of a certain model:

const prisma = new PrismaClient({
omit: {
user: {
password: true
}
}
})

// The password field is excluded in all queries, including this one
const user = await prisma.user.findUnique({ where: { id: 1 } })

For more information on omit, be sure to check our documentation.

json and enum fields in SQLite

Previous to this version, you could not define json and enum fields in your Prisma schema when using SQLite. The respective GitHub issues have been among the most popular ones in our repo, so with our new approach to open-source governance, we finally got to work and implemented these.

Working with JSON and Enum fields works similarly to other database providers, here’s an example:

datasource db {
provider = "sqlite"
url = "file:./dev.db"
}

model User {
id Int @ id @ default(autoincrement())
name String
role Role
data Json
}

enum Role {
Customer
Admin
}

Support for auto-generated ULID values

Similar to cuid2 support released in ORM version 6.0.0, we are now adding support for Universally Unique Lexicographically Sortable Identifiers (or short: ULIDs 😄) in version 6.2.0. A ULID value is a 26-character alphanumeric string, e.g. 01GZ0GZ3XARH8ZP44A7TQ2W4ZD.

With this new feature, you can now create records with auto-generated ULID values for String fields:
```
model User {
  id String @ id @ default(ulid())  
}
```
New batch function: updateManyAndReturn

updateMany allows you to update many records in your database, but it only returns the count of the affected rows, not the resulting rows themselves. With updateManyAndReturn you are now able to achieve this:
```
const users = await prisma.user.updateManyAndReturn({
  where: {
    email: {
      contains: 'prisma.io',
    }
  },
  data: {
    role: 'ADMIN'
  }
})
```
This call to updateManyAndReturn will now return the actual records that have been updated in the query:
```
[{
  id: 22,
  name: 'Alice',
  email: '[email protected]',
  profileViews: 0,
  role: 'ADMIN',
  coinflips: []
}, {
  id: 23,
  name: 'Bob',
  email: '[email protected]',
  profileViews: 0,
  role: 'ADMIN',
  coinflips: []
}]
```
Please note that like createManyAndReturn, updateManyAndReturn is only supported in PostgreSQL, CockroachDB, and SQLite.

Fixed runtime error in Node.js v23

While not officially supported, we understand that a lot of you like to be on the latest Node.js version — so we fixed an error that only occurred on Node.js 23. Happy coding ✌️

Prisma is hiring 🤝

Join us at Prisma to work on the most popular TypeScript ORM and other exciting products like the first serverless database built on unikernels!

We currently have two open roles in our Engineering team:
- Senior Software Engineer (Prisma ORM)
- Senior Software Engineer (Prisma Data Platform)
If these don’t fit, you can still check out our jobs page and send a general application.
6.2.0-integration-engines-6-2-0-9-feat-sqlite-enum-de83b89d1d4a474e646feab1929290e26fdf82d7.4 - 2025-01-02
6.2.0-integration-engines-6-2-0-9-feat-sqlite-enum-de83b89d1d4a474e646feab1929290e26fdf82d7.3 - 2025-01-02
6.2.0-integration-engines-6-2-0-9-feat-sqlite-enum-de83b89d1d4a474e646feab1929290e26fdf82d7.2 - 2024-12-31
6.2.0-integration-engines-6-2-0-9-feat-sqlite-enum-de83b89d1d4a474e646feab1929290e26fdf82d7.1 - 2024-12-31
6.2.0-integration-engines-6-2-0-7-feat-update-many-and-return-f165828e67aa4eee12e3988ecaef03a622c2c96c.7 - 2024-12-30
6.2.0-integration-engines-6-2-0-7-feat-update-many-and-return-f165828e67aa4eee12e3988ecaef03a622c2c96c.6 - 2024-12-30
6.2.0-integration-engines-6-2-0-7-feat-update-many-and-return-f165828e67aa4eee12e3988ecaef03a622c2c96c.5 - 2024-12-30
6.2.0-integration-engines-6-2-0-7-feat-update-many-and-return-f165828e67aa4eee12e3988ecaef03a622c2c96c.4 - 2024-12-30
6.2.0-integration-engines-6-2-0-7-feat-update-many-and-return-f165828e67aa4eee12e3988ecaef03a622c2c96c.3 - 2024-12-30
6.2.0-integration-engines-6-2-0-7-feat-update-many-and-return-f165828e67aa4eee12e3988ecaef03a622c2c96c.2 - 2024-12-30
6.2.0-integration-engines-6-2-0-7-feat-update-many-and-return-f165828e67aa4eee12e3988ecaef03a622c2c96c.1 - 2024-12-30
6.2.0-integration-engines-6-2-0-13-integration-sql-nested-transactions4-fa6eebbccfd5b45ef639efcb0fe328c189735aa4.2 - 2025-01-07
6.2.0-integration-engines-6-2-0-13-integration-sql-nested-transactions4-fa6eebbccfd5b45ef639efcb0fe328c189735aa4.1 - 2025-01-07
6.2.0-dev.14 - 2025-01-07
6.2.0-dev.13 - 2025-01-06
6.2.0-dev.12 - 2025-01-06
6.2.0-dev.11 - 2025-01-06
6.2.0-dev.10 - 2025-01-02
6.2.0-dev.9 - 2024-12-25
6.2.0-dev.8 - 2024-12-24
6.2.0-dev.7 - 2024-12-23
6.2.0-dev.6 - 2024-12-20
6.2.0-dev.5 - 2024-12-19
6.2.0-dev.4 - 2024-12-19
6.2.0-dev.3 - 2024-12-19
6.2.0-dev.2 - 2024-12-18
6.2.0-dev.1 - 2024-12-18
6.1.0 - 2024-12-17
Today we're releasing Prisma ORM version 6.1.0

In this version our tracing Preview feature is being graduated to GA!

Highlights

Tracing goes GA

The tracing Preview feature is now stable. You now no longer have to include tracing in your set of enabled preview features.
```
generator client {
   provider        = "prisma-client-js"
-  previewFeatures = ["tracing"]
}
```
We have also changed some of the spans generated by Prisma Client. Previously, a trace would report the following spans:
```
prisma:client:operation
prisma:client:serialize
prisma:engine
prisma:engine:connection
prisma:engine:db_query
prisma:engine:serialize
```
Now, the following are reported:
```
prisma:client:operation
prisma:client:serialize
prisma:engine:query
prisma:engine:connection
prisma:engine:db_query
prisma:engine:serialize
prisma:engine:response_json_serialization
```
Additionally, we have made a few changes to our dependencies:
- @ opentelemetry/api is now a peer dependency instead of a regular dependency
- registerInstrumentations in @ opentelemetry/instrumentation is now re-exported by @ prisma/instrumentation
After upgrading to Prisma ORM 6.1.0 you will need to add @ opentelemetry/api to your dependencies if you haven't already:
```
npm install @ opentelemetry/api
```
You will also no longer need to have @ opentelemetry/instrumentation if you only use registerInstrumentations. In this case you can import registerInstrumentations from @ prisma/instrumentation
```
- import { PrismaInstrumentation } from '@ prisma/instrumentation'
+ import { PrismaInstrumentation, registerInstrumentations } from '@ prisma/instrumentation'
```
Mutli-line comments in Prisma Schema Language (PSL)

Comments can now be defined as multi-line in your Prisma schema! Comments can use the existing format:
```
// this is a schema comment
```
or can now also use our multi-line format:
```
/*
 * this is a multi-line comment
 * You can add in all you want here
 * Keep typing and this comment will keep on going
 */
```
Bug fixes

Tracing related

As we're moving our tracing preview to GA, a number of issues have been resolved. Here are a few highlights:
- Tests for tracing expanded and improved
- Issues with Elastic APM addressed
- Issues with Datadog tracer addressed
- Prisma Client now respects suppressTracing
Other issues

We also have a number of other issues that were resolved outside of our tracing feature.
- Resolved type issues with the PrismaNeonHTTP adapter
- findUnique returns null when used instead of Promise.all
- Resolved an issue with the latest version of Alpine Linux
Fixes and improvements

Prisma
- Tracing: Detailed report and profiling informations
- Prisma Client Request Tracing Integration
- Instrumentation error in production: TypeError: parentTracer.getSpanLimits is not a function
- Prisma is using the internal Span constructor
- Prisma Client doesn't put all OTEL trace spans under one parent span
- Prisma trace has unaccounted time
- prisma:engine spans do not respect suppressTracing()
- tracing: engine spans don't pass through Sampler
- Add tests for tracing and different ways to open the first connection (including internal spans)
- Tracing: Long trailing delay in prisma:client:operation
- prisma:engine spans are missing when there are multiple new PrismaClient() invocations
- parentTracer.getSpanLimits is not a function
- Support tracers not derived from opentelemetry-sdk-trace-base (e.g. Datadog tracer)
- traceparent comments with multiple SQL statements
- Make @ prisma/instrumentation dependencies peer dependencies
- Make sure db.statement attribute doesn't include the traceparent comment
- [Instrumentation] registerInstrumentations uses the global provider instead of the one passed in
- Instrumentation: Problems in working with Elastic APM
- PrismaNeonHTTP adapter breaks on some types e.g. timestamp
- Promise.all() returns null with findUnique()
- Alpine Linux 3.21: Prisma failed to detect the libssl/openssl version to use
Prisma Client
- Tracing operation duration bug under stress test
- @ prisma/instrumentation Type Error: 'InstrumentionNodeModuleDefintion' is not generic
6.1.0-integration-expose-deserialize-raw-result.1 - 2024-12-02
6.1.0-integration-engines-6-1-0-18-fixup-wasm-response-json-serialization-span-8988abfac9afb8e5e01a2f1862852f4e8ce393e0.1 - 2024-12-16
6.1.0-integration-engines-6-1-0-17-fixup-wasm-response-json-serialization-span-18513eab509bdb5aef5cdd9c553594c3924d18cb.1 - 2024-12-16
6.1.0-dev.34 - 2024-12-17
6.1.0-dev.33 - 2024-12-17
6.1.0-dev.32 - 2024-12-17
6.1.0-dev.31 - 2024-12-16
6.1.0-dev.30 - 2024-12-16
6.1.0-dev.29 - 2024-12-16
6.1.0-dev.28 - 2024-12-16
6.1.0-dev.27 - 2024-12-16
6.1.0-dev.26 - 2024-12-16
6.1.0-dev.25 - 2024-12-16
6.1.0-dev.24 - 2024-12-16
6.1.0-dev.23 - 2024-12-16
6.1.0-dev.22 - 2024-12-16
6.1.0-dev.21 - 2024-12-16
6.1.0-dev.20 - 2024-12-16
6.1.0-dev.19 - 2024-12-16
6.1.0-dev.18 - 2024-12-16
6.1.0-dev.17 - 2024-12-16
6.1.0-dev.16 - 2024-12-16
6.1.0-dev.15 - 2024-12-13
6.1.0-dev.14 - 2024-12-12
6.1.0-dev.13 - 2024-12-06
6.1.0-dev.12 - 2024-12-05
6.1.0-dev.11 - 2024-12-04
6.1.0-dev.10 - 2024-12-03
6.1.0-dev.9 - 2024-12-03
6.1.0-dev.8 - 2024-12-03
6.1.0-dev.7 - 2024-12-02
6.1.0-dev.6 - 2024-12-02
6.1.0-dev.5 - 2024-12-02
6.1.0-dev.4 - 2024-12-01
6.1.0-dev.3 - 2024-11-30
6.1.0-dev.2 - 2024-11-30
6.1.0-dev.1 - 2024-11-30
6.0.1 - 2024-12-02
Today we are releasing the 6.0.1 patch release to address an issue with using Prisma Client generated in a custom output path with Next.js.

Changes
- Revert "type": "commonjs" addition in generated package.json

from @prisma/client GitHub release notes

Important

Check the changes in this PR to ensure they won't cause issues with your project.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

📜 Customise PR templates

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Snyk has created this PR to upgrade @prisma/client from 6.0.1 to 6.2.1. See this package in npm: @prisma/client See this project in Snyk: https://app.snyk.io/org/nwikeodigwe/project/c8fd9917-b566-4f49-8ba9-7b93cb075465?utm_source=github&utm_medium=referral&page=upgrade-pr

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Snyk] Upgrade @prisma/client from 6.0.1 to 6.2.1 #8

[Snyk] Upgrade @prisma/client from 6.0.1 to 6.2.1 #8

nwikeodigwe commented Jan 30, 2025

Changes

Highlights

Excluding fields via `omit` is now production-ready

`json` and `enum` fields in SQLite

Support for auto-generated ULID values

New batch function: `updateManyAndReturn`

Fixed runtime error in Node.js v23

Prisma is hiring 🤝

Highlights

Tracing goes GA

Mutli-line comments in Prisma Schema Language (PSL)

Bug fixes

Tracing related

Other issues

Fixes and improvements

Prisma

Prisma Client

Changes

[Snyk] Upgrade @prisma/client from 6.0.1 to 6.2.1 #8

Are you sure you want to change the base?

[Snyk] Upgrade @prisma/client from 6.0.1 to 6.2.1 #8

Conversation

nwikeodigwe commented Jan 30, 2025

Snyk has created this PR to upgrade @prisma/client from 6.0.1 to 6.2.1.

Changes

Highlights

Excluding fields via omit is now production-ready

json and enum fields in SQLite

Support for auto-generated ULID values

New batch function: updateManyAndReturn

Fixed runtime error in Node.js v23

Prisma is hiring 🤝

Highlights

Tracing goes GA

Mutli-line comments in Prisma Schema Language (PSL)

Bug fixes

Tracing related

Other issues

Fixes and improvements

Prisma

Prisma Client

Changes

Excluding fields via `omit` is now production-ready

`json` and `enum` fields in SQLite

New batch function: `updateManyAndReturn`