search

k-furusho / todo-app-nest-api

REST API for the NestJS + Next.js Todo application
0 stars 0 forks source link

Build(deps): Bump @prisma/client from 4.4.0 to 4.10.1 #123

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps @prisma/client from 4.4.0 to 4.10.1.

Release notes

Sourced from @​prisma/client's releases.

4.10.1

Today, we are issuing the 4.10.1 patch release.

Fixes in Prisma Client

4.10.0

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

Highlights

Introspection support for PostgreSQL views

We introduced initial support for database views in 4.9.0 with the addition of the view keyword. This release introduces introspection support for PostgreSQL views. You can run prisma db pull against your database to populate your Prisma schema with your views.

To learn more, refer to our documentation on views introspection. Try it out and let us know your thoughts in this GitHub issue.

Improved introspection for unsupported database functionality & partitioned tables

Currently, the Prisma Schema Language(PSL) does not cover the full feature sets of different database providers. For the unsupported database functionality, Prisma provides offers escape hatches like raw queries or manual editing of the migration files.

While we work on adding support for missing database functionality, e.g. database views, some of it is not fully-supported and the escape hatches fail. Objects that use unsupported properties might not be caught during introspection and raw queries might not work. Re-introspection may sometimes remove the information from the schema file and the generated migrations may be invalid or re-generate the same SQL repeatedly.

We're therefore fixing the defects and supporting the unsupported database functionalities Prisma currently doesn't support. We created a list of these features in this GitHub issue we would like to improve.

This release improves introspection support for partitioned tables in PostgreSQL and MySQL. Previously, Prisma would pick up the partitions as models and miss the actual main table. Prisma will now pick up the main table as a model, not the partitions.

If you're already using partitioned tables in your database, you can use prisma db pull to update your Prisma schema. If you're already using Prisma and want to partition a table in your database, you can:

  1. Create a draft migration using prisma migrate dev --create-only
  2. Update the draft migration with the SQL to partition the tables
  3. Re-run prisma migrate dev to apply the draft migration to your database

Try it out and let us know what you think. If you run into an issue, feel free to create a bug report.

Smaller engine size used in Prisma CLI

In 4.8.0, we decreased the size of the engines by ~50%, which significantly impacted Prisma Client, especially in serverless environments.

In this release, we've reduced the size of Prisma CLI by removing the Introspection and Formatter engines. The introspection functionality is now served by the Migration Engine. A cross-platform Wasm module has entirely replaced the Formatter Engine. This reduces the overall installation size for Prisma CLI.

Fixes and improvements

Prisma Client

... (truncated)

Commits
  • a650304 chore: bump engines to 4.10.1-2.aead147aa326ccb985dcfed5b065b4fdabd44b19
  • ed8c472 fix(client): missing env var regression when loading up Client (#17838)
  • 7254f9d test(client): regression test for directUrl (#17811)
  • de8cb5d chore: bump engines to patch version 4.10.1-1.80b351cc7c06d352abe81be19b8a89e...
  • f49d3b1 chore(deps): update engines to 4.10.0-84.ca7fcef713137fa11029d519a9780db130cc...
  • 42b7cb2 fix(client): Copy browser runtime files (#17779)
  • a0eb65c fix(client): data proxy custom output (#17772)
  • 73a2102 chore(deps): update engines to 4.10.0-82.596e2c7f0ee39d24a00ef2d4f0247ab4e9ba...
  • f53212c chore(deps): update engines to 4.10.0-76.77d5f190ecb9bf3906dd92740745d05467f4...
  • 18b80e7 chore(deps): update engines to 4.10.0-75.5a0a9ea068242e9e284319e8287e25470b39...
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 1 year ago

Superseded by #135.