Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 19, 2024

This PR contains the following updates:

Package Change Age Confidence
@aws-sdk/client-s3 (source) 3.896.0 -> 3.908.0 age confidence
@aws-sdk/s3-request-presigner (source) 3.896.0 -> 3.908.0 age confidence
@codemirror/legacy-modes 6.5.1 -> 6.5.2 age confidence
@codemirror/view 6.38.4 -> 6.38.5 age confidence
@playwright/test (source) 1.55.1 -> 1.56.0 age confidence
@prisma/client (source) 5.17.0 -> 5.22.0 age confidence
@supabase/realtime-js (source) 2.15.6 -> 2.75.0 age confidence
@testing-library/jest-dom 6.8.0 -> 6.9.1 age confidence
@types/node (source) 22.18.6 -> 22.18.9 age confidence
@types/react (source) 19.1.15 -> 19.2.2 age confidence
@types/react-dom (source) 19.1.9 -> 19.2.1 age confidence
@typescript-eslint/eslint-plugin (source) 7.16.1 -> 7.18.0 age confidence
@typescript-eslint/parser (source) 7.16.1 -> 7.18.0 age confidence
eslint (source) 8.57.0 -> 8.57.1 age confidence
eslint-config-prettier 9.1.0 -> 9.1.2 age confidence
katex (source) 0.16.22 -> 0.16.23 age confidence
lint-staged 16.2.3 -> 16.2.4 age confidence
motion 12.23.22 -> 12.23.24 age confidence
pnpm (source) 10.17.1 -> 10.18.2 age confidence
prettier-plugin-tailwindcss 0.6.5 -> 0.6.14 age confidence
prisma (source) 5.17.0 -> 5.22.0 age confidence
react (source) 19.1.1 -> 19.2.0 age confidence
react-dom (source) 19.1.1 -> 19.2.0 age confidence
react-hook-form (source) 7.63.0 -> 7.65.0 age confidence
tailwindcss (source) 3.4.5 -> 3.4.18 age confidence
typescript (source) 5.5.3 -> 5.9.3 age confidence
zod (source) 4.1.11 -> 4.1.12 age confidence

Release Notes

aws/aws-sdk-js-v3 (@​aws-sdk/client-s3)

v3.908.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-s3

v3.907.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-s3

v3.906.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-s3

v3.901.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-s3

v3.899.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-s3

aws/aws-sdk-js-v3 (@​aws-sdk/s3-request-presigner)

v3.908.0

Compare Source

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.907.0

Compare Source

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.906.0

Compare Source

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.901.0

Compare Source

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.899.0

Compare Source

Note: Version bump only for package @​aws-sdk/s3-request-presigner

codemirror/legacy-modes (@​codemirror/legacy-modes)

v6.5.2

Compare Source

Bug fixes

Properly tokenize multi-line strings in TOML mode.

Properly declare comment syntax metadata for the Q language.

codemirror/view (@​codemirror/view)

v6.38.5

Compare Source

Bug fixes

Avoid firing text changes that cover unchanged text on Android.

Fix an issue where the editor could, in some circumstances, insert a stray newline when typing over a document that ended in a block widget.

Work around an issue in Safari 26 that causes inappropriate scrolling on focus in some circumstances.

microsoft/playwright (@​playwright/test)

v1.56.0

Compare Source

prisma/prisma (@​prisma/client)

v5.22.0

Compare Source

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

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

Highlights
Further Tracing Improvements

In our ongoing effort to stabilize the tracing Preview feature, we’ve made our spans compliant with OpenTelemetry Semantic Conventions for Database Client Calls. This should lead to better compatibility with tools such as DataDog and Sentry.

We’ve also included numerous bug fixes that should make this Preview feature easier to work with.

Metrics bug fix

Occasionally, connection pool metrics would become negative or grow unbounded. In this release, connection pool metrics should stay consistent.

Connection Pool Timeout fix

In a specific case, there could be issues where fetching a new connection from the connection pool would time out, regardless of the state of the application and connection pool. If you have experience connection pool issues accessing a PostgreSQL database with TLS encryption in a resource-constrained environment (such as Function-as-a-Service offerings or very small VPS) this should resolve those issues.

Special thanks to @​youxq for their pull request and help resolving this issue!

Join us

Looking to make an impact on Prisma in a big way? We're hiring!

Learn more on our careers page: https://www.prisma.io/careers

Fixes and improvements
Prisma Migrate
Prisma
Credits

Huge thanks to @​tmm1, @​Takur0, @​hinaloe, @​andyjy, and @​youxq for helping!

v5.21.1

Compare Source

  • Fixed a bug where migrations were not using shadow database correctly in some edge cases

v5.21.0

Compare Source

Today, we are excited to share the 5.21.0 release 🎉

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

Highlights

Better support for tracing in MongoDB

The tracing Preview feature now has full support for MongoDB with previously missing functionality now implemented. This is a part of the ongoing effort to stabilize this Preview feature and release it in General Availability.

tracing is a Preview feature that enables built-in support for OpenTelemetry instrumentation inside the Prisma Client and provides deep insights into the performance and timing of your queries. See our documentation for more information.

For an easy to use and zero-configuration tracing instrumentation tool with a dashboard that provides an overview of your queries, statistics, and AI-powered recommendations, try Prisma Optimize.

WebAssembly engine size decrease for edge functions

Due to recent changes, some users experienced a steep increase of the bundle size in Prisma 5.20 when using the driverAdapters Preview feature, going over the 1 MB limit on the free tier of Cloudflare Workers. This has now been fixed.

Fixes and improvements

Prisma Engines

Credits

Huge thanks to @​austin-tildei, @​LucianBuzzo, @​mcuelenaere, @​pagewang0, @​key-moon, @​pranayat, @​yubrot, @​skyzh for helping!

v5.20.0

Compare Source

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

Highlights

strictUndefinedChecks in Preview

With Prisma ORM 5.20.0, the Preview feature strictUndefinedChecks will disallow any value that is explicitly undefined and will be a runtime error. This change is direct feedback from this GitHub issue and follows our latest proposal on the same issue.

To demonstrate the change, take the following code snippet:

prisma.table.deleteMany({
  where: {
    // If `nullableThing` is nullish, this query will remove all data.
    email: nullableThing?.property,
  }
})

In Prisma ORM 5.19.0 and below, this could result in unintended behavior. In Prisma ORM 5.20.0, if the strictUndefinedChecks Preview feature is enabled, you will get a runtime error instead:

Invalid \`prisma.user.findMany()\` invocation in
/client/tests/functional/strictUndefinedChecks/test.ts:0:0
  XX })
  XX 
  XX test('throws on undefined input field', async () => {
→ XX   const result = prisma.user.deleteMany({
         where: {
           email: undefined
                  ~~~~~~~~~
         }
       })
Invalid value for argument \`where\`: explicitly \`undefined\` values are not allowed."

We have also introduced the Prisma.skip symbol, which will allow you to get the previous behavior if desired.

prisma.table.findMany({
  where: {
    // Use Prisma.skip to skip parts of the query
    email: nullableEmail ?? Prisma.skip
  }
})

From Prisma ORM 5.20.0 onward, we recommend enabling strictUndefinedChecks, along with the TypeScript compiler option exactOptionalPropertyTypes, which will help catch cases of undefined values at compile time. Together, these two changes will help protect your Prisma queries from potentially destructive behavior.

strictUndefinedChecks will be a valid Preview feature for the remainder of Prisma ORM 5. With our next major version, this behavior will become the default and the Preview feature will be “graduated” to Generally Available.

If you have any questions or feedback about strictUndefinedChecks, please ask/comment in our dedicated Preview feature GitHub discussion.

typedSql bug fix

Thank you to everyone who has tried out our typedSql Preview feature and provided feedback! This release has a quick fix for typescript files generated when Prisma Schema enums had hyphens.

Fixes and improvements

Prisma
Prisma Engines

Credits

Huge thanks to @​mcuelenaere, @​pagewang0, @​key-moon, @​pranayat, @​yubrot, @​thijmenjk, @​mydea, @​HRM, @​haaawk, @​baileywickham, @​brian-dlee, @​nickcarnival, @​eruditmorina, @​nzakas, and @​gutyerrez for helping!

v5.19.1

Compare Source

Today, we are issuing the 5.19.1 patch release.

What's Changed

We've fixed the following issues:

Full Changelog: prisma/prisma@5.19.0...5.19.x, prisma/prisma-engines@5.19.0...5.19.x

v5.19.0

Compare Source

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

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

Highlights

Introducing TypedSQL

TypedSQL is a brand new way to interact with your database from Prisma Client. After enabling the typedSql Preview feature, you’re able to write SQL queries in a new sql subdirectory of your prisma directory. These queries are then checked by Prisma during using the new --sql flag of prisma generate and added to your client for use in your code.

To get started with TypedSQL:

  1. Make sure that you have the latest version of prisma and @prisma/client installed:

    npm install -D prisma@latest
    npm install @​prisma/client@latest
    
  2. Enable the typedSql Preview feature in your Prisma Schema.

       generator client {
         provider = "prisma-client-js"
         previewFeatures = ["typedSql"]
       }
    
  3. Create a sql subdirectory of your prisma directory.

    mkdir -p prisma/sql
    
  4. You can now add .sql files to the sql directory! Each file can contain one sql query and the name must be a valid JS identifier. For this example, say you had the file getUsersWithPosts.sql with the following contents:

    SELECT u.id, u.name, COUNT(p.id) as "postCount"
    FROM "User" u
    LEFT JOIN "Post" p ON u.id = p."authorId"
    GROUP BY u.id, u.name
  5. Import your SQL query into your code with the @prisma/client/sql import:

       import { PrismaClient } from '@​prisma/client'
       import { getUsersWithPosts } from '@​prisma/client/sql'
    
       const prisma = new PrismaClient()
    
       const usersWithPostCounts = await prisma.$queryRawTyped(getUsersWithPosts)
       console.log(usersWithPostCounts)

There’s a lot more to talk about with TypedSQL. We think that the combination of the high-level Prisma Client API and the low-level TypedSQL will make for a great developer experience for all of our users.

To learn more about behind the “why” of TypedSQL be sure to check out our announcement blog post.

For docs, check out our new TypedSQL section.

Bug fixes

Driver adapters and D1

A few issues with our driverAdapters Preview feature and Cloudflare D1 support were resolved via prisma/prisma-engines#4970 and #​24922

  • Mathematic operations such as max, min, eq, etc in queries when using Cloudflare D1.
  • Resolved issues when comparing BigInt IDs when relationMode="prisma" was enabled and Cloudflare D1 was being used.
Joins
  • #​23742 fixes Prisma Client not supporting deeply nested some clauses when the relationJoins Preview feature was enabled.
MongoDB

The MongoDB driver for Rust (that our query engine users under the hood) had behavior that prioritized IPv4 connections over IPv6 connections. In IPv6-only environments, this could lead to significant "cold starts" where the query engine had to wait for IPv4 to fail before the driver would try IPv6.

With help from the MongoDB team, this has been resolved. The driver will now try IPv4 and IPv6 connections in parallel and then move forward with the first response. This should prevent cold start issues that have been seen with MongoDB in Prisma Accelerate.

Thank you to the MongoDB team!

Join us

Looking to make an impact on Prisma in a big way? We're now hiring engineers for the ORM team!

  • Senior Engineer (TypeScript): This person will be primarily working on the TypeScript side and evolving our Prisma client. Rust knowledge (or desire to learn Rust) is a plus.
  • Senior Engineer (Rust): This person will be focused on the prisma-engines Rust codebase. TypeScript knowledge (or, again, a desire to learn) is a plus.

Credits

Huge thanks to @​mcuelenaere, @​pagewang0, @​Druue, @​key-moon, @​Jolg42, @​pranayat, @​ospfranco, @​yubrot, @​skyzh for helping!

v5.18.0

Compare Source

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

Highlights

Native support for UUIDv7

Previous to this release, the Prisma Schema function uuid() did not accept any arguments and created a UUIDv4 ID. While sufficient in many cases, UUIDv4 has a few drawbacks, namely that it is not temporally sortable.

UUIDv7 attempts to resolve this issue, making it easy to temporally sort your database rows by ID!

To support this, we’ve updated the uuid() function in Prisma Schema to accept an optional, integer argument. Right now, the only valid values are 4 and 7, with 4 being the default.

model User {
  id   String @​id @​default(uuid()) // defaults to 4
  name String
}

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

model User {
  id   String @​id @​default(uuid(7)) // will use UUIDv7 instead of UUIDv4
  name String
}
Bug squashing

We’ve squashed a number of bugs this release, special thanks to everyone who helped us! A few select highlights are:

Fixes and improvements

Prisma
Language tools (e.g. VS Code)

Share your feedback about Prisma ORM

We want to know how you like working with Prisma ORM in your projects! Please take our 2min survey and let us know what you like or where we can improve 🙏

Credits

Huge thanks to @​mcuelenaere, @​pagewang0, @​Druue, @​key-moon, @​Jolg42, @​pranayat, @​ospfranco, @​yubrot, @​skyzh, @​haaawk for helping!

supabase/supabase-js (@​supabase/realtime-js)

v2.75.0

Compare Source

This was a version bump only for @​supabase/realtime-js to align it with other projects, there were no code changes.

v2.74.0

Compare Source

🚀 Features
  • realtime: add support to configure Broadcast Replay (#​1623)
❤️ Thank You
  • Eduardo Gurgel
testing-library/jest-dom (@​testing-library/jest-dom)

v6.9.1

Compare Source

v6.9.0

Compare Source

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

v7.18.0

Compare Source

🩹 Fixes
  • eslint-plugin: [no-unnecessary-type-assertion] prevent runtime error when asserting a variable declared in default TS lib

  • eslint-plugin: [unbound-method] report on destructuring in function parameters

  • eslint-plugin: [no-duplicate-type-constituents] shouldn't report on error types

  • eslint-plugin: [strict-boolean-expressions] support branded booleans

❤️ Thank You
  • auvred
  • Oliver Salzburg
  • Vinccool96
  • Yukihiro Hasegawa

You can read about our versioning strategy and releases on our website.

v7.17.0

Compare Source

🚀 Features
  • eslint-plugin: backport no-unsafe-function type, no-wrapper-object-types from v8 to v7

  • eslint-plugin: [return-await] add option to report in error-handling scenarios only, and deprecate "never"

🩹 Fixes
  • eslint-plugin: [no-floating-promises] check top-level type assertions (and more)

  • eslint-plugin: [strict-boolean-expressions] consider assertion function argument a boolean context

  • eslint-plugin: [no-unnecessary-condition] false positive on optional private field

❤️ Thank You
  • Armano
  • Josh Goldberg ✨
  • Kirk Waiblinger
  • StyleShit

You can read about our versioning strategy and releases on our website.

typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v7.18.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v7.17.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

eslint/eslint (eslint)

v8.57.1

Compare Source

Bug Fixes
  • a19072f fix: add logic to handle fixTypes in the lintText() method (#​18900) (Francesco Trotta)
  • 04c7188 fix: Don't lint same file multiple times (#​18899) (Francesco Trotta)
  • 87ec3c4 fix: do not throw when defining a global named __defineSetter__ (#​18898) (Francesco Trotta)
  • 60a1267 fix: Provide helpful error message for nullish configs (#​18889) (Milos Djermanovic)
  • a0dea8e fix: allow name in global ignores, fix --no-ignore for non-global (#​18875) (Milos Djermanovic)
  • 3836bb4 fix: do not crash on error in fs.walk filter (#​18886) (Milos Djermanovic)
  • 2dec349 fix: skip processor code blocks that match only universal patterns (#​18880) (Milos Djermanovic)
Documentation
Build Related
  • 35d366a build: Support updates to previous major versions (#​18870) (Milos Djermanovic)
Chores
prettier/eslint-config-prettier (eslint-config-prettier)

v9.1.2

Compare Source

KaTeX/KaTeX (katex)

v0.16.23

Compare Source

Bug Fixes
lint-staged/lint-staged (lint-staged)

v16.2.4

Compare Source

Patch Changes
motiondivision/motion (motion)

v12.23.24

Compare Source

Fixed
  • Ensure that when a component remounts, it continues to fire animations even when initial={false}.

v12.23.23

Compare Source

Added
  • Exporting PresenceChild and PopChild type for internal use.
pnpm/pnpm (pnpm)

v10.18.2

Compare Source

Patch Changes
  • pnpm outdated --long should work #​10040.
  • Replace ndjson with split2. Reduce the bundle size of pnpm CLI #​10054.
  • pnpm dlx should request the full metadata of packages, when minimumReleaseAge is set #​9963.
  • pnpm version switching should work when the pnpm home directory is in a symlinked directory #​9715.
  • Fix EPIPE errors when piping output to other commands #​10027.

v10.18.1

Compare Source

Patch Changes
  • Don't print a warning, when --lockfile-only is used #​8320.
  • pnpm setup creates a command shim to the pnpm executable. This is needed to be able to run pnpm self-update on Windows #​5700.
  • When using pnpm catalogs and running a normal pnpm install, pnpm produced false positive warnings for "skip adding to the default catalog because it already exists". This warning now only prints when using pnpm add --save-catalog as originally intended.

v10.18.0

Compare Source

Minor Changes
  • Added network performance monitoring to pnpm by implementing warnings for slow network requests, including both metadata fetches and tarball downloads.

    Added configuration options for warning thresholds: fetchWarnTimeoutMs and fetchMinSpeedKiBps.
    Warning messages are displayed when requests exceed time thresholds or fall below speed minimums

    Related PR: #​10025.

Patch Changes
  • Retry filesystem operations on EAGAIN errors #​9959.
  • Outdated command respects minimumReleaseAge configuration #​10030.
  • Correctly apply the cleanupUnusedCatalogs configuration when removing dependent packages.
  • Don't fail with a meaningless error when scriptShell is set to false #​8748.
  • pnpm dlx should not fail when minimumReleaseAge is set #​10037.
tailwindlabs/prettier-plugin-tailwindcss (prettier-plugin-tailwindcss)

v0.6.14

Compare Source

  • Add support for OXC + Hermes Prettier plugins (#​376, #​380)
  • Sort template literals in Angular expressions (#​377)
  • Don't repeatedly add backslashes to escape sequences when formatting (#​381)

v0.6.13

Compare Source

  • Prevent Svelte files from breaking when there are duplicate classes (#​359)
  • Ensure prettier-plugin-multiline-arrays and prettier-plugin-jsdoc work when used together with this plugin (#​372)

v0.6.12

Compare Source

  • Add internal (unsupported) option to load Tailwind CSS using a different package name (#​366)

v0.6.11

Compare Source

  • Support TypeScript configs and plugins when using v4 (#​342)

v0.6.10

Compare Source


Configuration

📅 Schedule: Branch creation - "before 4am on sunday" (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.

Copy link

vercel bot commented May 19, 2024

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

Project Deployment Preview Comments Updated (UTC)
programming-in-th Error Error Sep 27, 2025 8:24pm

Copy link

github-actions bot commented May 19, 2024

Coverage Report

Status Category Percentage Covered / Total
🔵 Lines 1.38% 135 / 9781
🔵 Statements 1.38% 135 / 9781
🔵 Functions 43.91% 83 / 189
🔵 Branches 47.52% 96 / 202
File CoverageNo changed files found.
Generated in workflow #1929 for commit 0564d2a by the Vitest Coverage Report Action

@renovate renovate bot force-pushed the renovate/dependencies-(non-major) branch from 911e658 to 58530fd Compare May 19, 2024 23:44
@renovate renovate bot force-pushed the renovate/dependencies-(non-major) branch from 58530fd to d2e456f Compare May 20, 2024 15:27
@renovate renovate bot force-pushed the renovate/dependencies-(non-major) branch from d2e456f to 8236124 Compare May 21, 2024 01:04
@renovate renovate bot force-pushed the renovate/dependencies-(non-major) branch from 8236124 to 591115e Compare May 21, 2024 17:31
@renovate renovate bot force-pushed the renovate/dependencies-(non-major) branch from 591115e to 6f3c0d1 Compare May 22, 2024 02:26
@renovate renovate bot force-pushed the renovate/dependencies-(non-major) branch from 6f3c0d1 to 86c685b Compare May 22, 2024 11:56
@renovate renovate bot force-pushed the renovate/dependencies-(non-major) branch from 86c685b to 59f00b0 Compare May 22, 2024 19:07
@renovate renovate bot force-pushed the renovate/dependencies-(non-major) branch from 59f00b0 to 43c449e Compare May 22, 2024 23:06
@renovate renovate bot force-pushed the renovate/dependencies-(non-major) branch from 43c449e to f489e7a Compare May 23, 2024 10:38
@renovate renovate bot force-pushed the renovate/dependencies-(non-major) branch from f489e7a to a5d2c20 Compare May 23, 2024 13:41
@renovate renovate bot force-pushed the renovate/dependencies-(non-major) branch from a5d2c20 to 429dac7 Compare May 23, 2024 21:11
@renovate renovate bot force-pushed the renovate/dependencies-(non-major) branch from 429dac7 to 52511ee Compare May 24, 2024 10:12
@renovate renovate bot force-pushed the renovate/dependencies-(non-major) branch from 52511ee to 64824c2 Compare May 25, 2024 16:07
@renovate renovate bot force-pushed the renovate/dependencies-(non-major) branch from 64824c2 to e4b6bd6 Compare May 26, 2024 10:44
@renovate renovate bot force-pushed the renovate/dependencies-(non-major) branch from 4e02728 to 57e9c58 Compare September 27, 2025 20:22
@renovate renovate bot force-pushed the renovate/dependencies-(non-major) branch 12 times, most recently from 4ff509e to 7970775 Compare October 4, 2025 05:03
@renovate renovate bot force-pushed the renovate/dependencies-(non-major) branch 14 times, most recently from eda8a67 to c6f81b5 Compare October 11, 2025 02:08
@renovate renovate bot force-pushed the renovate/dependencies-(non-major) branch from c6f81b5 to 0564d2a Compare October 11, 2025 09:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants