fix(deps): update all non-major dependencies by renovate[bot] · Pull Request #231 · NezuChan/utilities

renovate · 2024-06-29T18:51:55Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
@prisma/client (source)	`^5.16.1` → `^5.22.0`
@swc/cli	`^0.3.14` → `^0.8.1`
@swc/core (source)	`^1.6.5` → `^1.15.33`
@types/amqplib (source)	`^0.10.5` → `^0.10.8`
@types/node (source)	`^20.14.9` → `^20.19.39`
amqp-connection-manager	`^4.1.14` → `^4.1.15`
amqplib (source)	`^0.10.4` → `^0.10.9`
drizzle-kit (source)	`^0.22.7` → `^0.31.10`
drizzle-orm (source)	`^0.31.2` → `^0.45.2`
ioredis	`^5.4.1` → `^5.10.1`
lerna (source)	`^8.1.5` → `^8.2.4`
prisma (source)	`^5.16.1` → `^5.22.0`
rimraf	`^5.0.7` → `^5.0.10`

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

removing @unique in schema.prisma does not generate SQL to do so

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

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

Make sure that you have the latest version of prisma and @prisma/client installed:
```
npm install -D prisma@latest
npm install @&#8203;prisma/client@latest
```

Enable the typedSql Preview feature in your Prisma Schema.

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

