fix(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@cerbos/grpc (source)	0.18.1 -> 0.18.3
@prisma/client (source)	5.17.0 -> 5.20.0
@types/jest (source)	29.5.12 -> 29.5.13
@types/node (source)	20.14.14 -> 20.16.7
mongoose (source)	8.5.2 -> 8.6.3
prisma (source)	5.17.0 -> 5.20.0
ts-jest (source)	29.2.4 -> 29.2.5
typescript (source)	5.5.4 -> 5.6.2

---

Release Notes

cerbos/cerbos-sdk-javascript (@​cerbos/grpc)

v0.18.3

Compare Source

Changed

• Bump dependency on [@​bufbuild/protobuf] to 2.1.0 (#​1012)

• Bump dependency on [@​grpc/grpc-js] to 1.11.3 (#​1000, #​1011)

v0.18.2

Compare Source

Changed

• Replace dependency on [protobufjs] with [@​bufbuild/protobuf] (#​990)

• Bump dependency on [@​grpc/grpc-js] to 1.11.1 (#​974, #​979, #​981)

prisma/prisma (@​prisma/client)

v5.20.0

Compare Source

🌟 Help us spread the word about Prisma by starring the repo or posting on X about the release. 🌟

Highlights

strictUndefinedChecks in Preview

With Prisma ORM 5.20.0, the Preview feature strictUndefinedChecks will disallow any value that is explicitly undefined and will be a runtime error. This change is direct feedback from this GitHub issue and follows our latest proposal on the same issue.

To demonstrate the change, take the following code snippet:

prisma.table.deleteMany({
  where: {
    // If `nullableThing` is nullish, this query will remove all data.
    email: nullableThing?.property,
  }
})

In Prisma ORM 5.19.0 and below, this could result in unintended behavior. In Prisma ORM 5.20.0, if the strictUndefinedChecks Preview feature is enabled, you will get a runtime error instead:

Invalid \`prisma.user.findMany()\` invocation in
/client/tests/functional/strictUndefinedChecks/test.ts:0:0
  XX })
  XX 
  XX test('throws on undefined input field', async () => {
→ XX   const result = prisma.user.deleteMany({
         where: {
           email: undefined
                  ~~~~~~~~~
         }
       })
Invalid value for argument \`where\`: explicitly \`undefined\` values are not allowed."

We have also introduced the Prisma.skip symbol, which will allow you to get the previous behavior if desired.

prisma.table.findMany({
  where: {
    // Use Prisma.skip to skip parts of the query
    email: nullableEmail ?? Prisma.skip
  }
})

From Prisma ORM 5.20.0 onward, we recommend enabling strictUndefinedChecks, along with the TypeScript compiler option exactOptionalPropertyTypes, which will help catch cases of undefined values at compile time. Together, these two changes will help protect your Prisma queries from potentially destructive behavior.

strictUndefinedChecks will be a valid Preview feature for the remainder of Prisma ORM 5. With our next major version, this behavior will become the default and the Preview feature will be “graduated” to Generally Available.

If you have any questions or feedback about strictUndefinedChecks, please ask/comment in our dedicated Preview feature GitHub discussion.

typedSql bug fix

Thank you to everyone who has tried out our typedSql Preview feature and provided feedback! This release has a quick fix for typescript files generated when Prisma Schema enums had hyphens.

Fixes and improvements

Prisma

• Prisma incorrectly parses CRDB's FK constraint error as not available.
• Invalid TypeScript files created by generate when typedSql is enabled and enum contains hyphens.
• @prisma/internals didn't list ts-toolbelt in dependencies.
• using $extends prevents model comments from being passed to TypeScript

Prisma Engines

• Planetscale engine tests: interactive_tx
• Fix broken engine size publishing workflow

Credits

Huge thanks to @​mcuelenaere, @​pagewang0, @​key-moon, @​pranayat, @​yubrot, @​thijmenjk, @​mydea, @​HRM, @​haaawk, @​baileywickham, @​brian-dlee, @​nickcarnival, @​eruditmorina, @​nzakas, and @​gutyerrez for helping!

v5.19.1

Compare Source

Today, we are issuing the 5.19.1 patch release.

What's Changed

We've fixed the following issues:

• https://github.com/prisma/prisma/issues/25103
• https://github.com/prisma/prisma/issues/25137
• https://github.com/prisma/prisma/issues/25104
• https://github.com/prisma/prisma/issues/25101

Full Changelog: prisma/prisma@5.19.0...5.19.x, prisma/prisma-engines@5.19.0...5.19.x

v5.19.0

Compare Source

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

🌟 Help us spread the word about Prisma by starring the repo or posting on X about the release. 🌟

Highlights

Introducing TypedSQL

TypedSQL is a brand new way to interact with your database from Prisma Client. After enabling the typedSql Preview feature, you’re able to write SQL queries in a new sql subdirectory of your prisma directory. These queries are then checked by Prisma during using the new --sql flag of prisma generate and added to your client for use in your code.

To get started with TypedSQL:

1. Make sure that you have the latest version of prisma and @prisma/client installed:

   npm install -D prisma@latest
   npm install @​prisma/client@latest
   

2. Enable the typedSql Preview feature in your Prisma Schema.

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

3. Create a sql subdirectory of your prisma directory.

   mkdir -p prisma/sql
   

4. You can now add .sql files to the sql directory! Each file can contain one sql query and the name must be a valid JS identifier. For this example, say you had the file getUsersWithPosts.sql with the following contents:

   SELECT u.id, u.name, COUNT(p.id) as "postCount"
   FROM "User" u
   LEFT JOIN "Post" p ON u.id = p."authorId"
   GROUP BY u.id, u.name

5. Import your SQL query into your code with the @prisma/client/sql import:

      import { PrismaClient } from '@​prisma/client'
      import { getUsersWithPosts } from '@​prisma/client/sql'
   
      const prisma = new PrismaClient()
   
      const usersWithPostCounts = await prisma.$queryRawTyped(getUsersWithPosts)
      console.log(usersWithPostCounts)

There’s a lot more to talk about with TypedSQL. We think that the combination of the high-level Prisma Client API and the low-level TypedSQL will make for a great developer experience for all of our users.

To learn more about behind the “why” of TypedSQL be sure to check out our announcement blog post.

For docs, check out our new TypedSQL section.

Bug fixes

Driver adapters and D1

A few issues with our driverAdapters Preview feature and Cloudflare D1 support were resolved via https://github.com/prisma/prisma-engines/pull/4970 and https://github.com/prisma/prisma/pull/24922

• Mathematic operations such as max, min, eq, etc in queries when using Cloudflare D1.
• Resolved issues when comparing BigInt IDs when relationMode="prisma" was enabled and Cloudflare D1 was being used.

Joins

• https://github.com/prisma/prisma/issues/23742 fixes Prisma Client not supporting deeply nested some clauses when the relationJoins Preview feature was enabled.

Join us

Looking to make an impact on Prisma in a big way? We're now hiring engineers for the ORM team!

• Senior Engineer (TypeScript): This person will be primarily working on the TypeScript side and evolving our Prisma client. Rust knowledge (or desire to learn Rust) is a plus.
• Senior Engineer (Rust): This person will be focused on the prisma-engines Rust codebase. TypeScript knowledge (or, again, a desire to learn) is a plus.

Credits

Huge thanks to @​mcuelenaere, @​pagewang0, @​Druue, @​key-moon, @​Jolg42, @​pranayat, @​ospfranco, @​yubrot, @​skyzh for helping!

v5.18.0

Compare Source

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

Highlights

Native support for UUIDv7

Previous to this release, the Prisma Schema function uuid() did not accept any arguments and created a UUIDv4 ID. While sufficient in many cases, UUIDv4 has a few drawbacks, namely that it is not temporally sortable.

UUIDv7 attempts to resolve this issue, making it easy to temporally sort your database rows by ID!

To support this, we’ve updated the uuid() function in Prisma Schema to accept an optional, integer argument. Right now, the only valid values are 4 and 7, with 4 being the default.

model User {
  id   String @​id @​default(uuid()) // defaults to 4
  name String
}

model User {
  id   String @​id @​default(uuid(4)) // same as above, but explicit
  name String
}

model User {
  id   String @​id @​default(uuid(7)) // will use UUIDv7 instead of UUIDv4
  name String
}

Bug squashing

We’ve squashed a number of bugs this release, special thanks to everyone who helped us! A few select highlights are:

• SQLite db will now be created and read from the correct location when using prismaSchemaFolder.
• Empty Json[] fields will now return [] instead of null when accessed through a join using the relationJoins Preview feature.

Fixes and improvements

Prisma

• Support UUID v7

Language tools (e.g. VS Code)

• Support fetching references for a model

Credits

Huge thanks to @​mcuelenaere, @​pagewang0, @​Druue, @​key-moon, @​Jolg42, @​pranayat, @​ospfranco, @​yubrot, @​skyzh, @​haaawk for helping!

Automattic/mongoose (mongoose)

v8.6.3

Compare Source

==================

• fix: make getters convert uuid to string when calling toObject() and toJSON() #​14890 #​14869
• fix: fix missing Aggregate re-exports for ESM #​14886 wongsean
• types(document): add generic param to depopulate() to allow updating properties #​14891 #​14876

v8.6.2

Compare Source

==================

• fix: make set merge deeply nested objects #​14870 #​14861 ianHeydoc
• types: allow arbitrary keys in query filters again (revert #​14764) #​14874 #​14863 #​14862 #​14842
• types: make SchemaType static setters property accessible in TypeScript #​14881 #​14879
• type(inferrawdoctype): infer Date types as JS dates rather than Mongoose SchemaType Date #​14882 #​14839

v8.6.1

Compare Source

==================

• fix(document): avoid unnecessary clone() in applyGetters() that was preventing getters from running on 3-level deep subdocuments #​14844 #​14840 #​14835
• fix(model): throw error if bulkSave() did not insert or update any documents #​14837 #​14763
• fix(cursor): throw error in ChangeStream constructor if changeStreamThunk() throws a sync error #​14846
• types(query): add $expr to RootQuerySelector #​14845
• docs: update populate.md to fix missing match: { } #​14847 makhoulshbeeb

v8.6.0

Compare Source

==================

• feat: upgrade mongodb -> 6.8.0, handle throwing error on closed cursor in Mongoose with MongooseError instead of MongoCursorExhaustedError #​14813
• feat(model+query): support options parameter for distinct() #​14772 #​8006
• feat(QueryCursor): add getDriverCursor() function that returns the raw driver cursor #​14745
• types: change query selector to disallow unknown top-level keys by default #​14764 alex-statsig
• types: make toObject() and toJSON() not generic by default to avoid type widening #​14819 #​12883
• types: avoid automatically inferring lean result type when assigning to explicitly typed variable #​14734

v8.5.5

Compare Source

==================

• fix(populate): fix a couple of other places where Mongoose gets the document's _id with getters #​14833 #​14827 #​14759
• fix(discriminator): shallow clone Schema.prototype.obj before merging schemas to avoid modifying original obj #​14821
• types: fix schema type based on timestamps schema options value #​14829 #​14825 ark23CIS

v8.5.4

Compare Source

==================

• fix: add empty string check for collection name passed #​14806 Shubham2552
• docs(model): add 'throw' as valid strict value for bulkWrite() and add some more clarification on throwOnValidationError #​14809

v8.5.3

Compare Source

==================

• fix(document): call required functions on subdocuments underneath nested paths with correct context #​14801 #​14788
• fix(populate): avoid throwing error when no result and lean() set #​14799 #​14794 #​14759 MohOraby
• fix(document): apply virtuals to subdocuments if parent schema has virtuals: true for backwards compatibility #​14774 #​14771 #​14623 #​14394
• types: make HydratedSingleSubdocument and HydratedArraySubdocument merge types instead of using & #​14800 #​14793
• types: support schema type inference based on schema options timestamps as well #​14773 #​13215 ark23CIS
• types(cursor): indicate that cursor.next() can return null #​14798 #​14787
• types: allow mongoose.connection.db to be undefined #​14797 #​14789
• docs: add schema type widening advice #​14790 JstnMcBrd

kulshekhar/ts-jest (ts-jest)

v29.2.5

Compare Source

microsoft/TypeScript (typescript)

v5.6.2

Compare Source

---

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - "after 9am and before 5pm Monday" (UTC).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.