fix(deps): update external-major (major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@prisma/client (source)	^5.22.0 -> ^6.3.0
@types/react (source)	^18.3.18 -> ^19.0.8
is-ci	^3.0.1 -> ^4.1.0
jsdom	^25.0.1 -> ^26.0.0
prisma (source)	^5.22.0 -> ^6.3.0
react (source)	^18.3.1 -> ^19.0.0
react-dom (source)	^18.3.1 -> ^19.0.0
tailwind-merge	^2.6.0 -> ^3.0.1
tailwindcss (source)	^3.4.17 -> ^4.0.3
vitest (source)	^2.1.8 -> ^3.0.5

---

Release Notes

prisma/prisma (@​prisma/client)

v6.3.0

Compare Source

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

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

Highlights

A brand new Prisma Studio

In this release we've included several great improvements to Prisma Studio's developer experience. You can learn all about the changes we've made in our release blog post, but here's a short list:

Prisma Studio is back in the Console

Fans of Prisma Data Browser rejoice! The new Prisma Studio is now in the Prisma Console and is available for all PostgreSQL and MySQL databases.

A new model viewer

Previously, switching from model to model in Prisma Studio would require backing all the way out to the model view, then digging in again. With our new UI, it's easy to switch from model to model while keeping your place.

A new editing experience

If you're trying to edit a given field in a model, Prisma Studio made it quite easy. However, if you're trying to edit every field in a given row, it could get quite annoying to keep scrolling left to right. Our new edit sidebar resolves that with the ability to edit all fields for a given row at once.

Clean up at the click of a button

When editing a number of models, it can get difficult to get back to a clean slate. In the new Prisma Studio, we've added a "Close all" button that puts you back to a fresh start.

Add limit to updateMany() and deleteMany()

Previously, limit has not existed as a valid option in top level updateMany() and deleteMany() queries. In 6.3.0 limit is now available in these queries, bringing their features more in line with other query types.

You can use limit like the following:

await prisma.user.deleteMany({
  where: { column: 'value' },
  limit: 100,
});

This will limit the number of deleted users to 100 at maximum.

Sort generator fields deterministically

In previous version of Prisma ORM, the fields inside of a generator block in your Prisma Schema were not deterministically sorted. This could lead to cases where prisma db pull could lead to re-ordering of fields.

In 6.3.0, the sorting of fields in this block is now deterministic. You may see re-ordering on the first prisma db pull after you upgrade, but it will remain consistent afterwards.

Replace NOT IN with NOT EXISTS for PostgreSQL relation filters

In previous versions of Prisma ORM, when using the none or some relation filters, the SQL queries generated used NOT IN. In many cases this lead to performance issues as the size of the related table grew. In 6.3.0, we’ve replaced these usages of IN with EXISTS in order to improve query performance.

A special thank you

We'd like to extend our heartfelt thanks to @​loren and his team for the collaboration and trust in our enterprise support plan. Working closely with them allowed us to address important issues like #​19249 and #​17303. Their insights and partnership have been invaluable in improving our product.

If your team could benefit from dedicated support and tailored solutions, learn more about our enterprise support plan.

Fixes and improvements

Prisma Client

• Add take or limit to updateMany() & deleteMany()

Prisma

• Prisma interactive transaction ignores DB exception on commit (with triggers)
• prisma db pull non-deterministically sorts generator fields
• no entry found for key error on views<->model relations
• Adding onUpdate data to the DMMF in @prisma/generator-helper

Credits

Huge thanks to @​WhyAsh5114 for their contributions to this release!

v6.2.1

Compare Source

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

• https://github.com/prisma/prisma/pull/25997

v6.2.0

Compare Source

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.

v6.1.0

Compare Source

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'

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

v6.0.1

Compare Source

v6.0.0

Compare Source

We’re excited to share the Prisma ORM v6 release today 🎉

As this is a major release, it includes a few breaking changes that may affect your application. Before upgrading, we recommend that you check out our upgrade guide to understand the impact on your application.

If you want to have an overview of what we accomplished since v5, check out our announcement blog post: Prisma 6: Better Performance, More Flexibility & Type-Safe SQL.

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

Breaking changes

⚠️ This section contains a list of breaking changes. If you upgrade your application to Prisma ORM v6 without addressing these, your application is going to break! For detailed upgrade instructions, check out the upgrade guide. ⚠️ 

Minimum supported Node.js versions

The new minimum supported Node.js versions for Prisma ORM v6 are:

• for Node.js 18 the minimum supported version is 18.18.0
• for Node.js 20 the minimum supported version is 20.9.0
• for Node.js 22 the minimum supported version is 22.11.0

There is no official support for Node.js <18.18.0, 19, 21, 23.

Minimum supported TypeScript version

The new minimum supported TypeScript version for Prisma ORM v6 is: 5.1.0.

Schema change for implicit m-n relations on PostgreSQL

If you're using PostgreSQL and are defining implicit many-to-many relations in your Prisma schema, Prisma ORM maintains the relation table for you under the hood. This relation table has A and B columns to represent the tables of the models that are part of this relation.

Previous versions of Prisma ORM used to create a unique index on these two columns. In Prisma v6, this unique index is changing to a primary key in order to simplify for the default replica identity behaviour.

If you're defining implicit m-n relations in your Prisma schema, the next migration you'll create will contain ALTER TABLE statements for all the relation tables that belong to these relations.

Full-text search on PostgreSQL

The fullTextSearch Preview feature is promoted to General Availability only for MySQL. This means that if you're using PostgreSQL and currently make use of this Preview feature, you now need to use the new fullTextSearchPostgres Preview feature.

Usage of Buffer

Prisma v6 replaces the usage of Buffer with Uint8Array to represent fields of type Bytes. Make sure to replace all your occurrences of the Buffer type with the new Uint8Array.

Removed NotFoundError

In Prisma v6, we removed the NotFoundError in favor of PrismaClientKnownRequestError with error code P2025 in findUniqueOrThrow() and findFirstOrThrow(). If you've relied on catching NotFoundError instances in your code, you need to adjust the code accordingly.

New keywords that can't be used as model names: async, await, using

With this release, you can't use async, await and using as model names any more.

---

⚠️ For detailed upgrade instructions, check out the upgrade guide. ⚠️ 

Preview features promoted to General Availability

In this release, we are promoting a number of Preview features to General Availability.

fullTextIndex

If you use the full-text index feature in your app, you can now remove fullTextIndex from the previewFeatures in your Prisma schema:

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

fullTextSearch

If you use the full-text search feature with MySQL in your app, you can now remove fullTextSearch from the previewFeatures in your Prisma schema:

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

If you are using it with PostgreSQL, you need to update the name of the feature flag to fullTextSearchPostgres:

generator client {  
  provider        = "prisma-client-js"
- previewFeatures = ["fullTextSearch"]  
+ previewFeatures = ["fullTextSearchPostgres"]
}

New features

We are also releasing new features with this release:

• cuid2() support
• Include unused enum definitions in prisma generate's output
• Improved compatibility with Deno 2

Company news

🚀 Prisma Postgres is free during Early Access

In case you missed it: We recently launched Prisma Postgres, a serverless database with zero cold starts, a generous free tier, connection pooling, real-time events, and a lot more! It’s entirely free during the Early Access phase, try it now!

✨ Let us know what you think of Prisma ORM

We're always trying to improve! If you've recently used Prisma ORM, we'd appreciate hearing your thoughts about your experience via this 2min survey.

watson/is-ci (is-ci)

v4.1.0

Compare Source

• add types (116335d)

v4.0.0

Compare Source

• update to ci-info v4 (658c179)

jsdom/jsdom (jsdom)

v26.0.0

Compare Source

Breaking change: canvas peer dependency requirement has been upgraded from v2 to v3. (sebastianwachter)

Other changes:

• Added AbortSignal.any(). (jdbevan)
• Added initial support for form-associated custom elements, in particular making them labelable and supporting the ElementInternals labels property. The form-associated callbacks are not yet supported. (hesxenon)
• Updated whatwg-url, adding support for URL.parse().
• Updated cssstyle and rrweb-cssom, to improve CSS parsing capabilities.
• Updated nwsapi, improving CSS selector matching.
• Updated parse5, fixing a bug around <noframes> elements and HTML entity decoding.
• Fixed JSDOM.fromURL() to properly reject the returned promise if the server redirects to an invalid URL, instead of causing an uncaught exception.

facebook/react (react)

v19.0.0

Compare Source

facebook/react (react-dom)

v19.0.0

Compare Source

dcastil/tailwind-merge (tailwind-merge)

v3.0.1

Compare Source

Bug Fixes

• Update info about supported Tailwind CSS version in README by @​dcastil in b9c136d
• Update incorrect link in v3 changelog by @​dcastil in e22885e

Full Changelog: dcastil/tailwind-merge@v3.0.0...v3.0.1

Thanks to @​brandonmcconnell, @​manavm1990, @​langy, @​jamesreaco, @​roboflow, @​syntaxfm, @​getsentry, @​codecov and a private sponsor for sponsoring tailwind-merge! ❤️

v3.0.0

Compare Source

Tailwind CSS v4 is here and it's time to upgrade tailwind-merge to support it. tailwind-merge v3.0.0 is more accurate than ever and follows the Tailwind CSS spec more closely than in v2. That is thanks to Tailwind CSS v4 being more consistent than ever.

This release drops support for Tailwind CSS v3 and in turn adds support for Tailwind CSS v4. That means you should upgrade to Tailwind CSS v4 and tailwind-merge v3 together. All breaking changes are related to the Tailwind CSS v4 support.

Check out the migration guide and if you have any questions, feel free to create an issue.

Breaking Changes

• Dropping support for Tailwind CSS v3 in favor of support for Tailwind CSS v4 by @​dcastil in https://github.com/dcastil/tailwind-merge/pull/518
• Theme scales keys changed and now match Tailwind CSS v4 theme variable namespace exactly by @​dcastil in https://github.com/dcastil/tailwind-merge/pull/518
• isLength validator was removed and split into separate validators isNumber and isFraction by @​dcastil in https://github.com/dcastil/tailwind-merge/pull/518
• Prefix defined in config shouldn't include combining - character anymore by @​dcastil in https://github.com/dcastil/tailwind-merge/pull/518
• Tailwind CSS v3 prefix position in class not supported anymore in favor of Tailwind CSS v4 position by @​dcastil in https://github.com/dcastil/tailwind-merge/pull/518
• Custom separators are no longer supported by @​dcastil in https://github.com/dcastil/tailwind-merge/pull/518
• New mandatory orderSensitiveModifiers property in config when using createTailwindMerge by @​dcastil in https://github.com/dcastil/tailwind-merge/pull/518
• DefaultThemeGroupIds type union consists of different string literals than before by @​dcastil in https://github.com/dcastil/tailwind-merge/pull/518
• Classes removed in Tailwind CSS v4 are not supported by tailwind-merge anymore by @​dcastil in https://github.com/dcastil/tailwind-merge/pull/518

New Features

• Support for new important modifier position at the end of class by @​dcastil in https://github.com/dcastil/tailwind-merge/pull/518
• Support for arbitrary CSS variable syntax by @​dcastil in https://github.com/dcastil/tailwind-merge/pull/518
• There are a bunch of new validators used by tailwind-merge, primarily for new Tailwind CSS v4 features like arbitrary CSS variables by @​dcastil in https://github.com/dcastil/tailwind-merge/pull/518

Bug Fixes

• Previously some order-sensitive modifiers like before: were treated as not order-sensitive. This is now fixed by @​dcastil in https://github.com/dcastil/tailwind-merge/pull/518

Documentation

• Added section explaining order-sensitive modifiers to configuration docs by @​dcastil in https://github.com/dcastil/tailwind-merge/pull/518

Full Changelog: dcastil/tailwind-merge@v2.6.0...v3.0.0

Thanks to @​brandonmcconnell, @​manavm1990, @​langy, @​jamesreaco, @​roboflow, @​syntaxfm, @​getsentry, @​codecov and a private sponsor for sponsoring tailwind-merge! ❤️

tailwindlabs/tailwindcss (tailwindcss)

v4.0.3

Compare Source

Fixed

• Fix incorrect removal of @import url(); (#​16144)

v4.0.2

Compare Source

Fixed

• Only generate positive grid-cols-* and grid-rows-* utilities (#​16020)
• Ensure escaped theme variables are handled correctly (#​16064)
• Ensure we process Tailwind CSS features when only using @reference or @variant (#​16057)
• Refactor gradient implementation to work around prettier/prettier#17058 (#​16072)
• Vite: Ensure hot-reloading works with SolidStart setups (#​16052)
• Vite: Fix a crash when starting the development server in SolidStart setups (#​16052)
• Vite: Don't rebase URLs that appear to be aliases (#​16078)
• Vite: Transform <style> blocks in HTML files (#​16069)
• Prevent camel-casing CSS custom properties added by JavaScript plugins (#​16103)
• Do not emit @keyframes in @theme reference (#​16120)
• Discard invalid declarations when parsing CSS (#​16093)
• Do not emit empty CSS rules and at-rules (#​16121)
• Handle @variant when at the top-level of a stylesheet (#​16129)

v4.0.1

Compare Source

Added

• Include :open pseudo-class in existing open variant (#​15349)

Fixed

• Remove invalid min-w/h-none utilities (#​15845)
• Discard CSS variable shorthand utilities that don't use valid CSS variables (#​15738)
• Ensure font-size utilities with none modifier have a line-height set e.g. text-sm/none (#​15921)
• Ensure font-size utilities with unknown modifier don't generate CSS (#​15921)
• Don’t suggest font weight utilities more than once (#​15857)
• Suggest container query variants (#​15857)
• Disable bare value suggestions when not using the --spacing variable (#​15857)
• Ensure suggested classes are properly sorted (#​15857)
• Don’t look at .gitignore files outside initialized repos (#​15941)
• Find utilities when using the Svelte class shorthand syntax across multiple lines (#​15974)
• Find utilities when using the Angular class shorthand syntax (#​15974)
• Find utilities when using functions inside arrays (#​15974)
• Ensure that @tailwindcss/browser does not pollute the global namespace (#​15978)
• Ensure that tailwind-merge is not scanned when using the Vite plugin (#​16005)
• Ensure CSS theme variables are available within shadow roots (#​15975)
• Fix crash when project lives in the / directory (#​15988)
• Ensure custom variants have a non-empty selector list (#​16009)
• Upgrade: Ensure JavaScript config files on different drives are correctly migrated (#​15927)
• Upgrade: Migrate leading-[1] to leading-none (#​16004)
• Upgrade: Do not migrate arbitrary leading utilities to bare values (#​16004)

v4.0.0

Compare Source

Added

• New high-performance engine — where full builds are up to 5x faster, and incremental builds are over 100x faster — and measured in microseconds.
• Designed for the modern web — built on cutting-edge CSS features like cascade layers, registered custom properties with @property, and color-mix().
• Simplified installation — fewer dependencies, zero configuration, and just a single line of code in your CSS file.
• First-party Vite plugin — tight integration for maximum performance and minimum configuration.
• Automatic content detection — all of your template files are discovered automatically, with no configuration required.
• Built-in import support — no additional tooling necessary to bundle multiple CSS files.
• CSS-first configuration — a reimagined developer experience where you customize and extend the framework directly in CSS instead of a JavaScript configuration file.
• CSS theme variables — all of your design tokens exposed as native CSS variables so you can access them anywhere.
• Dynamic utility values and variants — stop guessing what values exist in your spacing scale, or extending your configuration for things like basic data attributes.
• Modernized P3 color palette — a redesigned, more vivid color palette that takes full advantage of modern display technology.
• Container queries — first-class APIs for styling elements based on their container size, no plugins required.
• New 3D transform utilities — transform elements in 3D space directly in your HTML.
• Expanded gradient APIs — radial and conic gradients, interpolation modes, and more.
• @​starting-style support — a new variant you can use to create enter and exit transitions, without the need for JavaScript.
• not-* variant — style an element only when it doesn't match another variant, custom selector, or media or feature query.
• Even more new utilities and variants — including support for color-scheme, field-sizing, complex shadows, inert, and more.

Start using Tailwind CSS v4.0 today by installing it in a new project, or playing with it directly in the browser on Tailwind Play.

For existing projects, we've published a comprehensive upgrade guide and built an automated upgrade tool to get you on the latest version as quickly and painlessly as possible.

For a deep-dive into everything that's new, check out the announcement post.

vitest-dev/vitest (vitest)

v3.0.5

Compare Source

🚀 Features

• ui: Insert message "no tests found" in ui - by @​DevJoaoLopes in https://github.com/vitest-dev/vitest/issues/7366 (92da4)

🐞 Bug Fixes

• Validate websocket request - by @​hi-ogawa and @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/7317 (191ef)
• Don't toggle cli cursor on non-TTY - by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/7336 (3c805)
• vite-node: Differentiate file url with hash and query - by @​hi-ogawa in https://github.com/vitest-dev/vitest/issues/7365 (926ca)

View changes on GitHub

v3.0.4

Compare Source

   🐞 Bug Fixes

• Filter projects eagerly during config resolution  -  by @​sheremet-va and @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/7313 (dff44)
• Apply development|production condition on Vites 6 by @​hi-ogawa and @​sheremet-va (#​7301) (ef146)
• browser: Restrict served files from /__screenshot-error  -  by @​hi-ogawa in https://github.com/vitest-dev/vitest/issues/7340 (ed9ae)
• deps: Update all non-major dependencies  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/7297 (38ea8)
• runner: Timeout long sync hook  -  by @​hi-ogawa in https://github.com/vitest-dev/vitest/issues/7289 (c60ee)
• typechecking: Support typechecking parsing with Vite 6  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/7335 (bff70)
• types: Fix public types  -  by @​mrginglymus and @​sheremet-va in https://github.com/vitest-dev/vitest/issues/7328 (ce6af)

    View changes on GitHub

v3.0.3

Compare Source

   🐞 Bug Fixes

• browser:
  • Don't throw a validation error if v8 coverage is used with filtered instances  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/7306 (fa463)
  • Don't fail when running --browser.headless if the browser projest is part of the workspace  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/7311 (e43a8)

   🏎 Performance

• reporters: Update summary only when needed  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/7291 (7f36b)

    View changes on GitHub

v3.0.2

Compare Source

   🐞 Bug Fixes

• Don't await an empty timeout after every test  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/7281 (ef1aa)
• expect: Fix expect().resolves/rejects chain typings  -  by @​hi-ogawa in https://github.com/vitest-dev/vitest/issues/7273 (fa415)

    View changes on GitHub

v3.0.1

Compare Source

   🐞 Bug Fixes

• Revert "fix: re-apply default conditions if using vite 6 or later (https://github.com/vitest-dev/vitest/issues/7071)"  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/7071 and https://github.com/vitest-dev/vitest/issues/7271 (755ec)
• deps: Update all non-major dependencies  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/7147 (537fa)

    View changes on GitHub

v3.0.0

Compare Source

   🚨 Breaking Changes

• spy.mockReset changes  -  by @​Lordfirespeed in [https://github.com/feat!: spy.mockReset changes vitest-dev/vitest#6426](https://github.com/vites

---

Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), 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 was generated by Mend Renovate. View the repository job log.

[deepsource-io]

Here's the code health analysis summary for commits 6b4a7a6..55379bf. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
JavaScript	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.