fix(deps): update all non-major dependencies #317
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^4.12.0
->^4.13.0
18.15.11
->18.15.13
5.58.0
->5.59.0
5.58.0
->5.59.0
8.38.0
->8.39.0
4.12.0
->4.13.0
Release Notes
prisma/prisma
v4.13.0
Compare Source
🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟
Highlights
Introspection stopgaps
The Prisma Schema Language (PSL) currently doesn't support all database features and functionality of our target databases. The PSL is an abstraction over SQL and will keep evolving to address gaps in our database feature matrix.
Before this release,
prisma db pull
did not pick up the unsupported features in a database. It was easy to lose them when runningprisma migrate dev
based on an existing Prisma schema if not included in a migration file using custom migrations.To avoid this, we added Introspection Stopgaps that surface the existence of these features in your database and link to our documentation on how to manually work around the Prisma Schema with unsupported database features (”Stopgaps” as we will remove them as soon as we implement full support for these features).
In this release, we added stopgaps for the following features:
NULLS FIRST
/NULLS LAST
Prisma CLI will output warnings on introspection (
prisma db pull
) and add comments to your Prisma schema. In the coming releases, we will expand this to many more features labeled withtopic: database-functionality
on GitHub.Improved support for Netlify and Vercel build process
Netlify and Vercel cache project dependencies during the build process and reuse that cache until dependencies change. While this helps speed up the build process, any
postinstall
scripts of these dependencies will not be executed.Prisma uses a
postinstall
script in its package to automatically trigger the customized generation of Prisma Client for your Prisma Schema. When a dependency cache is used, that generation process is not triggered, and an outdated Prisma Client may be used in your application.When you update your Prisma Schema but not your dependencies, Prisma Client will not be generated for the new schema. For example, columns you added recently to one of your models will not be present in the Prisma Client API - causing errors.
This problem can be avoided by:
postinstall
script in yourpackage.json
fileprisma generate
step to the “Build” scripts of Vercel and Netlify.We now added detection of this scenario and will prevent a build without an additional
prisma generate
. This will ensure you're aware of the problem early and get guidance on how to fix this problem. You can read more on how to do this in our docs — Vercel caching troubleshooting, Netlify caching troubleshooting.Better support for pnpm as a package manager
Before this release, Prisma only used npm scripts which would lead to undesirable behavior for a project using a different package manager such as pnpm and yarn. This release improves the detection of the package managers in your project by using
ni
. If you're still running into this problem, let us know by creating a GitHub issue.Segmentation fault and TLS connection error fix
In this release, we've fixed a TLS connection error segmentation fault. This mostly affected users running on Node.js 17 or later with OpenSSL 1.1 when using TLS to connect to their database.
JSON protocol Preview feature feedback
We have fixed multiple bugs for the
jsonProtocol
Preview feature and are close to making it Generally Available. We are still looking for feedback about its usage to ensure it is ready and works as expected for everyone.We would appreciate it if you would try it out, help us polish the feature, and move it to General Availability. Testing it requires little effort. You can test it using the following steps:
jsonProtocol
Preview feature in your Prisma schemaWe encourage you to leave your feedback in this GitHub issue or create a bug report if your run into any issues.
Fixes and improvements
Prisma Client
prisma generate
fails when using pnpm workspaces because it tries to install prisma dependencies with npm or yarnnode_modules
cache that contains generated Clientprisma generate
when@prisma/client
is not installed in projectpnpm install
hangs on@prisma/client
postinstallPrisma Migrate
Language tools (e.g. VS Code)
[object Object]
output in logging isn't helpfulCredits
Huge thanks to @KhooHaoYit, @rintaun, @maxmartynov, @haneenmahd for helping!
📺 Join us for another "What's new in Prisma" live stream
Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" live stream.
The stream takes place on YouTube on Thursday, April 20 at 5 pm Berlin | 8 am San Francisco.
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v5.59.0
Compare Source
Bug Fixes
Features
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v5.59.0
Compare Source
Note: Version bump only for package @typescript-eslint/parser
eslint/eslint
v8.39.0
Compare Source
Features
3f7af9f
feat: ImplementSourceCode#markVariableAsUsed()
(#17086) (Nicholas C. Zakas)Documentation
6987dc5
docs: Fix formatting in Custom Rules docs (#17097) (Milos Djermanovic)4ee92e5
docs: Update README (GitHub Actions Bot)d8e9887
docs: Custom Rules cleanup/expansion (#16906) (Ben Perlmutter)1fea279
docs: Clarify how to add to tsc agenda (#17084) (Nicholas C. Zakas)970ef1c
docs: Update triage board location (Nicholas C. Zakas)6d8bffd
docs: Update README (GitHub Actions Bot)Chores
60a6f26
chore: upgrade @eslint/js@8.39.0 (#17102) (Milos Djermanovic)d5ba5c0
chore: package.json update for @eslint/js release (ESLint Jenkins)f57eff2
ci: run tests on Node.js v20 (#17093) (Nitin Kumar)9d1b8fc
perf: Binary search in token storeutils.search
(#17066) (Francesco Trotta)07a4435
chore: Add request for minimal repro to bug report (#17081) (Nicholas C. Zakas)eac4943
refactor: remove unnecessary use ofSourceCode#getAncestors
in rules (#17075) (Milos Djermanovic)0a7b60a
chore: update description ofSourceCode#getDeclaredVariables
(#17072) (Milos Djermanovic)6e2df71
chore: remove unnecessary references to the LICENSE file (#17071) (Milos Djermanovic)Configuration
📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.
This PR has been generated by Mend Renovate. View repository job log here.