fix(deps): update prisma monorepo to v5.17.0 #68

renovate · 2024-01-09T16:57:33Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@prisma/client (source)	`5.8.0` -> `5.17.0`
prisma (source)	`5.8.0` -> `5.17.0`

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

prisma/prisma (@prisma/client)

`v5.17.0`

Compare Source

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

Highlights

VSCode extension improvements

We’re happy to introduce some cool new features that will make your experience with the Prisma VSCode extension even better!

Find references across schema files

The ability to hop between references of a given symbol is really useful in application code and now with the introduction of multi-file schema, we think it’s the perfect time to bring this feature to the VSCode extension!

With the 5.17.0 release, you’ll now have the ability to use the native “find references” feature to find any usage of a given symbol

Added context on hover

When hovering over a symbol that references a view, type, enum, or any other block with multiple values, you’ll now see a handy pop out that shows what is in that block at a glance.

Additional quick fixes

We’ve taken some fixes made by the prisma format cli command and made them quick fixes available to the VSCode Extension. Now, when you have forget a back relation or relation scalar field, you’ll now see in real time what is wrong and have the option to fix it via the extension.

QueryRaw performance improvements

We’ve changed the response format of queryRaw to decrease its average size which reduces serialization CPU overhead.

When querying large data sets, we expect you to see improved memory usage and up to 2x performance improvements.

Fixes and improvements

Credits

Huge thanks to @key-moon, @pranayat, @yubrot, @skyzh for helping!

`v5.16.2`

Compare Source

Today, we are issuing the 5.16.2 patch release to fix an issue in Prisma client.

Fix in Prisma Client

nextjs app deployed to vercel edge can't import prisma WASM modul

`v5.16.1`

Compare Source

Today, we are issuing the 5.16.1 patch release to fix an issue in Prisma client.

Fix in Prisma Client

`v5.16.0`

Compare Source

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

Highlights

Omit model fields globally

With Prisma ORM 5.16.0 we’re more than happy to announce that we’re expanding the omitApi Preview feature to also include the ability to omit fields globally.

When the Preview feature is enabled, you’re able to define fields to omit when instantiating Prisma Client.

const prisma = new PrismaClient({
  omit: {
    user: {
      // make sure that password is never queried.
      password: true,
    },
  },
});

You’re also able to omit fields from multiple models and multiple fields from the same model

const prisma = new PrismaClient({
  omit: {
    user: { 
      // make sure that password and internalId are never queried.
      password: true,
      internalId: true,
    },
    post: {
      secretkey: true,
    },
  },
});

With both local and global omit, you now have the flexibility to completely remove sensitive fields while also tailoring individual queries. If you need the ability to generally omit a field except in a specific query, you can also overwrite a global omit locally

const prisma = new PrismaClient({
  omit: {
    user: { 
      // password is omitted globally.
      password: true,
    },
  },
});

const userWithPassword = await prisma.user.findUnique({
  omit: { password: false }, // omit now false, so password is returned
  where: { id: 1 },
});

Changes to `prismaSchemaFolder`

In 5.15.0 we released the prismaSchemaFolder Preview feature, allowing you to create multiple Prisma Schema files in a prisma/schema directory. We’ve gotten a lot of great feedback and are really excited with how the community has been using the feature.

To continue improving our multi-file schema support, we have a few breaking changes to the prismaSchemaFolder feature:

When using relative paths in Prisma Schema files with the prismaSchemaFolder feature, a path is now relative to the file it is defined in rather than relative to the prisma/schema folder. This means that if you have a generator block in /project/prisma/schema/config/generator.prisma with an output of ./foo the output will be resolved to /project/prisma/schema/config/foo rather than /project/prisma/foo. The path to a SQLite file will be resolved in the same manner.
We realized that during migration many people would have prisma/schema as well as prisma/schema.prisma. Our initial implementation looked for a .prisma file first and would ignore the schema folder if it exists. This is now an error.

Changes to `fullTextSearch`

In order to improve our full-text search implementation we have made a breaking change to the fullTextSearch Preview feature.

Previously, when the feature was enabled we updated the <Model>OrderByWithRelationInput TypeScript type with the <Model>OrderByWithRelationAndSearchRelevanceInput type. However, we have noted that there are no cases where relational ordering is needed but search relevance is not. Thus, we have decided to remove the <Model>OrderByWithRelationAndSearchRelevanceInput naming and only use the <Model>OrderByWithRelationInput naming.

Fixes and improvements

Prisma

Language tools (e.g. VS Code)

Prisma Engines

Credits

Huge thanks to @key-moon, @pranayat, @yubrot, @skyzh, @brian-dlee, @mydea, @nickcarnival, @eruditmorina, @nzakas, @gutyerrez, @avallete, @ceddy4395, @Kayoshi-dev, @yehonatanz for helping!

`v5.15.1`

Compare Source

Today, we are issuing the 5.15.1 patch release.

Fixes in Prisma Client

`v5.15.0`

Compare Source

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

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

Highlights

Multi-File Prisma Schema support

Prisma ORM 5.15.0 features support for multi-file Prisma Schema in Preview.

This closes a long standing issue and does so in a clean and easy to migrate way.

To get started:

Enable the prismaSchemaFolder Preview feature by including it in the previewFeatures field of your generator.

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

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

Create a schema subdirectory under your prisma directory.
Move your schema.prisma into this directory.

You are now set up with a multi-file Prisma Schema! Add as many or as few .prisma files to the new prisma/schema directory.

When running commands where a Prisma Schema file is expected to be provided, you can now define a Prisma Schema directory. This includes Prisma CLI commands that use the --schema option as well as defining schema via package.json

Our tooling has also been updated to handle multiple Prisma Schema files. This includes our Visual Studio Code extension and tools like database introspection, which will deposit new models in a introspected.prisma file. Existing models will be updated in the file they are found.

To learn more, please refer to our official documentation and announcement blog post. If you try out prismaSchemaFolder, please let us know!

Interesting Bug Fixes

Fix for PostgreSQL prepared statement caching for raw queries

This release fixes a nasty bug with the caching of prepared statements in raw Prisma Client queries that affected PostgreSQL when you ran the same SQL statement with differently typed paramters. This should not fail any more.

Fix for SQL Server introspection of (deprecated) `CREATE DEFAULT`

Our Introspection logic crashed on encountering certain multi-line CREATE DEFAULT, a deprecated way to define defaults in SQL Server. As many SQL Server users are working with established databases, this happened frequently enough that we now explicitly ignore these defaults instead of crashing.

Fix for Cloudflare D1’s lower parameter limit

Cloudflare’s D1 has a lower parameter limit than local SQLite, which caused bigger queries to fail. We adapted that limit to the D1 default for @prisma/adapter-d1, which will avoid such failures.

Fix for Cloudflare D1’s different `PRAGMA` support

Our generated migration SQL for SQLite did not always work for Cloudflare D1, because of differences in the supported pragmas. We adapted the SQL to work in both local SQLite and Cloudflare D1.

Fixes and improvements

Prisma Migrate

Prisma Client

Language tools (e.g. VS Code)

Credits

Huge thanks to @pranayat, @yubrot, and @skyzh for helping!

`v5.14.0`

Compare Source

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

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

Highlights

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 🙏

`createManyAndReturn()`

We’re happy to announce the availability of a new, top-level Prisma Client query: createManyAndReturn(). It works similarly to createMany() but uses a RETURNING clause in the SQL query to retrieve the records that were just created.

Here’s an example of creating multiple posts and then immediately returning those posts.

const postBodies = req.json()['posts']

const posts = prisma.post.createManyAndReturn({
	data: postBodies
});

return posts

Additionally,createManyAndReturn() supports the same options as findMany(), such as the ability to return only specific fields.

const postBodies = req.json()['posts']

const postTitles = prisma.post.createManyAndReturn({
	data: postBodies,
	select: {
	  title: true,
	},
});

return postTitles

Note: Because createManyAndReturn() uses the RETURNING clause, it is only supported by PostgreSQL, CockroachDB, and SQLite databases. At this time, relationLoadStrategy: join is not supported in createManyAndReturn() queries.

MongoDB performance improvements

Previously, Prisma ORM suffered from performance issues when using the in operator or when including related models in queries against a MongoDB database. These queries were translated by the Prisma query engine in such a way that indexes were skipped and collection scans were used, leading to slower queries especially on large datasets.

With 5.14.0, Prisma ORM now rewrites queries to use a combination of $or and $eq operators, leading to dramatic performance increases for queries that include in operators or relation loading.

Fixes and improvements

Prisma Client

Prisma Migrate

Language tools (e.g. VS Code)

Company news

Prisma Changelog

Curious about all things Prisma? Be sure to check out the Prisma Changelog for updates across Prisma's products, including ORM, Accelerate, and Pulse!

Credits

Huge thanks to @pranayat, @yubrot, @skyzh, @anuraaga, @gutyerrez, @avallete, @ceddy4395, @Kayoshi-dev for helping!

`v5.13.0`

Compare Source

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

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

Highlights

`omit` fields from Prisma Client queries (Preview)

We’re excited to announce Preview support for the omit option within the Prisma Client query options. The highly-requested omit feature now allows you to exclude fields that you don’t want to retrieve from the database on a per-query basis.

By default, when a query returns records, the result includes all scalar fields of the models defined in the Prisma schema. select can be used to return specific fields, while omit can now be used to exclude specific fields. omit lives at the same API level and works on all of the same Prisma Client model queries as select. Note, however, that omit and select are mutually exclusive. In other words, you can’t use both in the same query.

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

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

Be sure to re-generate Prisma Client afterwards:

npx prisma generate

Here is an example of using omit:

// Includes all fields except password
await prisma.user.findMany({
  omit: {
   password: true
  },
})

Here is an example of using omit with include:

// Includes all user fields except user's password and title of user's posts
await prisma.user.findMany({
  omit: {
   password: true
  },
  include: {
    posts: {
      omit: {
        title: true
      },
    },
  },
})

Expand to view the example Prisma schema

model User {
  id       Int     @&#8203;id @&#8203;default(autoincrement())
  email    String  @&#8203;unique
  name     String?
  password String
  posts    Post[]
}

model Post {
  id       Int    @&#8203;id @&#8203;default(autoincrement())
  title    String
  author   User   @&#8203;relation(fields: [authorId], references: [id])
  authorId Int
}

Many users have requested a global implementation of omit. This request will be accommodated in the future. In the meantime, you can follow the issue here.

📣 Share your feedback: omitApi Preview feature

📚 Documentation: omit - Prisma Client API Reference

Fixes and improvements

Prisma Migrate

Nicer Datamodel Type validation

Prisma Client

✘ [ERROR] near "��": syntax error at offset 0 when running wrangler d1 migrations apply with Prisma generated migration (on Windows, using Powershell)

Credits

Huge thanks to @ospfranco, @pranayat, @yubrot, @skyzh, @anuraaga, @yehonatanz, @arthurfiorette, @elithrar, @tockn, @Kuhave, @obiwac for helping!

`v5.12.1`

Compare Source

Today, we are issuing the 5.12.1 patch release to fix two small problems with our new Cloudflare D1 support.

Fixes in Prisma CLI

Windows-only fix for new D1 specific flags for `migrate diff` and `db pull`

The flags --from-local-d1 and --to-local-d1 for migrate diff and --local-d1 to db pull we added in 5.12.0 were not working as expected when running on Windows only. This is now fixed.

📚 Documentation: Deploying a Cloudflare worker with D1 and Prisma ORM

New option for `migrate diff`: `-o` or `--output`