Create a sql subdirectory of your prisma directory.
```
mkdir -p prisma/sql
```
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
```

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

   import { PrismaClient } from '@&#8203;prisma/client'
   import { getUsersWithPosts } from '@&#8203;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 prisma/prisma-engines#4970 and #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

#23742 fixes Prisma Client not supporting deeply nested some clauses when the relationJoins Preview feature was enabled.

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 @&#8203;id @&#8203;default(uuid()) // defaults to 4
  name String
}

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

model User {
  id   String @&#8203;id @&#8203;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

Support UUID v7

Language tools (e.g. VS Code)

Support fetching references for a model

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

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.

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.

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

Remove or change This is the 10th instance of Prisma Client being started. Make sure this is intentional. warning

Prisma

Prisma generate option --allow-no-models doesn't work.

Language tools (e.g. VS Code)

LSP Rename incorrectly maps field name and appends character

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

nextjs app deployed to vercel edge can't import prisma WASM module

swc-project/swc (@swc/core)

`v1.15.33`

Compare Source

Bug Fixes

(ci) Update rand lockfile entries (#11827) (7988966)
(es/minifier) Fold unary bool nullish coalescing (#11826) (e39ae3d)
(es/minifier) Preserve for-init sequence order (#11837) (16a56d0)
(es/parser) Parse empty Flow exact object type (#11836) (3d18a26)

Features

Move swc ast explorer into workspace (#11831) (02a8f81)

`v1.15.32`

Compare Source

Bug Fixes

(es/flow) Fix Flow type-only modules in script transforms (#11817) (be38316)
(es/flow) Avoid restoring module context when flow syntax is enabled (#11819) (3ed7243)
(es/minifier) Preserve frozen spread registry keys (#11825) (347181c)
(es/parser) Align Flow generic arrow JSX disambiguation (#11821) (28a7fad)

Features

(es) Add jsc.preserveSymlinks to swc::Options (#11813) (fe38342)

`v1.15.30`

Compare Source

Bug Fixes

(deploy) Fix musl binding test workflow (#11804) (c30a522)
(deploy) Build package ts before Linux GNU binding tests (#11806) (a3d3ef3)
(es/jsx) Preserve quoted JSX attribute newlines (#11796) (9fe56c8)
(es/minifier) Support full ES version parsing in minify (#11800) (af1f08f)
(es/module) Add opt-in symlink-preserving resolver (#11801) (6028240)
(es/parser) Allow return type annotation on Flow constructors (#11790) (d66b29c)
(es/parser) Support Flow anonymous keyof indexers (#11792) (452c4e5)
(es/parser) Add Flow strip RN and RNW regression corpus (#11799) (23a9109)

Documentation

Require PR template for pull requests (#11793) (3a1084a)

Features

(es/minify) Support extracting comments (#11798) (5986411)

`v1.15.26`

Compare Source

`v1.15.24`

Compare Source

`v1.15.21`

Compare Source

`v1.15.18`

Compare Source

`v1.15.17`

Compare Source

`v1.15.13`

Compare Source

`v1.15.11`

Compare Source

`v1.15.10`

Compare Source

`v1.15.8`

Compare Source

`v1.15.7`

Compare Source

`v1.15.6`

Compare Source

`v1.15.5`

Compare Source

`v1.15.4`

Compare Source

`v1.15.3`

Compare Source

`v1.15.2`

Compare Source

`v1.15.1`

Compare Source

`v1.15.0`

Compare Source

`v1.14.0`

Compare Source

`v1.13.21`

Compare Source

`v1.13.20`

Compare Source

`v1.13.19`

Compare Source

`v1.13.5`

Compare Source

`v1.13.4`

Compare Source

`v1.13.3`

Compare Source

`v1.13.2`

Compare Source

`v1.13.1`

Compare Source

`v1.13.0`

Compare Source

`v1.12.14`

Compare Source

`v1.12.11`

Compare Source

`v1.12.9`

Compare Source

`v1.12.7`

Compare Source

`v1.12.6`

Compare Source

`v1.12.5`

Compare Source

`v1.12.4`

Compare Source

`v1.12.3`

Compare Source

`v1.12.2`

Compare Source

`v1.12.1`

Compare Source

`v1.12.0`

Compare Source

`v1.11.31`

Compare Source

`v1.11.29`

Compare Source

`v1.11.24`

Compare Source

`v1.11.22`

Compare Source

`v1.11.21`

Compare Source

`v1.11.20`

Compare Source

`v1.11.18`

Compare Source

`v1.11.16`

Compare Source

`v1.11.15`

Compare Source

`v1.11.13`

Compare Source

`v1.11.12`

Compare Source

`v1.11.11`

Compare Source

`v1.11.10`

Compare Source

`v1.11.9`

Compare Source

`v1.11.8`

Compare Source

`v1.11.7`

Compare Source

`v1.11.6`

Compare Source

`v1.11.5`

Compare Source

`v1.11.4`

Compare Source

`v1.11.1`

Compare Source

`v1.10.18`

Compare Source

`v1.10.17`

Compare Source

`v1.10.16`

Compare Source

`v1.10.15`

Compare Source

`v1.10.14`

Compare Source

`v1.10.12`

Compare Source

`v1.10.11`

Compare Source

`v1.10.9`

Compare Source

`v1.10.8`

Compare Source

`v1.10.7`

Compare Source

`v1.10.6`

Compare Source

`v1.10.4`

Compare Source

`v1.10.3`

Compare Source

`v1.10.2`

Compare Source

`v1.10.1`

Compare Source

`v1.10.0`

Compare Source

`v1.9.3`

Compare Source

`v1.9.2`

Compare Source

`v1.9.1`

Compare Source

`v1.9.0`

Compare Source

`v1.8.0`

Compare Source

`v1.7.42`

Compare Source

`v1.7.40`

Compare Source

`v1.7.39`

Compare Source

`v1.7.36`

Compare Source

`v1.7.35`

Compare Source

`v1.7.28`

Compare Source

`v1.7.26`

Compare Source

`v1.7.25`

Compare Source

`v1.7.24`

Compare Source

`v1.7.23`

Compare Source

`v1.7.22`

Compare Source

`v1.7.21`

Compare Source

`v1.7.19`

Compare Source

`v1.7.18`

Compare Source

`v1.7.14`

Compare Source

`v1.7.12`

Compare Source

`v1.7.11`

Compare Source

`v1.7.10`

Compare Source

`v1.7.9`

Compare Source

`v1.7.6`

Compare Source

`v1.7.5`

Compare Source

`v1.7.4`

Compare Source

`v1.7.3`

Compare Source

`v1.7.2`

Compare Source

`v1.7.1`

Compare Source

`v1.7.0`

Compare Source

`v1.6.13`

Compare Source

`v1.6.12`

Compare Source

`v1.6.7`

Compare Source

`v1.6.6`

Compare Source

jwalton/node-amqp-connection-manager (amqp-connection-manager)

`v4.1.15`

Compare Source

ci: Install docker-compose.
fix: Fix types to work with latest amqplib.

Full Changelog: jwalton/node-amqp-connection-manager@v4.1.14...v4.1.15

amqp-node/amqplib (amqplib)

`v0.10.9`

Compare Source

Add support for IPv6 urls

`v0.10.8`

Compare Source

Updated README

`v0.10.7`

Compare Source

Remove bitsyntax dependency - See #785. Thanks @ikenfin
Stop checking if frame max is exceeded when parsing frames - See #784. Thanks @ohroy

`v0.10.6`

Compare Source

Replace references to the old squaremo/amqp.name repo with ones to amqp-node/amqplib
Use a frame_max of 131072 by default for RabbitMQ 4.1.0 compatibility

`v0.10.5`

Compare Source

git log v0.10.4..v0.10.5

Removed readable stream - See #729
Added support for unsigned integers - See #773
Committed protocol definitions - See 0a87ee4

drizzle-team/drizzle-orm (drizzle-kit)

`v0.31.10`

Compare Source

Updated to hanji@0.0.8 - native bun stringWidth, stripANSI support, errors for non-TTY environments
We've migrated away from esbuild-register to tsx loader, it will now allow to use drizzle-kit seamlessly with both ESM and CJS modules
We've also added native Bun and Deno launch support, which will not trigger tsx loader and utilise native bun and deno imports capabilities and faster startup times

`v0.31.9`

Compare Source

drizzle-kit api improvements for D1 connections

`v0.31.8`

Compare Source

Bug fixes

Fixed algorythm => algorithm typo.
Fixed external dependencies in build configuration.

`v0.31.7`: drizzle-kit@0.31.7

Compare Source

Bug fixes

[BUG]: Drizzle Kit push to Postgres 18 produces unecessary DROP SQL when the schema was NOT changed

`v0.31.6`

Compare Source

Bug fixes

[BUG]: Importing drizzle-kit/api fails in ESM modules

`v0.31.5`

Compare Source

Add casing support to studio configuration and related functions

`v0.31.4`

Compare Source

Fixed halfvec, bit and sparsevec type generation bug in drizzle-kit

`v0.31.3`

Compare Source

Internal changes to Studio context. Added databaseName and packageName properties for Studio

`v0.31.2`

Compare Source

Bug fixes

Fixed relations extraction to not interfere with Drizzle Studio.

`v0.31.1`

Compare Source

Fixed `drizzle-kit pull` bugs when using Gel extensions.

Because Gel extensions create schema names containing :: (for example, ext::auth), Drizzle previously handled these names incorrectly. Starting with this release, you can use Gel extensions without any problems. Here’s what you should do:

Enable extensions schemas in drizzle.config.ts

import  { defineConfig } from "drizzle-kit";

export default defineConfig({
  dialect: 'gel',
  schemaFilter: ['ext::auth', 'public']
});

Run drizzle-kit pull
Done!

`v0.31.0`

Compare Source

Features and improvements

Enum DDL improvements

For situations where you drop an enum value or reorder values in an enum, there is no native way to do this in PostgreSQL. To handle these cases, drizzle-kit used to:

Change the column data types from the enum to text
Drop the old enum
Add the new enum
Change the column data types back to the new enum

However, there were a few scenarios that weren’t covered: PostgreSQL wasn’t updating default expressions for columns when their data types changed

Therefore, for cases where you either change a column’s data type from an enum to some other type, drop an enum value, or reorder enum values, we now do the following:

Change the column data types from the enum to text
Set the default using the ::text expression
Drop the old enum
Add the new enum
Change the column data types back to the new enum
Set the default using the ::<new_enum> expression

`esbuild` version upgrade

For drizzle-kit we upgraded the version to latest (0.25.2), thanks @paulmarsicloud

Bug fixes

`v0.30.6`

Compare Source

Bug fixes

[BUG]: d1 push locally is not working - thanks @mabels and @RomanNabukhotnyi
[BUG] Cloudflare D1: drizzle-kit push is not working (error 7500 SQLITE_AUTH) - thanks @mabels and @RomanNabukhotnyi

`v0.30.5`

Compare Source

New Features

Added `Gel` dialect support and `gel-js` client support

Drizzle is getting a new Gel dialect with its own types and Gel-specific logic. In this first iteration, almost all query-building features have been copied from the PostgreSQL dialect since Gel is fully PostgreSQL-compatible. The only change in this iteration is the data types. The Gel dialect has a different set of available data types, and all mappings for these types have been designed to avoid any extra conversions on Drizzle's side. This means you will insert and select exactly the same data as supported by the Gel protocol.

Drizzle + Gel integration will work only through drizzle-kit pull. Drizzle won't support generate, migrate, or push features in this case. Instead, drizzle-kit is used solely to pull the Drizzle schema from the Gel database, which can then be used in your drizzle-orm queries.

The Gel + Drizzle workflow:

Use the gel CLI to manage your schema.
Use the gel CLI to generate and apply migrations to the database.
Use drizzle-kit to pull the Gel database schema into a Drizzle schema.
Use drizzle-orm with gel-js to query the Gel database.

On the drizzle-kit side you can now use dialect: "gel"

// drizzle.config.ts
import { defineConfig } from 'drizzle-kit';

export default defineConfig({
  dialect: 'gel',
});

For a complete Get Started tutorial you can use our new guides:

[G

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (in timezone Asia/Jakarta)

Branch creation
- "before 6am"
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 Bot added the meta: dependencies label Jun 29, 2024

renovate Bot force-pushed the renovate/all-minor-patch branch from 22a4536 to e7ed1a8 Compare July 9, 2024 20:23

renovate Bot changed the title ~~chore(deps): update all non-major dependencies~~ fix(deps): update all non-major dependencies Jul 9, 2024

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 Bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from fbc775a to 34049f3 Compare July 24, 2024 08:01

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 Bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 5a63728 to befaf15 Compare August 8, 2024 15:05

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 Bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 8fb7e52 to 5d506f6 Compare September 8, 2024 10:31

renovate Bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 877d789 to 8971b60 Compare September 11, 2024 12:14

renovate Bot force-pushed the renovate/all-minor-patch branch 8 times, most recently from 0504416 to 5151dea Compare September 27, 2024 20:02

renovate Bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 179ab3c to 4369f1c Compare October 10, 2024 11:42

renovate Bot force-pushed the renovate/all-minor-patch branch 9 times, most recently from 5c2cec7 to 2412772 Compare October 22, 2024 03:07

fix(deps): update all non-major dependencies

1bc1ff6

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

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

fix(deps): update all non-major dependencies#231
renovate[bot] wants to merge 1 commit intomainfrom
renovate/all-minor-patch

renovate Bot commented Jun 29, 2024 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

renovate Bot commented Jun 29, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Highlights

Further Tracing Improvements

Metrics bug fix

Connection Pool Timeout fix

Join us

Fixes and improvements

Prisma Migrate

Prisma

Credits

Highlights

Better support for tracing in MongoDB

WebAssembly engine size decrease for edge functions

Fixes and improvements

Prisma Engines

Credits

Highlights

strictUndefinedChecks in Preview

typedSql bug fix

Fixes and improvements

Prisma

Prisma Engines

Credits

What's Changed

Highlights

Introducing TypedSQL

Bug fixes

Driver adapters and D1

Joins

MongoDB

Join us

Credits

Highlights

Native support for UUIDv7

Bug squashing

Fixes and improvements

Prisma

Language tools (e.g. VS Code)

Share your feedback about Prisma ORM

Credits

Highlights

VSCode extension improvements

QueryRaw performance improvements

Fixes and improvements

Prisma Client

Prisma

Language tools (e.g. VS Code)

Credits

Fix in Prisma Client

Bug Fixes

Features

Bug Fixes

Features

Bug Fixes

Documentation

Features

renovate Bot commented Jun 29, 2024 •

edited

Loading

`strictUndefinedChecks` in Preview

`typedSql` bug fix