Skip to content

fix(deps): update all non-major dependencies #231

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix(deps): update all non-major dependencies #231

wants to merge 1 commit into from
+836 −920

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 29, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@prisma/client (source) ^5.16.1 -> ^5.22.0 age adoption passing confidence
@swc/cli ^0.3.14 -> ^0.7.7 age adoption passing confidence
@swc/core (source) ^1.6.5 -> ^1.11.29 age adoption passing confidence
@types/amqplib (source) ^0.10.5 -> ^0.10.7 age adoption passing confidence
@types/node (source) ^20.14.9 -> ^20.17.57 age adoption passing confidence
amqplib (source) ^0.10.4 -> ^0.10.8 age adoption passing confidence
drizzle-kit (source) ^0.22.7 -> ^0.31.1 age adoption passing confidence
drizzle-orm (source) ^0.31.2 -> ^0.44.2 age adoption passing confidence
ioredis ^5.4.1 -> ^5.6.1 age adoption passing confidence
lerna (source) ^8.1.5 -> ^8.2.2 age adoption passing confidence
prisma (source) ^5.16.1 -> ^5.22.0 age adoption passing confidence
rimraf ^5.0.7 -> ^5.0.10 age adoption passing confidence

Release Notes

prisma/prisma (@​prisma/client)

v5.22.0

Compare Source

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

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

Highlights
Further Tracing Improvements

In our ongoing effort to stabilize the tracing Preview feature, we’ve made our spans compliant with OpenTelemetry Semantic Conventions for Database Client Calls. This should lead to better compatibility with tools such as DataDog and Sentry.

We’ve also included numerous bug fixes that should make this Preview feature easier to work with.

Metrics bug fix

Occasionally, connection pool metrics would become negative or grow unbounded. In this release, connection pool metrics should stay consistent.

Connection Pool Timeout fix

In a specific case, there could be issues where fetching a new connection from the connection pool would time out, regardless of the state of the application and connection pool. If you have experience connection pool issues accessing a PostgreSQL database with TLS encryption in a resource-constrained environment (such as Function-as-a-Service offerings or very small VPS) this should resolve those issues.

Special thanks to @​youxq for their pull request and help resolving this issue!

Join us

Looking to make an impact on Prisma in a big way? We're hiring!

Learn more on our careers page: https://www.prisma.io/careers

Fixes and improvements
Prisma Migrate
Prisma
Credits

Huge thanks to @​tmm1, @​Takur0, @​hinaloe, @​andyjy, and @​youxq for helping!

v5.21.1

Compare Source

  • Fixed a bug where migrations were not using shadow database correctly in some edge cases

v5.21.0

Compare Source

Today, we are excited to share the 5.21.0 release 🎉

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

Highlights
Better support for tracing in MongoDB

The tracing Preview feature now has full support for MongoDB with previously missing functionality now implemented. This is a part of the ongoing effort to stabilize this Preview feature and release it in General Availability.

tracing is a Preview feature that enables built-in support for OpenTelemetry instrumentation inside the Prisma Client and provides deep insights into the performance and timing of your queries. See our documentation for more information.

For an easy to use and zero-configuration tracing instrumentation tool with a dashboard that provides an overview of your queries, statistics, and AI-powered recommendations, try Prisma Optimize.

WebAssembly engine size decrease for edge functions

Due to recent changes, some users experienced a steep increase of the bundle size in Prisma 5.20 when using the driverAdapters Preview feature, going over the 1 MB limit on the free tier of Cloudflare Workers. This has now been fixed.

Fixes and improvements
Prisma Engines
Credits

Huge thanks to @​austin-tildei, @​LucianBuzzo, @​mcuelenaere, @​pagewang0, @​key-moon, @​pranayat, @​yubrot, @​skyzh for helping!

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 Engines
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:

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
MongoDB

The MongoDB driver for Rust (that our query engine users under the hood) had behavior that prioritized IPv4 connections over IPv6 connections. In IPv6-only environments, this could lead to significant "cold starts" where the query engine had to wait for IPv4 to fail before the driver would try IPv6.

With help from the MongoDB team, this has been resolved. The driver will now try IPv4 and IPv6 connections in parallel and then move forward with the first response. This should prevent cold start issues that have been seen with MongoDB in Prisma Accelerate.

Thank you to the MongoDB team!

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:

Fixes and improvements
Prisma
Language tools (e.g. VS Code)
Share your feedback about Prisma ORM

We want to know how you like working with Prisma ORM in your projects! Please take our 2min survey and let us know what you like or where we can improve 🙏

Credits

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

v5.17.0

Compare Source

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

Highlights

VSCode extension improvements

We’re happy to introduce some cool new features that will make your experience with the Prisma VSCode extension even better!

Find references across schema files

The ability to hop between references of a given symbol is really useful in application code and now with the introduction of multi-file schema, we think it’s the perfect time to bring this feature to the VSCode extension!

With the 5.17.0 release, you’ll now have the ability to use the native “find references” feature to find any usage of a given symbol

references

Added context on hover

When hovering over a symbol that references a view, type, enum, or any other block with multiple values, you’ll now see a handy pop out that shows what is in that block at a glance.

image

Additional quick fixes

We’ve taken some fixes made by the prisma format cli command and made them quick fixes available to the VSCode Extension. Now, when you have forget a back relation or relation scalar field, you’ll now see in real time what is wrong and have the option to fix it via the extension.

image (1)

QueryRaw performance improvements

We’ve changed the response format of queryRaw to decrease its average size which reduces serialization CPU overhead.

When querying large data sets, we expect you to see improved memory usage and up to 2x performance improvements.

Fixes and improvements

Prisma Client
Prisma
Language tools (e.g. VS Code)

Credits

Huge thanks to @​key-moon, @​pranayat, @​yubrot, @​skyzh for helping!

v5.16.2

Compare Source

Today, we are issuing the 5.16.2 patch release to fix an issue in Prisma client.

Fix in Prisma Client

swc-project/swc (@​swc/core)

v1.11.29

Compare Source

Bug Fixes
Features
Miscellaneous Tasks
Performance
Refactor
Build

v1.11.24

Compare Source

v1.11.22

Compare Source

Bug Fixes
Features

  • (bindings/core) Enhance existing parse function to accept both string and buffer types(#​10371) (c9a2afc)

  • (css/prefixer) Fix default implementation (#​10351) (34f4e41)

Miscellaneous Tasks
Performance
Refactor
Testing

v1.11.21

Compare Source

Bug Fixes
Miscellaneous Tasks
Performance

v1.11.20

Compare Source

Bug Fixes

Related issue:

Features
Miscellaneous Tasks
Performance
Testing

v1.11.18

Compare Source

Bug Fixes
Features
Refactor
Testing

v1.11.16

Compare Source

Miscellaneous Tasks

v1.11.15

[C

Configuration

📅 Schedule: Branch creation - "before 6am" in timezone Asia/Jakarta, Automerge - At any time (no schedule defined).

🚦 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.

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 22a4536 to e7ed1a8 Compare July 9, 2024 20:23
@renovate renovate bot changed the title chore(deps): update all non-major dependencies fix(deps): update all non-major dependencies Jul 9, 2024
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from ce73177 to 48e8af4 Compare July 16, 2024 21:43
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from fbc775a to 34049f3 Compare July 24, 2024 08:01
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 4089ad8 to 5a3ee29 Compare July 31, 2024 22:21
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 5a63728 to befaf15 Compare August 8, 2024 15:05
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 5cec7d0 to ce2260f Compare August 14, 2024 10:00
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 0228b7e to 6535dd4 Compare April 29, 2025 18:22
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 12 times, most recently from e3378d8 to 096b3d5 Compare May 8, 2025 14:19
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from e90384a to 75593ab Compare May 19, 2025 05:38
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from e6da661 to 89b1a26 Compare May 21, 2025 18:59
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 7520a86 to 17b61b0 Compare May 31, 2025 00:23
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 17b61b0 to fdb451d Compare June 4, 2025 07:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
meta: dependencies
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants