fix(deps): update all non-major dependencies #334
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:
6.0.1
->6.1.0
18.3.16
->18.3.18
3.0.0
->3.0.2
5.3.0
->5.4.0
0.24.0
->0.24.2
15.1.0
->15.1.2
6.0.1
->6.1.0
4.30.1
->4.30.2
Release Notes
prisma/prisma (@prisma/client)
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
WillBooster/at-decorators (at-decorators)
v3.0.2
Compare Source
Bug Fixes
v3.0.1
Compare Source
Bug Fixes
chalk/chalk (chalk)
v5.4.0
Compare Source
CIRCLECI
environments to return level 3 color supportf838120
evanw/esbuild (esbuild)
v0.24.2
Compare Source
Fix regression with
--define
andimport.meta
(#4010, #4012, #4013)The previous change in version 0.24.1 to use a more expression-like parser for
define
values to allow quoted property names introduced a regression that removed the ability to use--define:import.meta=...
. Even thoughimport
is normally a keyword that can't be used as an identifier, ES modules special-case theimport.meta
expression to behave like an identifier anyway. This change fixes the regression.This fix was contributed by @sapphi-red.
v0.24.1
Compare Source
Allow
es2024
as a target intsconfig.json
(#4004)TypeScript recently added
es2024
as a compilation target, so esbuild now supports this in thetarget
field oftsconfig.json
files, such as in the following configuration file:As a reminder, the only thing that esbuild uses this field for is determining whether or not to use legacy TypeScript behavior for class fields. You can read more in the documentation.
This fix was contributed by @billyjanitsch.
Allow automatic semicolon insertion after
get
/set
This change fixes a grammar bug in the parser that incorrectly treated the following code as a syntax error:
The above code will be considered valid starting with this release. This change to esbuild follows a similar change to TypeScript which will allow this syntax starting with TypeScript 5.7.
Allow quoted property names in
--define
and--pure
(#4008)The
define
andpure
API options now accept identifier expressions containing quoted property names. Previously all identifiers in the identifier expression had to be bare identifiers. This change now makes--define
and--pure
consistent with--global-name
, which already supported quoted property names. For example, the following is now possible:Note that if you're passing values like this on the command line using esbuild's
--define
flag, then you'll need to know how to escape quote characters for your shell. You may find esbuild's JavaScript API more ergonomic and portable than writing shell code.Minify empty
try
/catch
/finally
blocks (#4003)With this release, esbuild will now attempt to minify empty
try
blocks:This can sometimes expose additional minification opportunities.
Include
entryPoint
metadata for thecopy
loader (#3985)Almost all entry points already include a
entryPoint
field in theoutputs
map in esbuild's build metadata. However, this wasn't the case for thecopy
loader as that loader is a special-case that doesn't behave like other loaders. This release adds theentryPoint
field in this case.Source mappings may now contain
null
entries (#3310, #3878)With this change, sources that result in an empty source map may now emit a
null
source mapping (i.e. one with a generated position but without a source index or original position). This change improves source map accuracy by fixing a problem where minified code from a source without any source mappings could potentially still be associated with a mapping from another source file earlier in the generated output on the same minified line. It manifests as nonsensical files in source mapped stack traces. Now thenull
mapping "resets" the source map so that any lookups into the minified code without any mappings resolves tonull
(which appears as the output file in stack traces) instead of the incorrect source file.This change shouldn't affect anything in most situations. I'm only mentioning it in the release notes in case it introduces a bug with source mapping. It's part of a work-in-progress future feature that will let you omit certain unimportant files from the generated source map to reduce source map size.
Avoid using the parent directory name for determinism (#3998)
To make generated code more readable, esbuild includes the name of the source file when generating certain variable names within the file. Specifically bundling a CommonJS file generates a variable to store the lazily-evaluated module initializer. However, if a file is named
index.js
(or with a different extension), esbuild will use the name of the parent directory instead for a better name (since many packages have files all namedindex.js
but have unique directory names).This is problematic when the bundle entry point is named
index.js
and the parent directory name is non-deterministic (e.g. a temporary directory created by a build script). To avoid non-determinism in esbuild's output, esbuild will now useindex
instead of the parent directory in this case. Specifically this will happen if the parent directory is equal to esbuild'soutbase
API option, which defaults to the lowest common ancestor of all user-specified entry point paths.Experimental support for esbuild on NetBSD (#3974)
With this release, esbuild now has a published binary executable for NetBSD in the
@esbuild/netbsd-arm64
npm package, and esbuild's installer has been modified to attempt to use it when on NetBSD. Hopefully this makes installing esbuild via npm work on NetBSD. This change was contributed by @bsiegert.vercel/next.js (next)
v15.1.2
Compare Source
v15.1.1
Compare Source
sindresorhus/type-fest (type-fest)
v4.30.2
Compare Source
527d600
SetOptional
/SetRequired
/SetReadonly
: Fix when the second argument isany
(#1007)fdbcb11
SetOptional
: Fix when instantiated with unions (#1007)fdbcb11
Configuration
📅 Schedule: Branch creation - "after 5am on Saturday" in timezone Asia/Tokyo, 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.