chore(deps): update all-dependencies

[renovate]

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence	Type	Update
@asteasolutions/zod-to-openapi	8.2.0 → 8.5.0					dependencies	minor
@prisma/adapter-pg (source)	7.2.0 → 7.8.0					dependencies	minor
@prisma/client (source)	7.2.0 → 7.8.0					dependencies	minor
@scalar/express-api-reference (source)	0.8.30 → 0.10.8					dependencies	minor
@swc/cli	0.7.9 → 0.8.1					dependencies	minor
@swc/core (source)	1.15.8 → 1.15.43					dependencies	patch
cors	2.8.5 → 2.8.6					dependencies	patch
dotenv	17.2.3 → 17.4.2					dependencies	minor
fs-extra	11.3.3 → 11.3.6					dependencies	patch
helmet (source)	8.1.0 → 8.2.0					dependencies	minor
ioredis	5.9.0 → 5.11.1					dependencies	minor
jose	6.1.3 → 6.2.3					dependencies	minor
lint-staged	16.2.7 → 16.4.0					dependencies	minor
node-cron (source)	4.2.1 → 4.5.0					dependencies	minor
pg (source)	8.16.3 → 8.22.0					dependencies	minor
pino (source)	10.1.0 → 10.3.1					dependencies	minor
pnpm (source)	10.26.1 → 10.34.4					packageManager	minor
redis	8.4.0-alpine → 8.8.0-alpine						minor
zod (source)	4.3.2 → 4.4.3					dependencies	minor

---

Release Notes

asteasolutions/zod-to-openapi (@​asteasolutions/zod-to-openapi)

v8.5.0

Compare Source

What's Changed

• fix: allow nested discriminated unions as they are supported in Zod v4 (#​239)

Full Changelog: asteasolutions/zod-to-openapi@v8.4.3...v8.5.0

v8.4.3

Compare Source

What's Changed

• Bump rollup from 4.22.4 to 4.59.0

Full Changelog: asteasolutions/zod-to-openapi@v8.4.2...v8.4.3

v8.4.2

Compare Source

What's Changed

• Bump minimatch

Full Changelog: asteasolutions/zod-to-openapi@v8.4.1...v8.4.2

v8.4.1

Compare Source

What's Changed

• Fix memory leak in generateDocument() when using request parameters (fixes #​361)

Full Changelog: asteasolutions/zod-to-openapi@v8.4.0...v8.4.1

v8.4.0

Compare Source

What's Changed

• Added support for z.json (#​353)
• Added support for template literals (#​352)
• Fixed a bug in some nested structures when using isAnyZodType with null/undefined #​343
• Exported OpenApiOptions to resolve a problem when extending an object schema. For more information see: #​341

Full Changelog: asteasolutions/zod-to-openapi@v8.3.3...v8.4.0

v8.3.3

Compare Source

What's Changed

• use correct date-time instead of date when using z.date
• fix: add null option for nullable enum

Full Changelog: asteasolutions/zod-to-openapi@v8.3.2...v8.3.3

v8.3.2

Compare Source

Testing Trusted Publishers setup again

Full Changelog: asteasolutions/zod-to-openapi@v8.3.1...v8.3.2

v8.3.1

Compare Source

Testing the Trusted Publihsers setup

Full Changelog: asteasolutions/zod-to-openapi@v8.3.0...v8.3.1

v8.3.0

Compare Source

What's Changed

• 🎉 FINALLY added support for zod lazy (and recursive schemas with getters). Closes: #​247, #​300 and the discussion in #​191
• Bump js-yaml from 3.14.1 to 3.14.2
• Setup Trusted Publishsers for NPM

Full Changelog: asteasolutions/zod-to-openapi@v8.2.0...v8.3.0

prisma/prisma (@​prisma/adapter-pg)

v7.8.0

Compare Source

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

🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X!

Highlights

ORM

Features

Prisma Client

• Added a queryPlanCacheMaxSize option to the PrismaClient constructor for fine-grained control over the query plan cache. Pass 0 to disable the cache entirely, or omit it to use the default cache size. A larger value can improve performance in applications that execute many unique queries, while a smaller one can reduce memory usage. (#​29503)

Bug Fixes

Prisma Client

• Fixed an equality filter panic and incorrect ::jsonb cast when filtering on PostgreSQL JSON list columns. Queries using where: { jsonListField: { equals: [...] } } no longer panic with a type mismatch or emit invalid SQL. (prisma/prisma-engines#5804)
• Fixed case-insensitive JSON field filtering (mode: insensitive), allowing where: { jsonField: { equals: "...", mode: "insensitive" } } to work correctly. (prisma/prisma-engines#5806)
• Fixed incorrect parameterization of enum values that have a custom database name set via @map. (#​29422)
• Fixed a database parameter limit check (P2029), which could incorrectly reject or miss over-limit queries. (#​29422)
• Fixed a regression that caused missing SQL Server VARCHAR casts for parameterized values. (prisma/prisma-engines#5801)

Schema Engine

• Fixed a misleading error message in prisma migrate diff that referenced the --shadow-database-url CLI flag, which was removed in Prisma 7. (#​29455)
• Fixed prisma migrate dev (and shadow database migration replay in general) failing with CREATE INDEX CONCURRENTLY cannot run inside a transaction block when a migration contained concurrent index creation statements on PostgreSQL. (prisma/prisma-engines#5799)
• Fixed PostgreSQL introspection silently dropping sequence defaults when the database returns the schema-qualified form pg_catalog.nextval('sequence_name'::regclass) instead of the bare nextval(...). Columns backed by sequences now correctly appear as @default(autoincrement()) in the Prisma schema in all cases. (prisma/prisma-engines#5802)

Driver Adapters

• @​prisma/adapter-d1: Savepoint operations (createSavepoint, rollbackToSavepoint, releaseSavepoint) now silently no-op with debug logging instead of executing SQL statements, consistent with how the D1 adapter already treats top-level transactions. (#​29499)

Open roles at Prisma

Interested in joining Prisma? We're growing and have several exciting opportunities across the company for developers who are passionate about building with Prisma. Explore our open positions on our Careers page and find the role that's right for you.

Enterprise support

Thousands of teams use Prisma and many of them already tap into our Enterprise & Agency Support Program for hands-on help with everything from schema integrations and performance tuning to security and compliance.

With this program you also get priority issue triage and bug fixes, expert scalability advice, and custom training so that your Prisma-powered apps stay rock-solid at any scale. Learn more or join: https://prisma.io/enterprise.

v7.7.0

Compare Source

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

🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X!

Highlights

ORM

prisma bootstrap command

A new prisma bootstrap command (#​29374, #​29424) sequences the full Prisma Postgres setup into a single interactive flow. It detects the current project state and runs only the steps that are needed:

1. Init or scaffold — In an empty directory, offers a choice of 10 starter templates (Next.js, Express, Hono, Fastify, Nuxt, SvelteKit, Remix, React Router 7, Astro, NestJS) from prisma-examples. In an existing project without a schema, runs prisma init.
2. Link — Authenticates via the browser and connects to a Prisma Postgres database. Skips if already linked.
3. Install dependencies — Detects the package manager and offers to install missing @prisma/client, prisma, and dotenv.
4. Migrate — Runs prisma migrate dev if the schema contains models.
5. Generate — Runs prisma generate.
6. Seed — Runs prisma db seed if a seed script is configured.

Each side-effecting step prompts for confirmation. Re-running the command skips already-completed steps.

Basic usage

npx prisma@latest bootstrap

With a starter template

npx prisma@latest bootstrap --template nextjs

Non-interactive (CI)

npx prisma@latest bootstrap --api-key "$PRISMA_API_KEY" --database "db_abc123"

Open roles at Prisma

Interested in joining Prisma? We're growing and have several exciting opportunities across the company for developers who are passionate about building with Prisma. Explore our open positions on our Careers page and find the role that's right for you.

Enterprise support

Thousands of teams use Prisma and many of them already tap into our Enterprise & Agency Support Program for hands-on help with everything from schema integrations and performance tuning to security and compliance.

With this program you also get priority issue triage and bug fixes, expert scalability advice, and custom training so that your Prisma-powered apps stay rock-solid at any scale. Learn more or join: https://prisma.io/enterprise.

v7.6.0

Compare Source

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

🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X!

Highlights

ORM

Features

CLI

• Added a prisma postgres link command that connects a local project to a Prisma Postgres database. This is the first command in a new prisma postgres command group for managing Prisma Postgres databases directly from the CLI. (#​29352)

Driver Adapters

• @​prisma/adapter-pg: Added a statementNameGenerator option that accepts a custom prepared statement name generator to allow users to leverage pg statement caching (#​29395)
• @​prisma/adapter-pg: Added support for usage of connection strings directly in the constructor for improved ergonomics (#​29287)
• @​prisma/adapter-mariadb: Added a useTextProtocol option in the constructor to toggle between text and binary protocols (#​29392)

Bug Fixes

Prisma Client

• Disabled caching of createMany queries to avoid cache bloat and potential Node.js crashes in bulk operations (#​29382)
• Made NowGenerator lazy to avoid synchronous new Date() calls, fixing Next.js "dynamic usage" errors in cached components (#​28724)
• Fixed missing export of Get<Model>GroupByPayload type in the new prisma-client generator, making it accessible for TypeScript usage (#​29346)

CLI

• Added streaming parsing with automatic fallback to handle Prisma schemas that produce extremely large intermediate strings (>500MB) that hit V8's string limits (#​29377)

Driver Adapters

• @​prisma/adapter-pg: Relaxed the @types/pg version constraint to ^8.16.0 for compatibility with newer PostgreSQL type definitions (#​29390)
• @​prisma/adapter-pg: Corrected error handling for ColumnNotFound errors to correctly extract column names from both quoted and unquoted PostgreSQL error messages (#​29307)
• @​prisma/adapter-mariadb: Modified the adapter to disable mariadb statement caching by default to address a reported leak (#​29392)

Prisma Studio

We’re continuing our work to improve Prisma Studio with more features being added.

Dark Mode

Need we say more? You’ve all asked for it, and it’s back.

dark-mode-studio.mp4

Copy as markdown

Now, you can copy one or more rows as either CSV or Markdown

Multi-cell editing

This is big one, something that folks have been asking for. Now, it’s possible to edit multiple cells while inspecting your database. If you make any changes, you’ll be prompted to either save or discard them. This makes manually adding new rows much easier to accomplish.

Back relations

If your data references another table, Prisma Studio now links to the related records, making it easy to inspect them. This makes traversing your database much simpler.

CleanShot.2026-03-24.at.20.39.01.mp4

Generative SQL with AI

If you need to inspect your database, instead of manually writing the SQL you may need, you can use natural language and AI to generate the appropriate SQL statements.

CleanShot.2026-03-19.at.00.01.53.mp4

Open roles at Prisma

Interested in joining Prisma? We’re growing and have several exciting opportunities across the company for developers who are passionate about building with Prisma. Explore our open positions on our Careers page and find the role that’s right for you.

Enterprise support

Thousands of teams use Prisma and many of them already tap into our Enterprise & Agency Support Program for hands-on help with everything from schema integrations and performance tuning to security and compliance.

With this program you also get priority issue triage and bug fixes, expert scalability advice, and custom training so that your Prisma-powered apps stay rock-solid at any scale. Learn more or join: https://prisma.io/enterprise.

v7.5.0

Compare Source

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

🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X!

Highlights

ORM

Features

• Added support for nested transaction rollbacks via savepoints (#​21678)

  Adds support for nested transaction rollback behavior for SQL databases: if an outer transaction fails, the inner nested transaction is rolled back as well. Implements this by tracking transaction ID + nesting depth so Prisma can reuse an existing open transaction in the underlying engine, and it also enables using $transaction from an interactive transaction client.

Bug fixes

Driver Adapters

• Made the adapter-mariadb use the binary MySQL protocol to fix an issue with lossy number conversions (#​29285)
• Made @types/pg a direct dependency of adapter-pg for better TypeScript experience out-of-the-box (#​29277)

Prisma Client

• Resolved Prisma.DbNull serializing as empty object in some bundled environments like Next.js (#​29286)
• Fixed DateTime fields returning Invalid Date with unixepoch-ms timestamps in some cases (#​29274)
• Fixed a cursor-based pagination issue with @db.Date columns (#​29327)

Schema Engine

• Manual partial indexes are now preserved when partialIndexes preview feature is disabled, preventing unnecessary drops and additions in migrations (#​5790, #​5795)
• Enhanced partial index predicate comparison to handle quoted vs unquoted identifiers correctly, eliminating needless recreate cycles (#​5788)
• Excluded partial unique indexes from DMMF uniqueFields and uniqueIndexes to prevent incorrect findUnique input type generation (#​5792)

Studio

With the launch of Prisma ORM v7, we also introduced a rebuilt version of Prisma Studio. With the feedback we’ve gathered since the release, we’ve added some high requested features to help make Studio a better experience.

Multi-cell Selection & Full Table Search

This release brings the ability to select multiple cells when viewing your database. In addition to being able to select multiple cells, you can also search across your database. You can search for a specific table or for specific cells within that table.

More intuitive filtering

Filtering is now easier to use, and includes an option for raw SQL filters.

And if you are using Studio in Console, you can use ai generated filters:

Cmd+k Command Palette

You can now use the keyboard to perform most actions in Studio with the new cmd+k command palette

Run raw SQL queries

Another feature we’ve included in Prisma Studio is the ability to run raw SQL queries against your data. There’s a new “SQL” tab in the sidebar that will bring you to page where you can perform any queries against your data. Below, we’re getting all the rows in the “Todo” table.

Open roles at Prisma

Interested in joining Prisma? We’re growing and have several exciting opportunities across the company for developers who are passionate about building with Prisma. Explore our open positions on our [Careers page](https://www.prisma.io/careers#current) and find the role that’s right for you.

Enterprise support

Thousands of teams use Prisma and many of them already tap into our Enterprise & Agency Support Program for hands-on help with everything from schema integrations and performance tuning to security and compliance.

With this program you also get priority issue triage and bug fixes, expert scalability advice, and custom training so that your Prisma-powered apps stay rock-solid at any scale. Learn more or join: https://prisma.io/enterprise.

v7.4.2

Compare Source

Today, we are issuing a 7.4.2 patch release focused on bug fixes and quality improvements.

🛠 Fixes

Prisma Client

• Fix a case-insensitive IN and NOT IN filter regression (#​29243)
• Fix a query plan mutation issue that resulted in broken cursor queries (#​29262)
• Fix an array parameter wrapping issue in push operations (prisma/prisma-engines#5784)
• Fix Uint8Array serialization in nested JSON fields (#​29268)
• Fix an issue with MySQL joins that relied on non-strict equality (#​29251)

Driver Adapters

• @​prisma/adapter-mariadb: Update text column detection to check for a binary collation (#​29238)
• @​prisma/adapter-mariadb: Correct relationJoins compatibility check for MariaDB 8.x versions (#​29246)

Schema Engine

• Fix partial index predicate comparison on PostgreSQL and MSSQL (prisma/prisma-engines#5780)

🙏 Huge thanks to our community

Many of the fixes in this release were contributed by our amazing community members. We're grateful for your continued support and contributions that help make Prisma better for everyone!

v7.4.1

Compare Source

Today, we are issuing a 7.4.1 patch release focused on bug fixes and quality improvements.

🛠 Fixes

Prisma Client

• Fix cursor-based pagination regression with parameterised values (#​29184)
• Preserve Prisma.skip through query extension argument cloning (#​29198)
• Enable batching of multiple queries inside interactive transactions (#​25571)
• Add missing JSON value deserialization for JSONB parameter fields (#​29182)
• Apply result extensions correctly for nested and fluent relations (#​29218)
• Allow missing config datasource URL and validate only when needed (prisma/prisma-engines#5777)

Driver Adapters

• @​prisma/adapter-ppg: Handle null values in type parsers for nullable columns (#​29192)

Prisma Schema Language

• Support where argument on field-level @unique for partial indexes (prisma/prisma-engines#5774)
• Add object expression and object member support to schema reformatter (prisma/prisma-engines#5776)

🙏 Huge thanks to our community

Many of the fixes in this release were contributed by our amazing community members. We're grateful for your continued support and contributions that help make Prisma better for everyone!

v7.4.0

Compare Source

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

🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X!

Highlights

ORM

Caching in Prisma Client

Today’s release is a big one, as we introduce a new caching layer into Prisma ORM. But why the need for a caching layer?

In Prisma 7, the query compiler runs as a WebAssembly module directly on the JavaScript main thread. While this simplified the architecture by eliminating the separate engine process, it introduced a trade-off: every query now synchronously blocks the event loop during compilation.

For individual queries, compilation takes between 0.1ms and 1ms, which is barely noticeable in isolation. But under high concurrency this overhead adds up and creates event loop contention that affects overall application throughput.

For instance, say we have a query that is run over and over, but is a similar shape:

// These two queries have the same shape:
const alice = await prisma.user.findUnique({ where: { email: 'alice@prisma.io' } })
const bob = await prisma.user.findUnique({ where: { email: 'bob@prisma.io' } })

Prior to v7.4.0, this would be reevaluated ever time the query is run. Now, Prisma Client will extract the user-provided values and replaces them with typed placeholders, producing a normalized query shape:

prisma.user.findUnique({ where: { email: %1 } })   // cache key
                                         ↑
                              %1 = 'alice@prisma.io'  (or 'bob@prisma.io')

This normalized shape is used as a cache key. On the first call, the query is compiled as usual and the resulting plan is stored in an LRU cache. On every subsequent call with the same query shape, regardless of the actual values, the cached plan is reused instantly without invoking the compiler.

We have more details on the impact of this change and some deep dives into Prisma architecture in an upcoming blog post!

Partial Indexes (Filtered Indexes) Support

We're excited to announce Partial Indexes support in Prisma! This powerful community-contributed feature allows you to create indexes that only include rows matching specific conditions, significantly reducing index size and improving query performance.

Partial indexes are available behind the partialIndexes preview feature for PostgreSQL, SQLite, SQL Server, and CockroachDB, with full migration and introspection support.

Basic usage

Enable the preview feature in your schema:

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

Raw SQL syntax

For maximum flexibility, use the raw() function with database-specific predicates:

model User {
  id       Int     @​id
  email    String
  status   String

  @​@​unique([email], where: raw("status = 'active'"))
  @​@​index([email], where: raw("deletedAt IS NULL"))
}

Type-safe object syntax

For better type safety, use the object literal syntax for simple conditions:

model Post {
  id        Int      @​id
  title     String
  published Boolean

  @​@​index([title], where: { published: true })
  @​@​unique([title], where: { published: { not: false } })
}

Bug Fixes

Most of these fixes are community contributions - thank you to our amazing contributors!

• prisma/prisma-engines#5767: Fixed an issue with PostgreSQL migration scripts that prevented usage of CREATE INDEX CONCURRENTLY in migrations
• prisma/prisma-engines#5752: Fixed BigInt precision loss in JSON aggregation for MySQL and CockroachDB by casting BigInt values to text (from community member polaz)
• prisma/prisma-engines#5750: Fixed connection failures with non-ASCII database names by properly URL-decoding database names in connection strings
• #​29155: Fixed silent transaction commit errors in PlanetScale adapter by ensuring COMMIT failures are properly propagated
• #​29141: Resolved race condition errors (EREQINPROG) in SQL Server adapter by serializing commit/rollback operations using mutex synchronization
• #​29158: Fixed MSSQL connection string parsing to properly handle curly brace escaping for passwords containing special characters

Open roles at Prisma

Interested in joining Prisma? We’re growing and have several exciting opportunities across the company for developers who are passionate about building with Prisma. Explore our open positions on our Careers page and find the role that’s right for you.

Enterprise support

Thousands of teams use Prisma and many of them already tap into our Enterprise & Agency Support Program for hands-on help with everything from schema integrations and performance tuning to security and compliance.

With this program you also get priority issue triage and bug fixes, expert scalability advice, and custom training so that your Prisma-powered apps stay rock-solid at any scale. Learn more or join: https://prisma.io/enterprise.

v7.3.0

Compare Source

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

🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X!

ORM

• #​28976: Fast and Small Query Compilers
  We've been working on various performance-related bugs since the initial ORM 7.0 release. With 7.3.0, we're introducing a new compilerBuild option for the client generator block in schema.prisma with two options: fast and small. This allows you to swap the underlying Query Compiler engine based on your selection, one built for speed (with an increase in size), and one built for size (with the trade off for speed). By default, the fast mode is used, but this can be set by the user:

generator client {
  provider = "prisma-client"
  output   = "../src/generated/prisma"
  compilerBuild = "fast" // "fast" | "small"
}

We still have more in progress for performance, but this new compilerBuild option is our first step toward addressing your concerns!

• #​29005: Bypass the Query Compiler for Raw Queries
  Raw queries ($executeRaw, $queryRaw) can now skip going through the query compiler and query interpreter infrastructure. They can be sent directly to the driver adapter, removing additional overhead.

• #​28965: Update MSSQL to v12.2.0
  This community PR updates the @prisma/adapter-mssql to use MSSQL v12.2.0. Thanks Jay-Lokhande!

• #​29001: Pin better-sqlite3 version to avoid SQLite bug
  An underlying bug in SQLite 3.51.0 has affected the better-sqlite3 adapter. We’ve bumped the version that powers @prisma/better-sqlite3 and have pinned the version to prevent any unexpected issues. If you are using @prisma/better-sqlite3 , please upgrade to v7.3.0.

• #​29002: Revert @map enums to v6.19.0 behavior
  In the initial release of v7.0, we made a change with Mapped Enums where the generated enum would get its value from the value passed to the @map function. This was a breaking change from v6 that caused issues for many users. We have reverted this change for the time being, as many different diverging approaches have emerged from the community discussion.

• prisma-engines#5745: Cast BigInt to text in JSON aggregation
  When using relationJoins with BigInt fields in Prisma 7, JavaScript's JSON.parse loses precision for integers larger than Number.MAX_SAFE_INTEGER (2^53 - 1). This happens because PostgreSQL's JSONB_BUILD_OBJECT returns BigInt values as JSON numbers, which JavaScript cannot represent precisely.

  // Original BigInt ID: 312590077454712834
  // After JSON.parse: 312590077454712830 (corrupted!)
  

  This PR cast BigInt columns to ::text inside JSONB_BUILD_OBJECT calls, similar to how MONEY is already cast to ::numeric.

  -- Before
  JSONB_BUILD_OBJECT('id', "id")
  
  -- After
  JSONB_BUILD_OBJECT('id', "id"::text)
  

This ensures BigInt values are returned as JSON strings, preserving full precision when parsed in JavaScript.

Open roles at Prisma

Interested in joining Prisma? We’re growing and have several exciting opportunities across the company for developers who are passionate about building with Prisma. Explore our open positions on our [Careers page](https://www.prisma.io/careers#current) and find the role that’s right for you.

Enterprise support

Thousands of teams use Prisma and many of them already tap into our Enterprise & Agency Support Program for hands-on help with everything from schema integrations and performance tuning to security and compliance.

With this program you also get priority issue triage and bug fixes, expert scalability advice, and custom training so that your Prisma-powered apps stay rock-solid at any scale. Learn more or join: https://prisma.io/enterprise.

scalar/scalar (@​scalar/express-api-reference)

v0.10.8

v0.10.7

v0.10.6

v0.10.5

v0.10.4

v0.10.3

v0.10.2

v0.10.1

v0.10.0

Minor Changes

• #​9422: Add a nonce option for Content Security Policy support.

  When you pass a nonce, the rendered HTML stamps it onto the inline <script> and the CDN <script> tag (and Scalar's own <style> tags, plus a matching <meta property="csp-nonce">). This lets the API Reference run under a strict script-src with no unsafe-inline and no unsafe-eval.

  ApiReference({
    url: '/openapi.json',
    // Match this value in your `script-src` CSP directive.
    nonce: 'r4nd0m',
  })

  Note: style-src still needs 'unsafe-inline'. The reference renders inline style="…" attributes, which a CSP nonce can never authorize (nonces only apply to <script>, <style> and <link> elements), so a nonce-only style-src is not possible. The win is a fully strict script-src.

v0.9.20

v0.9.19

v0.9.18

v0.9.17

v0.9.16

v0.9.14

v0.9.13

v0.9.12

v0.9.11

v0.9.10

v0.9.9

Patch Changes

• #​8873: refactor: migrate integrations to client-side rendering package

v0.9.8

v0.9.7

v0.9.6

v0.9.5

v0.9.4

Patch Changes

• #​8466: chore: new build pipeline

v0.9.3

Patch Changes

Updated Dependencies

• @​scalar/core@​0.4.3

v0.9.2

v0.9.1

v0.9.0

Minor Changes

• #​8322: chore: bump required node version to >=22 (LTS)

Patch Changes

Updated Dependencies

• @​scalar/core@​0.4.0
  • #​8322: chore: bump required node version to >=22 (LTS)

v0.8.48

Patch Changes

Updated Dependencies

• @​scalar/core@​0.3.45

v0.8.47

Patch Changes

Updated Dependencies

• @​scalar/core@​0.3.44

v0.8.46

Patch Changes

Updated Dependencies

• @​scalar/core@​0.3.43

v0.8.45

Patch Changes

• #​8248: fix(express): remove unused customTheme

Updated Dependencies

• @​scalar/core@​0.3.42

v0.8.44

Patch Changes

Updated Dependencies

• @​scalar/core@​0.3.41

v0.8.41

Patch Changes

Updated Dependencies

• @​scalar/core@​0.3.38

v0.8.40

Patch Changes

Updated Dependencies

• @​scalar/core@​0.3.37

v0.8.39

Patch Changes

Updated Dependencies

• @​scalar/core@​0.3.36

v0.8.38

Patch Changes

Updated Dependencies

• @​scalar/core@​0.3.35

v0.8.37

Patch Changes

Updated Dependencies

• @​scalar/core@​0.3.34

v0.8.36

Patch Changes

Updated Dependencies

• @​scalar/core@​0.3.33

v0.8.35

Patch Changes

• #​7810: docs: update documentation domain

v0.8.34

Patch Changes

Updated Dependencies

• @​scalar/core@​0.3.32

v0.8.33

Patch Changes

Updated Dependencies

• @​scalar/core@​0.3.31

v0.8.32

Patch Changes

Updated Dependencies

• @​scalar/core@​0.3.30

v0.8.31

Patch Changes

Updated Dependencies

• @​scalar/core@​0.3.29

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

v1.15.43

Compare Source

Bug Fixes

• (es/es2022) Correct scope for private property brand checks (#​11953) ([fb5afa2](https://redirect.github.com/swc-project/swc/commit/fb5afa22796439b41a0b261b6a4823cab0dcc8

✂ Note

PR body was truncated to here.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• 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.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
express_boilerplate	Ready	Preview, Comment	Jul 2, 2026 12:33pm
express-boilerplate	Ready	Preview, Comment	Jul 2, 2026 12:33pm
express-v5-typescript-boilerplate	Ready	Preview, Comment	Jul 2, 2026 12:33pm