chore(deps): update minor

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@eslint/compat (source)	1.2.8 -> 1.3.1
@eslint/config-inspector	1.0.2 -> 1.1.0
@eslint/js (source)	9.27.0 -> 9.30.0
@eslint/markdown	6.4.0 -> 6.6.0
@hookform/resolvers (source)	5.0.1 -> 5.1.1
@playwright/test (source)	1.52.0 -> 1.53.1
@prisma/client (source)	6.8.2 -> 6.10.1
@sentry/nextjs (source)	9.22.0 -> 9.33.0
@shikijs/rehype (source)	3.4.0 -> 3.7.0
@tanstack/react-query (source)	5.77.0 -> 5.81.5
@tanstack/react-query-devtools (source)	5.77.0 -> 5.81.5
@vitest/browser (source)	3.1.1 -> 3.2.4
@vitest/coverage-v8 (source)	3.1.1 -> 3.2.4
@vitest/eslint-plugin	1.2.7 -> 1.3.3
eslint (source)	9.27.0 -> 9.30.0
eslint-plugin-perfectionist (source)	4.13.0 -> 4.15.0
globals	16.1.0 -> 16.2.0
lucide-react (source)	0.511.0 -> 0.525.0
playwright (source)	1.52.0 -> 1.53.1
prisma (source)	6.8.2 -> 6.10.1
typescript-eslint (source)	8.32.0 -> 8.35.0
vitest (source)	3.1.1 -> 3.2.4

---

Release Notes

eslint/rewrite (@​eslint/compat)

v1.3.1

Compare Source

Bug Fixes

• relax @eslint/compat eslint peerDependencies constraint (#​215) (b96ec0c)

Dependencies

• The following workspace dependencies were updated
  • devDependencies
    • @​eslint/core bumped from ^0.15.0 to ^0.15.1

v1.3.0

Compare Source

Features

• add support for custom name parameter to includeIgnoreFile (#​211) (3e18175)

Dependencies

• The following workspace dependencies were updated
  • devDependencies
    • @​eslint/core bumped from ^0.14.0 to ^0.15.0

v1.2.9

Compare Source

Bug Fixes

• Upgrade @​eslint/core (#​197) (a830283)

eslint/config-inspector (@​eslint/config-inspector)

v1.1.0

Compare Source

Features

• update deps (541ba4c)

Bug Fixes

• rules page style, close #​134 (0af8b66)

eslint/eslint (@​eslint/js)

v9.30.0

Compare Source

v9.29.0

Compare Source

v9.28.0

Compare Source

eslint/markdown (@​eslint/markdown)

v6.6.0

Compare Source

Features

• add checkSiblingsOnly option to no-duplicate-headings rule (#​393) (2512729)
• add JSON frontmatter support (#​411) (8b77e69)
• add no-bare-urls rule (#​418) (5149927)
• add no-missing-link-fragments rule (#​380) (70e7dac)
• add no-reversed-media-syntax rule (#​398) (ae547ab)
• update no-multiple-h1 rule to recognize JSON frontmatter (#​413) (33dda18)

Bug Fixes

• ensure ATX headings follow spec for space after hash characters (#​421) (bab9670)

v6.5.0

Compare Source

Features

• add no-missing-atx-heading-space rule (#​371) (84c87c4)
• add no-empty-definitions rule (#​364) (cb5a956)
• add no-multiple-h1 rule (#​377) (d7c88e8)
• add require-alt-text rule (#​368) (32d8cbd)
• added new rule table-column-count (#​392) (c685139)
• create no-duplicate-definitions (#​360) (18c7d77)
• create no-empty-images (#​357) (23e4ff0)

Bug Fixes

• no-invalid-label-refs do not report correct position (#​366) (ed01747)
• no-missing-label-refs rule does not respect escaping (#​348) (cb6b437)
• update require-alt-text rule to ignore commented images (#​385) (b2fc801)

react-hook-form/resolvers (@​hookform/resolvers)

v5.1.1

Compare Source

Bug Fixes

• zod peer dep issue (#​780) (79cd8b2)

v5.1.0

Compare Source

Features

• support Zod 4, Zod v4 mini, and retains compatibility with Zod v3. (#​777) (8d083bd)

microsoft/playwright (@​playwright/test)

v1.53.1

Compare Source

v1.53.0

Compare Source

Trace Viewer and HTML Reporter Updates

• New Steps in Trace Viewer and HTML reporter:

• New option in 'html' reporter to set the title of a specific test run:

  import { defineConfig } from '@​playwright/test';
  
  export default defineConfig({
    reporter: [['html', { title: 'Custom test run #​1028' }]]
  });

Miscellaneous

• New option kind in testInfo.snapshotPath() controls which snapshot path template is used.

• New method locator.describe() to describe a locator. Used for trace viewer and reports.

  const button = page.getByTestId('btn-sub').describe('Subscribe button');
  await button.click();

• npx playwright install --list will now list all installed browsers, versions and locations.

Browser Versions

• Chromium 138.0.7204.4
• Mozilla Firefox 139.0
• WebKit 18.5

This version was also tested against the following stable channels:

• Google Chrome 137
• Microsoft Edge 137

prisma/prisma (@​prisma/client)

v6.10.1

Compare Source

Today, we are issuing a 6.10.1 patch release.

Bug fixes

In Prisma ORM version 6.10.0, we shipped a bug fix for Prisma Migrate that ensured we always gracefully closed PostgreSQL connections by sending the Terminate message and not just abruptly closing the TCP connection. This fix was incomplete because it didn't work on Windows, which is now fixed. We highly recommend upgrading to version 6.10.1 if you are using Windows.

We also recommend upgrading to this version if you are currently using local Prisma Postgres via the prisma dev command with an ORM version older than 6.10.x.

Performance improvements

The queryCompiler preview feature recently introduced a performance regression related to in-memory joins in TypeScript-based query execution (users who use the queryCompiler and the relationJoins preview features together were not affected, unless using relationLoadStrategy: "query"). This has now been fixed, leading to significant performance improvements: in our Query Compiler benchmarks, we are seeing up to 500x performance improvement compared to the previous implementation in the TypeScript-based query executor, or up to 10–20x performance improvement compared to the Rust-based Query Engine.

Other news

Please see the release notes for Prisma ORM 6.10.0 for other recent news and announcements.

v6.10.0

Compare Source

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

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

Highlights

No Rust engines for MS SQL Server & PlanetScale (Preview)

We are in the process of removing the Rust engines from Prisma ORM. If you want to try this, you can configure your generator like this:

generator client {
  provider        = "prisma-client-js" // or `prisma-client`
  output          = "../generated/prisma"
  previewFeatures = ["queryCompiler", "driverAdapters"]
}

In this release, we are excited to move the queryCompiler (which enables using Prisma ORM without Rust engines) into Preview for MS SQL Server and PlanetScale (via the new @prisma/adapter-mssql and existing @prisma/adapter-planetscale driver adapters).

📚Learn more in the docs.

Manage local Prisma Postgres instances in VS Code

We recently released a database management UI as part of the Prisma VS Code extension to enable visual database management workflows for Prisma Postgres. In this release, we added new functionality to it: You can now manage multiple local Prisma Postgres instances via the same UI. To try it, find the Prisma logo in VS Code’s sidebar and start managing your local Prisma Postgres instances (no Docker required).

📚 Learn more in the docs.

Performance improvements for prisma migrate dev

We improved the prisma migrate dev command by optimizing the interactions with the shadow database. Our measurements show a 2x improvement in speed for some databases!

"Push to Cloud": Easily deploy a local Prisma Postgres instance in VS Code

Local Prisma Postgres instances are perfect for development, but how do you go from local to remote once you’re ready to deploy?

The database management UI in VS Code now has a Push to Cloud button that makes it easy to deploy your local Prisma Postgres so that you can connect to it from your deployed applications.

📚 Learn more in the docs.

Support for shard keys on PlanetScale (Preview)

Sharding is a popular technique to scale up when database load grows. As of this release, Prisma ORM supports sharding on PlanetScale natively via the new @shardKey and @@​shardKey attributes in the Prisma schema which you can apply to the fields in your models that should serve as shard keys in your database setup:

// Single-column shard key
model User {
  id     String @​default(uuid())
  region String @​shardKey
}

// Multi-column shard key
model User {
  id         String @​default(uuid())
  country    String
  customerId String
  @​@​shardKey([country, customerId])
}

Note that this requires you to set the shardKeys Preview feature flag on your generator definition:

generator client {
  provider        = "prisma-client-js" // or `prisma-client`
  output          = "../generated/prisma"
  previewFeatures = ["shardKeys"]
}

📚 Learn more in the docs.

Other changes

• We deprecated the pg-worker package. It's not needed any more, you can simply use pg when using Prisma ORM in Cloudflare Workers.
• Entrypoint for new prisma-client generator changed. Learn how this affects imports in the docs.

More news

Local Prisma Postgres now works with any ORM & tool (Early Access)

We recently released direct connections for remote Prisma Postgres so that you can now use it with your favorite ORM or database tool. As of this release, this is also possible for your local Prisma Postgres instances. To try it, run the prisma dev command and use the direct connection string starting with postgres:// in order to connect from any tool.

📚 Learn more in the docs.

Let your favorite AI tool manage Prisma Postgres via remote MCP

We just released a new remote MCP server that helps you manage Prisma Postgres instances! It enables your AI tools to help with these workflows:

• Managing databases and connection strings
• Creating and re-instantiating backups
• Querying databases via plain SQL
• Introspecting database schemas

You can start it using the npx -y mcp-remote https://mcp.prisma.io/mcp command.

📚 Learn more in the docs.

v6.9.0

Compare Source

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

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

Highlights

Prisma ORM without Rust engines for PostgreSQL & SQLite (Preview)

If you've been excited about our work of removing the Rust engines from Prisma ORM but hesitated trying it out because it was in an Early Access (EA) phase, now is a great time for you to get your hands on the Rust-free Prisma ORM version.

This major architectural change has moved from EA into Preview in this release, meaning there are no more know major issues. If you want to try it out, add the queryCompiler and driverAdapters preview feature flags to your generator, install the driver adapter for your database, and get going:

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["queryCompiler", "driverAdapters"]
  output          = "../generated/prisma"
}

Now run prisma generate to re-generate Prisma Client. If you didn't use a driver adapter before, you'll need to install, e.g. the one for PostgreSQL:

npm install @​prisma/adapter-pg

Once installed, you can instantiate PrismaClient as follows:

import { PrismaClient } from './generated/prisma'
import { PrismaPg } from '@​prisma/adapter-pg'

const adapter = new PrismaPg({ connectionString: env.DATABASE_URL })
const prisma = new PrismaClient({ adapter })

No more hassle with query engines, binary targets and an even smoother experience in serverless and edge environments!

📚 Learn more in the docs.

Major improvements for local Prisma Postgres (Preview)

In the last release, we enabled you to spin up a Prisma Postgres instance locally via the new prisma dev command. Local Prisma Postgres uses PGlite under the hood and gives you an identical experience as you get with a remote Prisma Postgres instance.

This release brings major improvements to this feature:

• Persists your databases across prisma dev invocations.
• Enables you to have multiple local Prisma Postgres instances running at the same time.
• Running prisma init now uses local Prisma Postgres by default.

Try it out and let us know what you think!

📚 Learn more in the docs.

More news

Connect to Prisma Postgres with any ORM (Preview)

Since its GA release, you could only interact with Prisma Postgres using Prisma ORM via a custom connection string.

This has changed now: When setting up a new Prisma Postgres instance, you receive a regular PostgreSQL direct TCP connection string (starting with postgres://...) that lets you connect to it using your favorite tool or database library, including Drizzle, Kysely, TypeORM, and others.

If you want to access Prisma Postgres from a serverless environment, you can also use our new serverless driver (Early Access).

📚 Learn more in the docs.

Automated backup & restore

Prisma Postgres' backup and restore mechanism has seen a major upgrade recently: You can now easily restore any previous backup via the UI in the Prisma Console. Find the new Backups tab when viewing your database and select any backup from the list to restore its state to a previous point in time.

📚 Learn more in the docs.

Prisma's VS Code extension now has a UI to manage Prisma Postgres

If you're using Prisma ORM, chances are that you're using our VS Code extension too. In its latest release, we've added a major new capability to it: A UI for managing databases.

With this new UI, you can:

• Authenticate with the Prisma Console
• Create and delete remote Prisma Postgres instances
• View local Prisma Postgres instances
• View and edit data via an embedded Prisma Studio
• Visualize your database schema

To use the new features, make sure to have the latest version of the Prisma VS Code extension installed and look out for the new Prisma logo in VS Code's Activity Bar.

📚 Learn more in the docs.

New region for Prisma Postgres: San Francisco (us-west-1)

We keep expanding Prisma Postgres availability across the globe! After having added Singapore just a few weeks ago, we're now adding San Francisco based on another poll we ran on X. Here are all the regions where you can spin up Prisma Postgres instances today:

• us-west-1: San Francisco (new!)
• us-east-1: North Virginia
• eu-west-3: Paris
• ap-northeast-1: Tokyo
• ap-southeast-1: Singapore

Keep an eye on our X account to take part in the poll and vote for the next availability zone of Prisma Postgres!

getsentry/sentry-javascript (@​sentry/nextjs)

v9.33.0

Compare Source

Important Changes

• feat: Add opt-in vercelAiIntegration to cloudflare & vercel-edge (#​16732)

The vercelAiIntegration is now available as opt-in for the Cloudflare and the Next.js SDK for Vercel Edge.
To use it, add the integration in Sentry.init

Sentry.init({
  tracesSampleRate: 1.0,
  integrations: [Sentry.vercelAIIntegration()],
});

And enable telemetry for Vercel AI calls

const result = await generateText({
  model: openai('gpt-4o'),
  experimental_telemetry: {
    isEnabled: true,
  },
});

• feat(node): Add postgresjs instrumentation (#​16665)

The Node.js SDK now includes instrumentation for Postgres.js.

• feat(node): Use diagnostics channel for Fastify v5 error handling (#​16715)

If you're on Fastify v5, you no longer need to call setupFastifyErrorHandler. It is done automatically by the node SDK. Older versions still rely on calling setupFastifyErrorHandler.

Other Changes

• feat(cloudflare): Allow interop with OpenTelemetry emitted spans (#​16714)
• feat(cloudflare): Flush after waitUntil (#​16681)
• fix(nextjs): Remove ai from default server external packages (#​16736)

Work in this release was contributed by @​0xbad0c0d3. Thank you for your contribution!

v9.32.0

Compare Source

Important Changes

• feat(browser): Add CLS sources to span attributes (#​16710)

Enhances CLS (Cumulative Layout Shift) spans by adding attributes detailing the elements that caused layout shifts.

• feat(cloudflare): Add instrumentWorkflowWithSentry to instrument workflows (#​16672)

We've added support for Cloudflare Workflows, enabling comprehensive tracing for your workflow runs. This integration uses the workflow's instanceId as the Sentry trace_id and for sampling, linking all steps together. You'll now be able to see full traces, including retries with exponential backoff.

• feat(pino-transport): Add functionality to send logs to sentry (#​16667)

Adds the ability to send logs to Sentry via a pino transport.

Other Changes

• feat(nextjs): Expose top level buildTime errorHandler option (#​16718)
• feat(node): update pipeline spans to use agent naming (#​16712)
• feat(deps): bump @​prisma/instrumentation from 6.9.0 to 6.10.1 (#​16698)
• fix(sveltekit): Export logger from sveltekit worker (#​16716)
• fix(google-cloud-serverless): Make CloudEventsContext compatible with CloudEvent (#​16705)
• fix(nextjs): Stop injecting release value when create release options is set to false (#​16695)
• fix(node): account for Object. syntax with local variables matching (#​16702)
• fix(nuxt): Add alias for @opentelemetry/resources (#​16727)

Work in this release was contributed by @​flaeppe. Thank you for your contribution!

Bundle size 📦

Path	Size
@​sentry/browser	23.42 KB
@​sentry/browser - with treeshaking flags	23.2 KB
@​sentry/browser (incl. Tracing)	37.93 KB
@​sentry/browser (incl. Tracing, Replay)	75.18 KB
@​sentry/browser (incl. Tracing, Replay) - with treeshaking flags	68.42 KB
@​sentry/browser (incl. Tracing, Replay with Canvas)	79.83 KB
@​sentry/browser (incl. Tracing, Replay, Feedback)	91.63 KB
@​sentry/browser (incl. Feedback)	39.79 KB
@​sentry/browser (incl. sendFeedback)	28.02 KB
@​sentry/browser (incl. FeedbackAsync)	32.8 KB
@​sentry/react	25.16 KB
@​sentry/react (incl. Tracing)	39.88 KB
@​sentry/vue	27.69 KB
@​sentry/vue (incl. Tracing)	39.75 KB
@​sentry/svelte	23.45 KB
CDN Bundle	24.9 KB
CDN Bundle (incl. Tracing)	38 KB
CDN Bundle (incl. Tracing, Replay)	73.08 KB
CDN Bundle (incl. Tracing, Replay, Feedback)	78.41 KB
CDN Bundle - uncompressed	72.75 KB
CDN Bundle (incl. Tracing) - uncompressed	112.71 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed	224.1 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	236.62 KB
@​sentry/nextjs (client)	41.48 KB
@​sentry/sveltekit (client)	38.41 KB
@​sentry/node	147.34 KB
@​sentry/node - without tracing	96.32 KB
@​sentry/aws-serverless	121.48 KB

v9.31.0

Compare Source

Important Changes

• feat(nextjs): Add option for auto-generated random tunnel route (#​16626)

Adds an option to automatically generate a random tunnel route for the Next.js SDK. This helps prevent ad blockers and other tools from blocking Sentry requests by using a randomized path instead of the predictable /monitoring endpoint.

• feat(core): Allow to pass scope & client to getTraceData (#​16633)

Adds the ability to pass custom scope and client parameters to the getTraceData function, providing more flexibility when generating trace data for distributed tracing.

Other Changes

• feat(core): Add support for x-forwarded-host and x-forwarded-proto headers (#​16687)
• deps: Remove unused @sentry/opentelemetry dependency (#​16677)
• deps: Update all bundler plugin instances to latest & allow caret ranges (#​16641)
• feat(deps): Bump @​prisma/instrumentation from 6.8.2 to 6.9.0 (#​16608)
• feat(flags): add node support for generic featureFlagsIntegration and move utils to core (#​16585)
• feat(flags): capture feature flag evaluations on spans (#​16485)
• feat(pino): Add initial package for @sentry/pino-transport (#​16652)
• fix: Wait for the correct clientWidth/clientHeight when showing Feedback Screenshot previews (#​16648)
• fix(browser): Remove usage of Array.at() method (#​16647)
• fix(core): Improve safeJoin usage in console logging integration (#​16658)
• fix(google-cloud-serverless): Make CloudEvent type compatible (#​16661)
• fix(nextjs): Fix lookup of instrumentation-client.js file (#​16637)
• fix(node): Ensure graphql errors result in errored spans (#​16678)

Bundle size 📦

Path	Size
@​sentry/browser	23.42 KB
@​sentry/browser - with treeshaking flags	23.2 KB
@​sentry/browser (incl. Tracing)	37.89 KB
@​sentry/browser (incl. Tracing, Replay)	75.13 KB
@​sentry/browser (incl. Tracing, Replay) - with treeshaking flags	68.38 KB
@​sentry/browser (incl. Tracing, Replay with Canvas)	79.78 KB
@​sentry/browser (incl. Tracing, Replay, Feedback)	91.58 KB
@​sentry/browser (incl. Feedback)	39.79 KB
@​sentry/browser (incl. sendFeedback)	28.02 KB
@​sentry/browser (incl. FeedbackAsync)	32.8 KB
@​sentry/react	25.16 KB
@​sentry/react (incl. Tracing)	39.84 KB
@​sentry/vue	27.69 KB
@​sentry/vue (incl. Tracing)	39.71 KB
@​sentry/svelte	23.45 KB
CDN Bundle	24.9 KB
CDN Bundle (incl. Tracing)	37.97 KB
CDN Bundle (incl. Tracing, Replay)	73.03 KB
CDN Bundle (incl. Tracing, Replay, Feedback)	78.38 KB
CDN Bundle - uncompressed	72.75 KB
CDN Bundle (incl. Tracing) - uncompressed	112.63 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed	224.01 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed	236.53 KB
@​sentry/nextjs (client)	41.44 KB
@​sentry/sveltekit (client)	38.37 KB
@​sentry/node	147.29 KB
@​sentry/node - without tracing	96.27 KB
@​sentry/aws-serverless	121.42 KB

v9.30.0

Compare Source

• feat(nextjs): Add URL to tags of server components and generation functions issues (#​16500)
• feat(nextjs): Ensure all packages we auto-instrument are externalized (#​16552)
• feat(node): Automatically enable vercelAiIntegration when ai module is detected (#​16565)
• feat(node): Ensure modulesIntegration works in more environments (#​16566)
• feat(core): Don't gate user on logs with sendDefaultPii (#​16527)
• feat(browser): Add detail to measure spans and add regression tests (#​16557)
• feat(node): Update Vercel AI span attributes (#​16580)
• fix(opentelemetry): Ensure only orphaned spans of sent spans are sent ([#&markdown系ファイルもDBに入れる #820

---

Configuration

📅 Schedule: Branch creation - "before 11am on monday" in timezone Asia/Tokyo, 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.

[cloudflare-workers-and-pages]

Deploying s-private with    Cloudflare Pages

Latest commit:	a1ce905
Status:	✅  Deploy successful!
Preview URL:	https://4c6bf1a3.s-private.pages.dev
Branch Preview URL:	https://renovate-minor.s-private.pages.dev

View logs

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
s-private	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 30, 2025 0:10am

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	53.18%	2211 / 4157
🔵	Statements	53.18%	2211 / 4157
🔵	Functions	53%	97 / 183
🔵	Branches	70.1%	204 / 291

File Coverage

No changed files found.

Generated in workflow #991 for commit a1ce905 by the Vitest Coverage Report Action

[vercel]

Deployment failed with the following error:

Invalid region selector: "nrt1"