chore(deps): update all non-major dependencies #4

renovate · 2024-02-04T19:03:49Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@commitlint/cli (source)	`19.0.0` -> `19.0.3`
@commitlint/config-conventional (source)	`19.0.0` -> `19.0.3`
@prisma/client (source)	`5.5.2` -> `5.10.2`
@types/node (source)	`20.8.9` -> `20.11.22`
@types/react (source)	`18.2.33` -> `18.2.60`
@types/react-dom (source)	`18.2.14` -> `18.2.19`
@typescript-eslint/eslint-plugin (source)	`7.0.1` -> `7.1.0`
@typescript-eslint/parser (source)	`7.0.1` -> `7.1.0`
autoprefixer	`10.4.16` -> `10.4.17`
clsx	`2.0.0` -> `2.1.0`
eslint (source)	`8.56.0` -> `8.57.0`
eslint-config-next (source)	`14.0.0` -> `14.1.0`
eslint-plugin-import	`2.29.0` -> `2.29.1`
lru-cache	`10.0.2` -> `10.2.0`
next (source)	`14.0.0` -> `14.1.0`
postcss (source)	`8.4.31` -> `8.4.35`
prettier (source)	`3.0.2` -> `3.2.5`
prettier-plugin-tailwindcss	`0.5.6` -> `0.5.11`
prisma (source)	`5.5.2` -> `5.10.2`
sass	`1.69.5` -> `1.71.1`
tailwindcss (source)	`3.3.5` -> `3.4.1`
typescript (source)	`5.2.2` -> `5.3.3`

Release Notes

conventional-changelog/commitlint (@commitlint/cli)

`v19.0.3`

Compare Source

Note: Version bump only for package @commitlint/cli

`v19.0.2`

Compare Source

Note: Version bump only for package @commitlint/cli

`v19.0.1`

Compare Source

Bug Fixes

drop resolve-from, resolve-global and import-fresh, resolve global packages correctly (#3939) (8793c63), closes #3938

conventional-changelog/commitlint (@commitlint/config-conventional)

`v19.0.3`

Compare Source

Note: Version bump only for package @commitlint/config-conventional

prisma/prisma (@prisma/client)

`v5.10.2`

Compare Source

Today, we are issuing the 5.10.2 patch release.

Fix in Prisma CLI

Invalid character error persists on 5.10.1 in Prisma Studio

`v5.10.1`

Compare Source

Today, we are issuing the 5.10.1 patch release.

Fix in Prisma Client / Prisma CLI

Error: Invalid character when schema.prisma includes Chinese/Non-ASCII characters in a comment

`v5.10.0`

Compare Source

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

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

Highlights

Optimized relation queries in MySQL (Preview)

This release brings the optimizations for relation queries from the previous releases to MySQL as well! This means that by enabling the relationJoins Preview feature with the mysql database provider, you now also get access to the relationLoadStrategy option in relation queries that let you choose whether you want to merged relations on the application- or database-level.

If you enable the relationJoins Preview feature, you can choose between the join and query options:

join (default): Sends a single query to the database and joins the data on the database-level.
query: Sends multiple queries to the database and joins the data on the application-level.

To get started, enable the Preview feature in your Prisma schema:

// schema.prisma
generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["relationJoins"]
}

Be sure to re-generate Prisma Client afterwards:

npx prisma generate

And finally, specify the relation loading strategy for your relation query via the relationLoadStrategy option as follows:

await prisma.user.findMany({
  relationLoadStrategy: 'join', // or 'query' 
  include: {
    posts: true,
  },
})

Note that in the example above, the relationLoadStrategy could be omitted altogether because join is used as the default value.

A few notes about relationLoadStrategy support on MySQL:

relationLoadStrategy is supported for MySQL v8.0.14 and higher. MariaDB is not supported.
Prisma ORM uses correlated sub-queries for MySQL (as opposed to LATERAL JOINs which are used on PostgreSQL).

Configure transaction options in the `PrismaClient` constructor

This feature enables you to configure the following transaction options on a global level via the PrismaClient constructor:

isolationLevel: Sets the transaction isolation level. By default, this is set to the value currently configured in your database.
timeout: The maximum amount of time the interactive transaction can run before being canceled and rolled back. The default value is 5 seconds.
maxWait: The maximum amount of time Prisma Client will wait to acquire a transaction from the database. The default value is 2 seconds.

Here is an example of how you can set this value globally for all transactions:

const prisma = new PrismaClient({
  transactionOptions: {
    isolationLevel: 'ReadCommitted',
    timeout: 1_000, // 1 sec
    maxWait: 2_000  // 2 sec
  }
})

Thanks a lot to our fantastic community member @tockn, who took the initiative to implement this feature in Prisma ORM 🎉

Note that you can still override the global values by setting them on a particular transaction.

New `P2037` code for “Too many database connections opened” errors

We introduced a new error code for “Too many database connections opened” errors: P2037. You can find all error codes in our documentation.

Access the Prisma Data Platform via Prisma CLI

Now available in Early Access, you can manage your workspace and configure Prisma Accelerate and Prisma Pulse directly from the terminal.

Visit our docs to learn more about the integration and try it out for yourself!

Fixes and improvements

Prisma Client

`v5.9.1`

Compare Source

Today, we are issuing the 5.9.1 patch release.

Fixes in Prisma Client

In 5.9.0 we have changed our conditional exports in @prisma/client. This resulted in broken types for TypesScript users using certain combinations of module/moduleResolution settings. Additionally, it also caused a regression for Next.js users which have encountered invalid error messages from our side.

You can now try out 5.9.1 and let us know if you find a bug at https://pris.ly/prisma-prisma-bug-report

Note: many issues are duplicates.

`v5.9.0`

Compare Source

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

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

This release brings a number of small improvements as we continue our work on larger features which you will hear more about in the coming weeks:

Improve the performance of relation queries by introducing JOINs (see last release).
Support deployment to edge functions (already available in Early Access, you can apply for trying it out by taking our survey).

Highlights

Optimized result sets for more efficient queries

We continue our efforts of the performance of Prisma Client queries. In 5.1.0, we introduced the RETURNING keyword for several queries on PostrgeSQL and CockroachDB. We now expanded the use of RETURNING to SQLite and a broader range of queries for existing databases (e.g. delete on PostgreSQL and MongoDB). You can learn more about the optimizations of the result sets in these PRs:

SQL Server: Return proper error for unreachable database

When trying migrate/introspect a SQL server instance that’s unreachable, Prisma ORM now returns the correct P1001 error instead of failing without an error. Learn more in this PR: SQL Server: Migrate/Introspection engine doesn't return P1001 error for unreachable url.

Fixes and improvements

Prisma Client

Prisma Migrate

Language tools (e.g. VS Code)

Extension wrongfully suggests Json as a valid type completion on Sqlite

Company news

Test edge functions support in Early Access

Today, the only way how to use Prisma ORM in edge functions (e.g. Cloudflare Workers or Vercel Edge Functions) is by using Prisma Accelerate. However, we are actively working on making Prisma ORM compatible with edge functions natively as well. If you want to become an early tester, you can apply for the private Early Accessing program by taking this survey.

We Transitioned Prisma Accelerate to IPv6 Without Anyone Noticing

Last year, AWS announced the decision to begin charging for IPv4 addresses beginning in February 2024. This move had a major impact on Prisma Accelerate, prompting us to go all-in on IPv6. Learn more in this technical deep dive into how we approached our IPv6 migration, lessons learned, and the outcome for users of Prisma Accelerate.

Credits

Huge thanks to @laplab, @Druue, @anuraaga, @onichandame, @LucianBuzzo, @RobertCraigie, @almeidx, @victorgdb, @tinola, @sampolahtinen, @AikoRamalho, @petradonka for helping!

`v5.8.1`

Compare Source

Today, we are issuing the 5.8.1 patch release.

Fix in Prisma Client

Parallel execution with Promise.all causes P2024 error in version 5.8.0 due to connection limit.

`v5.8.0`

Compare Source

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

Highlights

Happy New Year from your friends at Prisma! 🎊

In the last 4 weeks, we resolved some bugs on the ORM and made some progress on some exciting features that we’re not yet ready to announce. Stay tuned for the upcoming releases, in which we’ll be announcing new features. 😉

`relationJoins` improvements: Relation loading strategy per query (Preview)

In version 5.7.0, we released relationJoins into Preview. The relationJoins feature enables support for JOINs for relation queries.

This release adds support for the ability to specify the strategy used to fetch relational data per query when the Preview feature is enabled. This will enable you to choose the most efficient strategy for fetching relation data depending on your use case.

You can now load relation data using either of the following strategies:

join — uses JOINs to fetch relation data
query — uses sub-queries to fetch relation data

When the relationJoins Preview feature is enabled, by default, the relation fetching strategy used is join. You can override the default behavior by using the relationLoadStrategy query option.

To get started, enable the Preview feature:

// schema.prisma
generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["relationJoins"]
}

… and specify the relation loading strategy for your query as follows:

await prisma.user.findMany({
  relationLoadStrategy: 'query',
  include: {
    posts: true,
  },
})

Try it out and share your feedback and create a bug report if you encounter any issues.

Survey: Edge functions support

We’re working on bringing Edge function support to Prisma ORM and we would appreciate your input by submitting a response to our survey. By filling out the survey, you will be considered for our Early Access cohort as soon as we have something for you to try out.

Fixes and improvements

Prisma Client

Prisma Migrate

Prisma Migrate errors with Environment is non-interactive when VERCEL env var is defined

Language tools (e.g. VS Code)

Credits

Huge thanks to @anuraaga, @onichandame, @LucianBuzzo, @RobertCraigie, @fqazi, @KhooHaoYit, @alencardc, @Oreilles, @tinola, @AikoRamalho, @luxaritas for helping!

Company news

🎉 A billion queries and counting: Prisma Accelerate

Prisma Accelerate, our global database cache has served over 1 billion queries since its General Availability launch.

We’d like to give a shoutout to our team and everyone who’s been with us on this journey. Stay tuned for some exciting products and features in the pipeline for 2024!

🔮 Prisma ORM Ecosystem

Are you building a cool tool, extension, generator, CLI tool or anything else, for Prisma ORM? Let us know.

We would like to learn about it and feature it on our Ecosystem page.

💼 We’re hiring

If you're interested in joining our growing team to help empower developers to build data-intensive applications, Prisma is the place for you. Check out our Careers page for open positions.

`v5.7.1`

Compare Source

Today, we are issuing the 5.7.1 patch release.

This patch fixes multiple small problems in our relationJoins preview feature. If you ran into problems when testing relationJoins before, please give it another go with 5.7.1 and share your feedback or create a bug report if you encounter any issues.

Fixes in Prisma Client

`v5.7.0`

Compare Source

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

Highlights

✨ In this release, we improved the SQL queries Prisma Client generates for you with two new Preview features, the driver adapters, and support for the database drivers we currently support. 5.7.0 will be the last release of the year. Stay tuned for the next one in January! ✨

Preview support for `JOIN`s for relation queries for PostgreSQL and CockroachDB

We’re excited to announce Preview support for JOINs in Prisma Client when querying relations. Support for JOINs has been a long-standing feature request, and this release adds support for PostgreSQL and CockroachDB. The upcoming releases will expand support for other databases Prisma supports.

To get started using JOINs, enable the Preview feature in your Prisma schema:

// schema.prisma
generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["relationJoins"]
}

Run prisma generate to regenerate Prisma Client and enable the Preview feature.

Prisma Client will use a JOIN in your query to fetch relation data for a majority of the cases.

Example queries

1-1 relation queries example

Prisma Client query

await prisma.user.findUnique({
	where: {
		id: 1
	},
	include: {
		profile: true
	}
})

SQL

SELECT
	"t1"."id",
	"t1"."name",
	"User_profile"."__prisma_data__" AS "profile"
FROM
	"public"."User" AS "t1"
	LEFT JOIN LATERAL (
		SELECT
			COALESCE(JSON_AGG("__prisma_data__"), '[]') AS "__prisma_data__"
		FROM
			(
				SELECT
					"t4"."__prisma_data__"
				FROM
					(
						SELECT
							JSON_BUILD_OBJECT(
								'id',
								"t3"."id",
								'bio',
								"t3"."bio",
								'userId',
								"t3"."userId"
							) AS "__prisma_data__"
						FROM
							(
								SELECT
									"t2".*
								FROM
									"public"."Profile" AS "t2"
								WHERE
									"t1"."id" = "t2"."userId"
							) AS "t3"
					) AS "t4"
			) AS "t5"
	) AS "User_profile" ON TRUE
WHERE "t1"."id" = $1
LIMIT $2

1-m relation queries example

Prisma Client query

await prisma.user.findUnique({
	where: {
		id: 1
	},
	include: {
		posts: true
	}
})

SQL

SELECT
	"t1"."id",
	"t1"."name",
	"User_posts"."__prisma_data__" AS "posts"
FROM
	"public"."User" AS "t1"
	LEFT JOIN LATERAL (
		SELECT
			COALESCE(JSON_AGG("__prisma_data__"), '[]') AS "__prisma_data__"
		FROM
			(
				SELECT
					"t4"."__prisma_data__"
				FROM
					(
						SELECT
							JSON_BUILD_OBJECT(
								'id',
								"t3"."id",
								'title',
								"t3"."title",
								'content',
								"t3"."content",
								'published',
								"t3"."published",
								'authorId',
								"t3"."authorId"
							) AS "__prisma_data__"
						FROM
							(
								SELECT
									"t2".*
								FROM
									"public"."Post" AS "t2"
								WHERE
									"t1"."id" = "t2"."authorId"
									/* root select */
							) AS "t3"
							/* inner select */
					) AS "t4"
					/* middle select */
			) AS "t5"
			/* outer select */
	) AS "User_posts" ON TRUE
WHERE "t1"."id" = $1
LIMIT $2

m-n relation queries example

Prisma Client query

await prisma.post.findUnique({
	where: {
		id: 1
	},
	include: {
		tags: true
	}
})

SQL

SELECT
	"t1"."id",
	"t1"."title",
	"t1"."content",
	"t1"."published",
	"t1"."authorId",
	"Post_tags_m2m"."__prisma_data__" AS "tags"
FROM
	"public"."Post" AS "t1"
	LEFT JOIN LATERAL (
		SELECT
			COALESCE(JSON_AGG("__prisma_data__"), '[]') AS "__prisma_data__"
		FROM
			(
				SELECT
					"Post_tags"."__prisma_data__"
				FROM
					"public"."_PostToTag" AS "t2"
					LEFT JOIN LATERAL (
						SELECT
							JSON_BUILD_OBJECT('id', "t4"."id", 'name', "t4"."name") AS "__prisma_data__",
							"t4"."id"
						FROM
							(
								SELECT
									"t3".*
								FROM
									"public"."Tag" AS "t3"
								WHERE
									"t2"."B" = "t3"."id"
									/* root select */
							) AS "t4"
					) AS "Post_tags" ON TRUE
				WHERE
					"t2"."A" = "t1"."id"
			) AS "Post_tags_m2m_1"
	) AS "Post_tags_m2m" ON TRUE
WHERE "t1"."id" = $1
LIMIT $2

Share your feedback and create a bug report if you encounter any issues.

Prisma’s `distinct` option now uses SQL queries (Preview)

From this release, Prisma Client’s distinct option now uses the native SQL DISTINCT ON for unordered queries with PostgreSQL and CockroachDB. The upcoming releases will expand support for the other databases that Prisma supports.

Prisma Client already supports querying for distinct records. However, Prisma Client took care of the post-processing for distinct records in memory.

To get started, enable the Preview feature in your Prisma schema:

// schema.prisma
generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["nativeDistinct"]
}

Regenerate your Prisma Client to get started using the Preview feature.

Given the following Prisma Client query:

await prisma.user.findMany({
    distinct: ['role'],
    select: {
      role: true,
    },
})

Before 5.7.0

Previously, Prisma Client handled the post-processing to select distinct records in-memory. Therefore, the following query was generated and executed against your database:

SELECT
	"public"."User"."id",
	"public"."User"."role"::text
FROM
	"public"."User"
WHERE
	1 = 1 OFFSET $1

After 5.7.0

SELECT DISTINCT ON ("public"."User"."role")
	"public"."User"."id",
	"public"."User"."role"::text
FROM
	"public"."User"
WHERE
	1 = 1 OFFSET $1

Share your feedback and create a bug report if you encounter any issues.

Improved support for Netlify using Node.js v20

In this release, we improved Prisma support when deploying to Netlify on Node.js v20. Previously, the Prisma Client could not resolve the location of the Query Engine after deploying to Netlify when using Node.js v20. If you run into this issue, we recommend updating to Prisma v5.7.0.

We recommend giving this comment on GitHub a read if you are not yet able to upgrade Prisma, to learn how to get around the error.

Fixes and improvements

Prisma Client

Company news

💼 We’re hiring!

If you're interested in joining our growing team to help empower developers to build data-intensive applications, Prisma is the place for you.

We're hiring for the following roles:

`v5.6.0`

Compare Source

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

Highlights

Driver adapters improvements (Preview)

In version 5.4.0, we released driverAdapters into Preview. The driverAdapters feature enables Prisma Client to access your database using JavaScript or Serverless database drivers.

In this release, we fixed many bugs for the existing driver adapters. We appreciate all the community feedback that has helped us improve this feature!

PlanetScale serverless driver adapter improvements

This release also introduces a small breaking change to the @prisma/adapter-planetscale package to improve its stability and performance. The serverless driver adapter will now use a connection pool instead of a single connection from PlanetScale’s serverless driver.

In case you’re using the @prisma/adapter-planetscale, update your Prisma Client instance with the following:

-import { connect } from '@&#8203;planetscale/database'
+import { Client } from '@&#8203;planetscale/database'
import { PrismaPlanetScale } from '@&#8203;prisma/adapter-planetscale'
import { PrismaClient } from '@&#8203;prisma/client'
import { fetch as undiciFetch } from 'undici';

-const connection = connect({ url: connectionString, fetch: undiciFetch })
+const client = new Client({ url: connectionString, fetch: undiciFetch })

-const adapter = new PrismaPlanetScale(connection)
+const adapter = new PrismaPlanetScale(client)

const prisma = new PrismaClient({ adapter })

Request for feedback

We encourage you to try out the driver adapters and share your feedback to help us move it to General Availability in either of the following GitHub discussions:

Refer to our docs to learn more about driver adapters.

New `prisma debug` command

This release introduces a new command: prisma debug. The command provides debugging information such as environment variables that Prisma Client, Prisma Migrate, Prisma CLI, and Prisma Studio use. The command is also useful when creating a bug report as the information complements the output of the prisma -v command.

You can learn more about the command in our docs.

Read replicas extension improvements

We also released version 0.3.0 of the @prisma/extension-read-replicas package that contains the following improvements:

A new $replica() method that explicitly enables you to use a replica for your query.

For example, by default, the queryRaw and executeRaw methods are forwarded to the primary database, as they could try to write to the database. You can use the $replica() method with either of the *Raw methods to explicitly execute your query against a replica instead of your primary database.
Validation for when there’s an empty list of replicas.
Webpack bundling fixes

We want to thank you, our community members, for your contributions! 🙏

You can find additional information on the changes in the extension’s release. You can learn more about the extension in the announcement blog post.

Package provenance

npm has introduced provenance statements to improve supply-chain security and transparency of packages. This allows developers to verify where and how packages are built.

Starting with the 5.6.0 release, all npm packages for Prisma ORM will be published with provenance statements. If you maintain a Prisma Client extension or generator, we encourage you to enable provenance statements when publishing to npm.

Fixes and improvements

Prisma Migrate

Prisma Client

Prisma CLI

prisma debug

Credits

Huge thanks to @onichandame, @LucianBuzzo, @RobertCraigie, @fqazi, @KhooHaoYit, @alencardc, @Oreilles, @christianledgard, @skyzh, @alula, @luxaritas, @Nasfame, @lukahartwig, @steebchen, @icanipa for helping!

Miscellaneous

Prisma Accelerate is now Generally Available

We're excited to share that Prisma Accelerate is now Generally Available. Prisma Accelerate is a global database cache that's available in over 280 locations and provides scalable connection pooling for serverless and edge applications.

Learn more in the announcement blog post. Sign up and try out Prisma Accelerate

💼 We’re hiring!

If you're interested in joining our growing team to help empower developers to build data-intensive applications, Prisma is the place for you.

We're hiring for an Engineering Manager: Prisma Data Platform.

typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)

`v7.1.0`

Compare Source

🚀 Features

eslint-plugin: add *-type-checked-only configs
eslint-plugin: [naming-convention] support the auto-accessor syntax
**eslint-plugin

Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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 has been generated by Mend Renovate. View repository job log here.

vercel · 2024-02-04T19:03:56Z

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
link	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 28, 2024 8:17pm

vercel bot deployed to Preview February 4, 2024 19:05 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 5a28dc0 to e42573e Compare February 5, 2024 07:17

vercel bot deployed to Preview February 5, 2024 07:18 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from e42573e to 2d0a017 Compare February 5, 2024 18:35

vercel bot deployed to Preview February 5, 2024 18:36 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 2d0a017 to d77c9fa Compare February 5, 2024 21:15

vercel bot deployed to Preview February 5, 2024 21:16 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from d77c9fa to 28f8d90 Compare February 6, 2024 10:33

vercel bot deployed to Preview February 6, 2024 10:35 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 28f8d90 to 96960ce Compare February 7, 2024 19:40

vercel bot deployed to Preview February 7, 2024 19:41 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 96960ce to 9240358 Compare February 8, 2024 23:14

vercel bot deployed to Preview February 8, 2024 23:15 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 9240358 to 9de98ff Compare February 15, 2024 12:39

vercel bot deployed to Preview February 15, 2024 12:40 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 9de98ff to ca9adb4 Compare February 15, 2024 18:50

vercel bot deployed to Preview February 15, 2024 18:51 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from ca9adb4 to 3bec360 Compare February 16, 2024 03:54

vercel bot deployed to Preview February 16, 2024 03:55 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 3bec360 to 6d802ea Compare February 17, 2024 10:08

vercel bot deployed to Preview February 17, 2024 10:09 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 6d802ea to cfff8be Compare February 20, 2024 01:21

vercel bot deployed to Preview February 20, 2024 01:22 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from cfff8be to 1962bad Compare February 20, 2024 15:29

vercel bot deployed to Preview February 20, 2024 15:30 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 1962bad to 64e9217 Compare February 20, 2024 19:40

vercel bot deployed to Preview February 20, 2024 19:41 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 64e9217 to 1023b5e Compare February 21, 2024 03:13

vercel bot deployed to Preview February 21, 2024 03:14 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 1023b5e to b5fcd30 Compare February 21, 2024 19:00

vercel bot deployed to Preview February 21, 2024 19:01 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from b5fcd30 to 7990b8e Compare February 22, 2024 23:06

vercel bot deployed to Preview February 22, 2024 23:07 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 7990b8e to a6021d7 Compare February 23, 2024 11:16

vercel bot deployed to Preview February 23, 2024 11:17 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from a6021d7 to 4be4cd8 Compare February 23, 2024 23:28

vercel bot deployed to Preview February 23, 2024 23:29 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 4be4cd8 to 4053096 Compare February 25, 2024 10:19

vercel bot deployed to Preview February 25, 2024 10:21 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 4053096 to 24261b3 Compare February 26, 2024 21:20

vercel bot deployed to Preview February 26, 2024 21:21 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 24261b3 to 317de9b Compare February 27, 2024 10:34

vercel bot deployed to Preview February 27, 2024 10:35 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 317de9b to 29dc083 Compare February 28, 2024 01:31

vercel bot deployed to Preview February 28, 2024 01:32 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 29dc083 to f57690b Compare February 28, 2024 15:22

renovate bot changed the title ~~fix(deps): update all non-major dependencies~~ chore(deps): update all non-major dependencies Feb 28, 2024

ccrsxx approved these changes Feb 28, 2024

View reviewed changes

renovate bot force-pushed the renovate/all-minor-patch branch from f57690b to 731d175 Compare February 28, 2024 15:24

vercel bot deployed to Preview February 28, 2024 15:27 View deployment

chore(deps): update all non-major dependencies

e90803c

renovate bot force-pushed the renovate/all-minor-patch branch from 731d175 to e90803c Compare February 28, 2024 20:16

vercel bot deployed to Preview February 28, 2024 20:17 View deployment

ccrsxx merged commit 3cf5833 into main Feb 29, 2024
5 checks passed

ccrsxx deleted the renovate/all-minor-patch branch February 29, 2024 09:10

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update all non-major dependencies #4

chore(deps): update all non-major dependencies #4

renovate bot commented Feb 4, 2024 •

edited

Loading

vercel bot commented Feb 4, 2024 •

edited

Loading

chore(deps): update all non-major dependencies #4

chore(deps): update all non-major dependencies #4

Conversation

renovate bot commented Feb 4, 2024 • edited Loading

Release Notes

Bug Fixes

Fix in Prisma CLI

Fix in Prisma Client / Prisma CLI

Highlights

Optimized relation queries in MySQL (Preview)

Configure transaction options in the PrismaClient constructor

New P2037 code for “Too many database connections opened” errors

Access the Prisma Data Platform via Prisma CLI

Fixes and improvements

Prisma Client

Fixes in Prisma Client

Highlights

Optimized result sets for more efficient queries

SQL Server: Return proper error for unreachable database

Fixes and improvements

Prisma Client

Prisma Migrate

Language tools (e.g. VS Code)

Company news

Test edge functions support in Early Access

We Transitioned Prisma Accelerate to IPv6 Without Anyone Noticing

Credits

Fix in Prisma Client

Highlights

relationJoins improvements: Relation loading strategy per query (Preview)

Survey: Edge functions support

Fixes and improvements

Prisma Client

Prisma Migrate

Language tools (e.g. VS Code)

Credits

Company news

🎉 A billion queries and counting: Prisma Accelerate

🔮 Prisma ORM Ecosystem

💼 We’re hiring

Fixes in Prisma Client

Highlights

Preview support for JOINs for relation queries for PostgreSQL and CockroachDB

Prisma’s distinct option now uses SQL queries (Preview)

Improved support for Netlify using Node.js v20

Fixes and improvements

Prisma Client

Prisma

Prisma Migrate

Credits

Company news

💼 We’re hiring!

Highlights

Driver adapters improvements (Preview)

PlanetScale serverless driver adapter improvements

Request for feedback

New prisma debug command

Read replicas extension improvements

Package provenance

Fixes and improvements

Prisma Migrate

Prisma Client

Prisma CLI

Credits

Miscellaneous

Prisma Accelerate is now Generally Available

💼 We’re hiring!

🚀 Features

Configuration

vercel bot commented Feb 4, 2024 • edited Loading

renovate bot commented Feb 4, 2024 •

edited

Loading

Configure transaction options in the `PrismaClient` constructor

New `P2037` code for “Too many database connections opened” errors

`relationJoins` improvements: Relation loading strategy per query (Preview)

Preview support for `JOIN`s for relation queries for PostgreSQL and CockroachDB

Prisma’s `distinct` option now uses SQL queries (Preview)

New `prisma debug` command

vercel bot commented Feb 4, 2024 •

edited

Loading