We added a new parameter --output to migrate diff that can be used to provide a filename into which the output of the command will be written. This is particularly useful for Windows users, using PowerShell, as using > to write into a file creates a UTF-16 LE file that can not be read by wrangler d1 migrations apply. Using this new option, this problem can be avoided:

npx prisma migrate diff --script --from-empty --to-schema-datamodel ./prisma/schema.prisma --output ./schema.sql

Related issues:

✘ [ERROR] near "��": syntax error at offset 0 when running wrangler d1 migrations apply with Prisma generated migration (on Windows, using PowerShell) #23702
[prisma migrate resolve --applied not working on new project, migration ... could not be found.][https://github.com/prisma/prisma/issues/17558](https://togithub.com/prisma/prisma/issues/17558)8)

`v5.12.0`

Compare Source

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

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

Highlights

Cloudflare D1 (Preview)

This release brings Preview support for Cloudflare D1 with Prisma ORM 🥳

D1 is Cloudflare’s SQLite database that can be used when deploying applications with Cloudflare.

When using Prisma ORM with D1, you can continue to: model your database with Prisma schema language, specify sqlite as your database provider in your Prisma schema, and interact with your database using Prisma Client.

To use Prisma ORM and D1 on Cloudflare Workers or Cloudflare Pages, you need to set sqlite as your database provider and use the @prisma/adapter-d1 database adapter via the driverAdapters Preview feature, released back in version 5.4.0.

Here is an example of sending a query to your D1 database using Prisma Client in your Worker:

// src/index.ts file
import { PrismaClient } from '@&#8203;prisma/client'
import { PrismaD1 } from '@&#8203;prisma/adapter-d1'

// Add the D1Database to the Env interface
export interface Env {
// This must match the binding name defined in your wrangler.toml configuration
  DB: D1Database
}

export default {
  async fetch(
    request: Request,
    env: Env,
    ctx: ExecutionContext
  ): Promise<Response> {
    // Make sure the database name matches the binding name in wrangler.toml and Env interface
    const adapter = new PrismaD1(env.DB)
    // Instantiate PrismaClient using the PrismaD1 driver adapter
    const prisma = new PrismaClient({ adapter })

    const users = await prisma.user.findMany()
    const result = JSON.stringify(users)
    return new Response(result)
  },
}

📚 Documentation: Deploying a Cloudflare worker with D1 and Prisma ORM

✍️ Blog post: Build Applications at the Edge with Prisma ORM & Cloudflare D1 (Preview)

📣 Share your feedback: D1 Driver Adapter

🚀 Example project: Deploy a Cloudflare Worker with D1

`createMany()` for SQLite

Bringing support for createMany() in SQLite has been a long-awaited and highly requested feature ⭐

createMany() is a method on Prisma Client, released back in version 2.16.0, that lets you insert multiple records into your database at once. This can be really useful when seeding your database or inserting bulk data.

Here is an example of using createMany() to create new users:

const users = await prisma.user.createMany({
  data: [
    { name: 'Sonali', email: '[email protected]' },
    { name: 'Alex', email: '[email protected]' },
    { name: 'Yewande', email: '[email protected]' },
    { name: 'Angelina', email: '[email protected]' },
  ],
})

Before this release, if you wanted to perform bulk inserts with SQLite, you would have most likely used $queryRawUnsafe to execute raw SQL queries. But now you don’t have to go through all that trouble 🙂

With SQLite, createMany() works exactly the same way from an API standpoint as it does with other databases except it does not support the skipDuplicates option. At the behavior level, SQLite will split createMany() entries into multiple INSERT queries when the model in your schema contains fields with attributes like @default(dbgenerated()) or @default(autoincrement()) and when the fields are not consistently provided with values across the entries.

📚Documentation: createMany() - Prisma Client API Reference

Fixes and Improvements

Prisma Client

Credits

Huge thanks to @yubrot, @skyzh, @anuraaga, @onichandame, @LucianBuzzo, @RobertCraigie, @arthurfiorette, @elithrar for helping!

`v5.11.0`

Compare Source

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

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

Highlights

Edge function support for Cloudflare and Vercel (Preview)

We’re thrilled to announce that support for edge function deployments with Prisma ORM is now in Preview 🥳 As of this release, you can deploy your apps that are using Prisma ORM to:

Vercel Edge Functions and Vercel Edge Middleware
Cloudflare Workers and Cloudflare Pages

In order to deploy to an edge function, you’ll need to use a compatible database driver (along with its Prisma driver adapter):

Neon Serverless Driver (for PostgreSQL databases hosted via Neon)
PlanetScale Serverless Driver (for MySQL databases hosted via PlanetScale)
pg driver (for traditional PostgreSQL databases)
@libsql/client driver (for SQLite databases hosted via Turso)

Check out our documentation to learn how you can deploy an edge function using any combination of supported edge function provider and database.

Performance improvements in nested `create` operations

With Prisma ORM, you can create multiple new records in nested queries, for example:

const user = await prisma.user.update({
  where: { id: 9 },
  data: {
    name: 'Elliott',
    posts: {
      create: {
        data: [{ title: 'My first post' }, { title: 'My second post' }],
      },
    },
  },
})

In previous versions, Prisma ORM would translate this into multiple SQL INSERT queries, each requiring its own roundtrip to the database. As of this release, these nested create queries are optimized and the INSERT queries are sent to the database in bulk in a single roundtrip. These optimizations apply to one-to-many as well as many-to-many relations.

With this change, using the nested create option to create multiple records effectively becomes equivalent to using a nested createMany operation (except that createMany only works with one-to-many relations, whereas create works both with one-to-many and many-to-many).

Note: Only the deepest nested operation is optimized. If a user specified create (1) -> create (2) -> create (3) in their query, only create (3) will be optimized.

Fixes and improvements

Prisma Client

Prisma Migrate

Prisma Engines

`v5.10.2`

Compare Source

Today, we are issuing the 5.10.2 patch release.

Fix in Prisma CLI

Invalid character error persists on 5.10.1 in Prisma Studio

`v5.10.1`

Compare Source

Today, we are issuing the 5.10.1 patch release.

Fix in Prisma Client / Prisma CLI

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

`v5.10.0`

Compare Source

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

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

Highlights

Optimized relation queries in MySQL (Preview)

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

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

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

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

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

Be sure to re-generate Prisma Client afterwards:

npx prisma generate

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

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

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

A few notes about relationLoadStrategy support on MySQL:

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

Configure transaction options in the `PrismaClient` constructor

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

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

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

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

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

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

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

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

Access the Prisma Data Platform via Prisma CLI

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

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

Fixes and improvements

Prisma Client

`v5.9.1`

Compare Source

Today, we are issuing the 5.9.1 patch release.

Fixes in Prisma Client

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

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

Note: many issues are duplicates.

`v5.9.0`

Compare Source

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

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

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

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

Highlights

Optimized result sets for more efficient queries

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

SQL Server: Return proper error for unreachable database

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

Fixes and improvements

Prisma Client

Prisma Migrate

Language tools (e.g. VS Code)

Extension wrongfully suggests Json as a valid type completion on Sqlite

Company news

Test edge functions support in Early Access

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

We Transitioned Prisma Accelerate to IPv6 Without Anyone Noticing

Last year, AWS announced the decision to begin charging for IPv4 addresses beginning in February 2024. This move had a major impact on Prisma Accelerate, prompting us to go all-in on I

Configuration

📅 Schedule: 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.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

renovate · 2024-08-01T14:33:36Z

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

Progress: resolved 0, reused 1, downloaded 0, added 0
undefined
 ERR_PNPM_FETCH_404  GET https://registry.npmjs.org/@brucesong/eslint-config-ts/-/eslint-config-ts-1.0.17.tgz: Not Found - 404

This error happened while installing a direct dependency of /tmp/renovate/repos/github/dolphin-admin/nest-api

No authorization header was set for the request.

changeset-bot · 2024-08-01T14:33:38Z

⚠️ No Changeset found

Latest commit: e830e76

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

renovate bot added the Dependencies Pull requests that update a dependency file label Jan 9, 2024

pull-request-size bot added the size/S label Jan 9, 2024

renovate bot force-pushed the renovate/prisma-monorepo branch from 5d6a60a to 3236a3f Compare January 11, 2024 14:09

pull-request-size bot added size/L and removed size/S labels Jan 11, 2024

renovate bot changed the title ~~fix(deps): update prisma monorepo to v5.8.0~~ fix(deps): update prisma monorepo to v5.8.0 - autoclosed Jan 13, 2024

renovate bot closed this Jan 13, 2024

renovate bot deleted the renovate/prisma-monorepo branch January 13, 2024 12:17

renovate bot changed the title ~~fix(deps): update prisma monorepo to v5.8.0 - autoclosed~~ fix(deps): update prisma monorepo to v5.8.0 Jan 15, 2024

renovate bot reopened this Jan 15, 2024

renovate bot restored the renovate/prisma-monorepo branch January 15, 2024 14:55

renovate bot force-pushed the renovate/prisma-monorepo branch from 3236a3f to 826cdd0 Compare January 15, 2024 14:56

renovate bot changed the title ~~fix(deps): update prisma monorepo to v5.8.0~~ fix(deps): update prisma monorepo to v5.8.1 Jan 15, 2024

pull-request-size bot added size/S and removed size/L labels Jan 15, 2024

renovate bot force-pushed the renovate/prisma-monorepo branch from 826cdd0 to f7c1ebc Compare January 30, 2024 17:39

renovate bot changed the title ~~fix(deps): update prisma monorepo to v5.8.1~~ fix(deps): update prisma monorepo to v5.9.0 Jan 30, 2024

renovate bot force-pushed the renovate/prisma-monorepo branch from f7c1ebc to 0267f4e Compare February 1, 2024 16:05

renovate bot changed the title ~~fix(deps): update prisma monorepo to v5.9.0~~ fix(deps): update prisma monorepo to v5.9.1 Feb 1, 2024

renovate bot force-pushed the renovate/prisma-monorepo branch from 0267f4e to 2d21edd Compare February 20, 2024 16:38

renovate bot changed the title ~~fix(deps): update prisma monorepo to v5.9.1~~ fix(deps): update prisma monorepo to v5.10.0 Feb 20, 2024

renovate bot force-pushed the renovate/prisma-monorepo branch from 2d21edd to 0bed0ca Compare February 20, 2024 19:51

renovate bot changed the title ~~fix(deps): update prisma monorepo to v5.10.0~~ fix(deps): update prisma monorepo to v5.10.1 Feb 20, 2024

renovate bot force-pushed the renovate/prisma-monorepo branch from 0bed0ca to c60c69f Compare February 21, 2024 21:24

renovate bot changed the title ~~fix(deps): update prisma monorepo to v5.10.1~~ fix(deps): update prisma monorepo to v5.10.2 Feb 21, 2024

renovate bot force-pushed the renovate/prisma-monorepo branch from c60c69f to 885f1da Compare February 25, 2024 09:05

pull-request-size bot added size/XL and removed size/S labels Feb 25, 2024

renovate bot force-pushed the renovate/prisma-monorepo branch 2 times, most recently from 4a0fc67 to 2addfd2 Compare March 12, 2024 15:00

renovate bot changed the title ~~fix(deps): update prisma monorepo to v5.10.2~~ fix(deps): update prisma monorepo to v5.11.0 Mar 12, 2024

renovate bot force-pushed the renovate/prisma-monorepo branch 2 times, most recently from d4eb1b9 to 348f87c Compare March 24, 2024 14:49

renovate bot force-pushed the renovate/prisma-monorepo branch from 348f87c to ea06d17 Compare April 2, 2024 13:37

renovate bot changed the title ~~fix(deps): update prisma monorepo to v5.11.0~~ fix(deps): update prisma monorepo to v5.12.0 Apr 2, 2024

renovate bot force-pushed the renovate/prisma-monorepo branch from ea06d17 to 5494754 Compare April 4, 2024 12:57

renovate bot changed the title ~~fix(deps): update prisma monorepo to v5.12.0~~ fix(deps): update prisma monorepo to v5.12.1 Apr 4, 2024

fix(deps): update prisma monorepo to v5.17.0

e830e76

renovate bot force-pushed the renovate/prisma-monorepo branch from 5494754 to e830e76 Compare August 1, 2024 14:33

renovate bot changed the title ~~fix(deps): update prisma monorepo to v5.12.1~~ fix(deps): update prisma monorepo to v5.17.0 Aug 1, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix(deps): update prisma monorepo to v5.17.0 #68

fix(deps): update prisma monorepo to v5.17.0 #68

renovate bot commented Jan 9, 2024 •

edited

Loading

renovate bot commented Aug 1, 2024

changeset-bot bot commented Aug 1, 2024

fix(deps): update prisma monorepo to v5.17.0 #68

Are you sure you want to change the base?

fix(deps): update prisma monorepo to v5.17.0 #68

Conversation

renovate bot commented Jan 9, 2024 • edited Loading

Release Notes

Highlights

VSCode extension improvements

QueryRaw performance improvements

Fixes and improvements

Prisma Client

Prisma

Language tools (e.g. VS Code)

Credits

Fix in Prisma Client

Fix in Prisma Client

Highlights

Omit model fields globally

Changes to prismaSchemaFolder

Changes to fullTextSearch

Fixes and improvements

Prisma

Language tools (e.g. VS Code)

Prisma Engines

Credits

Fixes in Prisma Client

Highlights

Multi-File Prisma Schema support

Interesting Bug Fixes

Fix for PostgreSQL prepared statement caching for raw queries

Fix for SQL Server introspection of (deprecated) CREATE DEFAULT

Fix for Cloudflare D1’s lower parameter limit

Fix for Cloudflare D1’s different PRAGMA support

Fixes and improvements

Prisma Migrate

Prisma Client

Language tools (e.g. VS Code)

Credits

Highlights

Share your feedback about Prisma ORM

createManyAndReturn()

MongoDB performance improvements

Fixes and improvements

Prisma Client

Prisma Migrate

Language tools (e.g. VS Code)

Company news

Prisma Changelog

Credits

Highlights

omit fields from Prisma Client queries (Preview)

Fixes and improvements

Prisma Migrate

Prisma Client

Credits

Fixes in Prisma CLI

Windows-only fix for new D1 specific flags for migrate diff and db pull

New option for migrate diff: -o or --output

Highlights

Cloudflare D1 (Preview)

createMany() for SQLite

Fixes and Improvements

Prisma Client

Credits

Highlights

Edge function support for Cloudflare and Vercel (Preview)

Performance improvements in nested create operations

Fixes and improvements

Prisma Client

Prisma Migrate

Prisma Engines

Fix in Prisma CLI

Fix in Prisma Client / Prisma CLI

Highlights

Optimized relation queries in MySQL (Preview)

Configure transaction options in the PrismaClient constructor

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

Access the Prisma Data Platform via Prisma CLI

Fixes and improvements

Prisma Client

renovate bot commented Jan 9, 2024 •

edited

Loading

Changes to `prismaSchemaFolder`

Changes to `fullTextSearch`

Fix for SQL Server introspection of (deprecated) `CREATE DEFAULT`

Fix for Cloudflare D1’s different `PRAGMA` support

`createManyAndReturn()`

`omit` fields from Prisma Client queries (Preview)

Windows-only fix for new D1 specific flags for `migrate diff` and `db pull`

New option for `migrate diff`: `-o` or `--output`

`createMany()` for SQLite

Performance improvements in nested `create` operations

Configure transaction options in the `PrismaClient` constructor

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