fix(deps): update all non-major dependencies #565
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:
7.25.9
->7.26.5
4.3.1
->4.3.3
3.9.1
->3.10.0
6.0.0
->6.2.1
8.4.6
->8.5.0
8.4.6
->8.5.0
8.4.6
->8.5.0
8.4.6
->8.5.0
0.5.15
->0.5.16
5.62.0
->5.64.1
5.62.0
->5.64.1
16.0.1
->16.2.0
18.3.12
->18.3.18
8.16.0
->8.20.0
8.16.0
->8.20.0
2.1.6
->2.1.8
10.1.2
->10.1.3
4.12.14
->4.12.23
9.16.0
->9.18.0
15.0.3
->15.1.5
2.10.3
->2.11.0
2.6.6
->2.7.0
4.24.10
->4.24.11
8.4.47
->8.5.1
8.4.49
->8.5.1
3.4.1
->3.4.2
6.0.0
->6.2.1
7.53.2
->7.54.2
2.12.0
->2.14.0
3.4.15
->3.4.17
5.7.2
->5.7.3
6.0.1
->6.0.7
2.1.6
->2.1.8
1.4.0
->1.6.1
Release Notes
babel/babel (@babel/eslint-parser)
v7.26.5
Compare Source
👓 Spec Compliance
babel-parser
import.defer()
form ofimport defer
(@babel-bot)🐛 Bug Fix
babel-plugin-transform-block-scoped-functions
isInStrictMode
in Babel 7 (@liuxingbaoyu)babel-plugin-transform-typescript
babel-parser
@(a.b)()
(@liuxingbaoyu)babel-generator
,babel-parser
,babel-plugin-transform-flow-strip-types
,babel-types
babel-compat-data
,babel-preset-env
transform-typeof-symbol
compat data (@liuxingbaoyu)babel-generator
,babel-parser
,babel-types
🔬 Output optimization
babel-plugin-transform-nullish-coalescing-operator
react-hook-form/devtools (@hookform/devtools)
v4.3.3
: Version 4.3.3Compare Source
v4.3.2
: Version 4.3.2Compare Source
react-hook-form/resolvers (@hookform/resolvers)
v3.10.0
Compare Source
Features
prisma/prisma (@prisma/client)
v6.2.1
Compare Source
Today we are releasing the 6.2.1 patch release to address an issue with some of the
omitApi
preview feature checks having been accidentally omitted when making the feature GA. Now it is fully functional without the preview feature flag.Changes
v6.2.0
Compare Source
Today we're releasing Prisma ORM version 6.2.0 🎉
🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟
We have a number of new features in this version, including support for
json
andenum
fields in SQLite, a newupdateManyAndReturn
function, support for ULID values, as well as the promotion of theomit
feature from Preview to Generally Availability.Highlights
Excluding fields via
omit
is now production-readyOur number one requested feature is out of Preview and Generally Available. In 6.2.0, you no longer need to add
omitApi
to your list of Preview features:generator client { provider = "prisma-client-js" - previewFeatures = ["omitApi"] }
As a refresher:
omit
allows you to exclude certain fields from being returned in the results of your Prisma Client queries.You can either do this locally, on a per-query level:
Or globally, to ensure a field is excluded from all queries of a certain model:
For more information on
omit
, be sure to check our documentation.json
andenum
fields in SQLitePrevious to this version, you could not define
json
andenum
fields in your Prisma schema when using SQLite. The respective GitHub issues have been among the most popular ones in our repo, so with our new approach to open-source governance, we finally got to work and implemented these.Working with JSON and Enum fields works similarly to other database providers, here’s an example:
Support for auto-generated ULID values
Similar to
cuid2
support released in ORM version 6.0.0, we are now adding support for Universally Unique Lexicographically Sortable Identifiers (or short: ULIDs 😄) in version 6.2.0. A ULID value is a 26-character alphanumeric string, e.g.01GZ0GZ3XARH8ZP44A7TQ2W4ZD
.With this new feature, you can now create records with auto-generated ULID values for
String
fields:New batch function:
updateManyAndReturn
updateMany
allows you to update many records in your database, but it only returns the count of the affected rows, not the resulting rows themselves. WithupdateManyAndReturn
you are now able to achieve this:This call to
updateManyAndReturn
will now return the actual records that have been updated in the query:Please note that like
createManyAndReturn
,updateManyAndReturn
is only supported in PostgreSQL, CockroachDB, and SQLite.Fixed runtime error in Node.js v23
While not officially supported, we understand that a lot of you like to be on the latest Node.js version — so we fixed an error that only occurred on Node.js 23. Happy coding ✌️
Prisma is hiring 🤝
Join us at Prisma to work on the most popular TypeScript ORM and other exciting products like the first serverless database built on unikernels!
We currently have two open roles in our Engineering team:
If these don’t fit, you can still check out our jobs page and send a general application.
v6.1.0
Compare Source
Today we're releasing Prisma ORM version 6.1.0
In this version our
tracing
Preview feature is being graduated to GA!Highlights
Tracing goes GA
The
tracing
Preview feature is now stable. You now no longer have to includetracing
in your set of enabled preview features.generator client { provider = "prisma-client-js" - previewFeatures = ["tracing"] }
We have also changed some of the spans generated by Prisma Client. Previously, a trace would report the following spans:
Now, the following are reported:
Additionally, we have made a few changes to our dependencies:
@opentelemetry/api
is now a peer dependency instead of a regular dependencyregisterInstrumentations
in@opentelemetry/instrumentation
is now re-exported by@prisma/instrumentation
After upgrading to Prisma ORM 6.1.0 you will need to add
@opentelemetry/api
to your dependencies if you haven't already:You will also no longer need to have
@opentelemetry/instrumentation
if you only useregisterInstrumentations
. In this case you can importregisterInstrumentations
from@prisma/instrumentation
Bug fixes
Tracing related
As we're moving our
tracing
preview to GA, a number of issues have been resolved. Here are a few highlights:suppressTracing
Other issues
We also have a number of other issues that were resolved outside of our
tracing
feature.PrismaNeonHTTP
adapterfindUnique
returnsnull
when used instead ofPromise.all
Fixes and improvements
Prisma
TypeError: parentTracer.getSpanLimits is not a function
Span
constructorprisma:engine
spans do not respectsuppressTracing()
tracing: engine
spans don't pass throughSampler
prisma:client:operation
prisma:engine
spans are missing when there are multiplenew PrismaClient()
invocationsparentTracer.getSpanLimits is not a function
opentelemetry-sdk-trace-base
(e.g. Datadog tracer)traceparent
comments with multiple SQL statements@prisma/instrumentation
dependencies peer dependenciesdb.statement
attribute doesn't include thetraceparent
commentregisterInstrumentations
uses the global provider instead of the one passed inPrismaNeonHTTP
adapter breaks on some types e.g. timestampPrisma failed to detect the libssl/openssl version to use
Prisma Client
@prisma/instrumentation
Type Error:'InstrumentionNodeModuleDefintion' is not generic
v6.0.1
Compare Source
storybookjs/storybook (@storybook/addon-actions)
v8.5.0
Compare Source
Storybook 8.5 is packed with powerful features to enhance your development workflow. This release makes it easier than ever to build accessible, well-tested UIs. Here’s what’s new:
List of all updates
@vitest/coverage-v8
during postinstall if no coverage reporter is installed - #29993, thanks @ghengeveld!vitest
detects missing deps - #29763, thanks @ndelangen!test.include
patterns - #30029, thanks @JReinhold!vitest
crashes - #29751, thanks @ndelangen!vitest.setup.js
- #30233, thanks @JReinhold!experimental-nextjs-vite
- #29814, thanks @ndelangen!glob
withtinyglobby
- #29817, thanks @ghengeveld!staticDirs
with Vitest - #29811, thanks @ghengeveld!require.resolve
- #30026, thanks @ndelangen!storybook
command - #29480, thanks @toothlessdev!Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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.