mk668a / nestjs-prisma-graphql-crud-gen

Generate CRUD resolvers from GraphQL schema with NestJS and Prisma
https://www.npmjs.com/package/nestjs-prisma-graphql-crud-gen
MIT License
49 stars 10 forks source link

Bump prisma from 4.1.1 to 4.8.1 in /packages/generator #109

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps prisma from 4.1.1 to 4.8.1.

Release notes

Sourced from prisma's releases.

4.8.1

Today, we are issuing the 4.8.1 patch release.

Fixe in Prisma Client

4.8.0

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

Highlights

Improved serverless experience — smaller engines size

In this release, we have decreased the size of our engine files by an average of 50%. The size of the Query Engine used on Debian, with OpenSSL 3.0.x, for example, went from 39MB to 14MB. We will also remove some smaller engines to decrease the total size in future versions.

Additionally, we have started optimizing how the Prisma schema is loaded in Prisma Client. You should notice a considerable improvement when executing the first query if you're working with a bigger schema with many models and relations.

We will continue investing in this direction in the next releases and further improve the experience with Prisma and serverless environments.

Multi-schema support for CockroachDB (Preview)

We're pleased to share that this release adds Preview support for multi-schema for CockroachDB. 🎉

This release adds support for:

  • Introspecting databases that organize objects in multiple database schemas
  • Managing multi-schema database setups directly from Prisma schema
  • Generating migrations that are database schema-aware with Prisma Migrate
  • Querying across multiple database schemas with Prisma Client

If you already have a CockroachDB database using multiple schemas, you can quickly get up and running set up multiple schemas by:

  • Enabling the Preview feature in the Prisma schema
  • Defining the schemas in the schemas property in the datasource block
  • Introspecting your database using prisma db pull

You can further evolve your database schema using the multi-schema Preview feature by using prisma migrate dev.

For further details, refer to our documentation and let us know what you think in this GitHub issue.

Improved OpenSSL 3.x support

Prisma now supports OpenSSL 3 builds for Linux Alpine on x86_64 architectures. This particularly impacts users running Prisma on node:alpine and node:lts-alpine Docker images. The images are based on an Alpine version that ships with OpenSSL 3.0.x, which isn’t compatible with OpenSSL 1.1.x (already supported by Prisma). You can read more details about it in this GitHub comment.

We also have rewritten our OpenSSL version detection logic, making it future-proof. We now expect Prisma to support systems running with any OpenSSL 3 minor versions out of the box.

Fixes and improvements

Prisma

... (truncated)

Commits
  • e6e95ea perf(client): Use dmmf from a running engine (#16798)
  • 2b9bcd8 fix(version): set ignoreEnvVarErrors: true (#16902)
  • a3cdde6 chore(deps): update dependency @​types/jest to v29.2.4
  • 5cb09a0 chore(deps): update studio to v0.479.0
  • 100d191 chore(deps): update jest (major) (#15107)
  • a94ca96 chore: update back to ubuntu-latest on CI (#16575)
  • 707836a fix(deps): update dependency fs-extra to v11 (#16513)
  • 97d1010 chore(deps): update studio to v0.478.0
  • 92d2d1c fix(validate,format): disable warnings when PRISMA_DISABLE_WARNINGS is truthy...
  • 8d8a1ed feat(validate): add lint warnings (#16458)
  • 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 #113.