Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update prisma monorepo to v3.13.0 #5375

Merged
merged 1 commit into from
May 1, 2022
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 1, 2022

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@prisma/client (source) 3.12.0 -> 3.13.0 age adoption passing confidence
@prisma/sdk (source) 3.12.0 -> 3.13.0 age adoption passing confidence
prisma (source) 3.12.0 -> 3.13.0 age adoption passing confidence

Release Notes

prisma/prisma

v3.13.0

Compare Source

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

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

Major improvements

migrate diff and db execute are now Generally Available!

We released two new Preview CLI commands in version 3.9.0prisma migrate diff and prisma db execute – to enable our users to create and understand migrations and build their workflows using the commands.

We're proud to announce that the commands are now Generally Available and can now be used without the --preview-feature flag. 🎉

The prisma migrate diff command creates a diff of your database schema, Prisma schema file, or the migration history. All you have to do is feed the command with a schema from state and a schema to state to get an SQL script or human-readable diff.

In addition to prisma migrate diff, prisma db execute is used to execute SQL scripts against a database. You can directly execute prisma migrate diff's output using prisma db execute --stdin.

Both commands are non-interactive, so it's possible to build many new workflows such as forward and backward migrations with some automation tooling. Take a look at our documentation to learn some of the popular workflows these commands unlock:

Let us know what tools, automation, and scripts you build using these commands.

SQL Server index clustering (Preview)

In version 3.5.0, we introduced the extendedIndexes Preview feature which we have constantly been adding new configuration options for indexes. In this release, we added support for enabling or disabling index/constraint clustering in SQL Server.

By default, indexes will be clustered by default. You can update this in your schema as follows to disable index clustering:

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

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

model Post {
  id      Int     @​default(autoincrement()) @​id(clustered: false)
  title   String
  content String?
}

The following SQL will be generated in your migration when you run prisma migrate dev

CREATE TABLE [Post] (
  id INT NOT NULL,
  [title] VARCHAR(255) NOT NULL,
  [content] NVARCHAR(1000),
  CONSTRAINT [Post_pkey] PRIMARY KEY NONCLUSTERED (id)
)

If you've enabled the extendedIndexes Preview feature, this is potentially a breaking change. Refer to our documentation to learn how you can upgrade from a previous version.

Updated native types for CockroachDB (Preview)

We have revamped the native types available in the CockroachDB connector. We initially re-used the PostgreSQL native types because they were close enough, but we have now adapted our list of the supported native types to match what CockroachDB supports.

If you are already using CockroachDB in your project, you can run prisma db pull to update all the native types in your Prisma schema. Refer to our documentation for the complete list of all CockroachDB native types.

OpenSSL 3.0 Support

We're excited to announce that version 3.13.0 now supports OpenSSL 3.0. Operating systems such as Ubuntu 22.04 default to OpenSSL 3.0, and when running prisma generate, you would run into the following error:

Error: Unknown binaryTarget debian-openssl-3.0.x

If you've run into a similar error, bump up to the latest Prisma version and give it another try!

Fixes and improvements

Prisma Client
Prisma
Language tools (e.g. VS Code)
Prisma Engines

Credits

Huge thanks to @​ever0de, @​jacobhq, @​dkantereivin, @​CommanderRoot for helping!

💼 We're hiring!

If you're interested in joining our growing team to help empower developers to build data-intensive applications, Prisma is the place for you.

We're looking for a Technical Support Engineer and Senior Software Engineer (Prisma Data Platform).

Feel free to read through the job descriptions and apply using the links provided.

📺 Join us for another "What's new in Prisma" livestream

Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" livestream.

The stream takes place on YouTube on Thursday, April 28 at 5 pm Berlin | 8 am San Francisco.


Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Enabled.

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, click this checkbox.

This PR has been generated by WhiteSource Renovate. View repository job log here.

@renovate renovate bot added the release:chore This PR is a chore (means nothing for users) label May 1, 2022
@netlify
Copy link

netlify bot commented May 1, 2022

Deploy Preview for redwoodjs-docs canceled.

Name Link
🔨 Latest commit 6457783
🔍 Latest deploy log https://app.netlify.com/sites/redwoodjs-docs/deploys/626e76103959cd000961ecf0

@jtoar jtoar enabled auto-merge (squash) May 1, 2022 12:23
@jtoar jtoar merged commit ec45beb into main May 1, 2022
@jtoar jtoar deleted the renovate/prisma-monorepo branch May 1, 2022 12:25
@jtoar jtoar added this to the next-release milestone May 1, 2022
dac09 added a commit to dac09/redwood that referenced this pull request May 2, 2022
…-core-tests

* 'main' of github.com:redwoodjs/redwood: (668 commits)
  Fix broken link in authentication.md (redwoodjs#5394)
  Update local-postgres-setup.md (redwoodjs#5353)
  modify typescript example (redwoodjs#5377)
  fix(deps): update dependency core-js to v3.22.3 (redwoodjs#5376)
  fix(deps): update dependency @types/node to v16.11.32 (redwoodjs#5374)
  fix(deps): update prisma monorepo to v3.13.0 (redwoodjs#5375)
  chore(deps): update dependency typescript to v4.6.4 (redwoodjs#5372)
  chore(deps): update dependency nodemon to v2.0.16 (redwoodjs#5364)
  fix(docs): add WindiCSS in setup ui list (redwoodjs#5369)
  chore(deps): update dependency @nhost/nhost-js to v1.1.6 (redwoodjs#5363)
  Add back git fetch step for lerna
  chore(deps): update dependency @clerk/clerk-sdk-node to v3.3.10 (redwoodjs#5358)
  fix(deps): update dependency @types/node to v16.11.28 (redwoodjs#5326)
  update all contributors (redwoodjs#5357)
  Patch all-contributors-cli (redwoodjs#5356)
  Remove unused `SubmitHandler` in example JavaScript code (redwoodjs#5352)
  Use GraphQL Codegen to generate more accurate resolver types (redwoodjs#5216)
  chore(deps): update dependency @clerk/clerk-sdk-node to v3.3.8 (redwoodjs#5345)
  fix(deps): update dependency jest-watch-typeahead to v1.1.0 (redwoodjs#5339)
  Update yarn.lock
  ...
jtoar pushed a commit that referenced this pull request May 3, 2022
@jtoar jtoar modified the milestones: next-release, v1.3.0 May 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release:chore This PR is a chore (means nothing for users)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants