fix(deps): update all non-major dependencies #133
+456
−446
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:
6.16.2
->6.16.3
6.17.0
6.16.2
->6.16.3
6.17.0
22.18.6
->22.18.7
22.18.8
5.0.1
->5.1.0
v3.30.6
->v3.30.7
6.16.2
->6.16.3
6.17.0
5.9.2
->5.9.3
8.44.1
->8.45.0
8.46.0
Release Notes
prisma/prisma (@prisma/client)
v6.16.3
Compare Source
Today, we are issuing a 6.16.3 patch release focused on bug fixes.
🛠 Fixes
Prisma Client (
prisma-client
generator): fixed missing JSON null type definitions (JsonNull
,DbNull
,AnyNull
) in thebrowser.ts
entrypoint. (#28186)Prisma Migrate: don't add the default schema (namespace) to the generated migrations unless it was specified explicitly in the schema file. This restores the pre-6.13.0 behaviour that was inadvertently changed with enabling multi-schema support by default. Users who rely on database schemas for multi-tenancy can now again use the same migration files for all of their schemas. (prisma/prisma-engines#5614)
Prisma Client: enabled negative
take
withfindFirst
again. (prisma/prisma-engines#5616 — contributed by @jay-l-e-e)Prisma Accelerate: aligned the behaviour of the new Rust-free client with Query Engine to handle self-signed certificates consistently and ensure backward compatibility. (#28134)
@prisma/adapter-mariadb
: fixed error event listeners leak. (#28177 — contributed by @Tiaansu)The fix introduces the missing types, but the singleton instances differ between the client and browser entrypoints of the generated client. This means that values like
Prisma.JsonNull
imported from browser cannot yet be assigned to fields expected from the client entrypoint, and vice versa. This results in confusing TypeScript errors if you mix them. A follow-up improvement is planned to unify these utility types across entrypoints.fastify/fastify-plugin (fastify-plugin)
v5.1.0
Compare Source
What's Changed
New Contributors
Full Changelog: fastify/fastify-plugin@v5.0.1...v5.1.0
github/codeql-action (github/codeql-action)
v3.30.7
Compare Source
microsoft/TypeScript (typescript)
v5.9.3
Compare Source
typescript-eslint/typescript-eslint (typescript-eslint)
v8.45.0
Compare Source
This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
Configuration
📅 Schedule: Branch creation - "on Sunday" (UTC), 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.