⬆️(dependencies) update js dependencies #1375
Open
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.
Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.
This PR contains the following updates:
0.37.0
->0.39.1
0.37.0
->0.39.1
0.37.0
->0.39.1
0.37.0
->0.39.1
0.37.0
->0.39.1
0.37.0
->0.39.1
0.37.0
->0.39.1
0.37.0
->0.39.1
5.2.5
->5.2.6
10.11.0
->10.12.0
10.11.0
->10.12.0
10.11.0
->10.12.0
5.86.0
->5.89.0
5.87.4
->5.89.0
5.87.4
->5.89.0
22.18.1
->22.18.6
19.1.12
->19.1.13
8.43.0
->8.44.0
8.43.0
->8.44.0
5.0.2
->5.0.3
1.0.1
->1.3.12
1.12.0
->1.12.2
9.35.0
->9.36.0
7.6.8
->7.8.0
26.1.0
->27.0.0
4.15.3
->4.16.1
1.264.2
->1.266.2
1.12.1
->1.12.2
29.4.1
->29.4.4
Release Notes
TypeCellOS/BlockNote (@blocknote/code-block)
v0.39.1
Compare Source
🩹 Fixes
❤️ Thank You
v0.39.0
Compare Source
🚀 Features
❤️ Thank You
v0.38.0
Compare Source
🚀 Features
🩹 Fixes
❤️ Thank You
fontsource/font-files (@fontsource/material-icons)
v5.2.6
Compare Source
getsentry/sentry-javascript (@sentry/nextjs)
v10.12.0
Compare Source
Important Changes
ref: Add and Adjust error event
mechanism
valuesThis release includes a variety of changes aimed at setting the
mechanism
field on errors captured automatically by the Sentry SDKs. The intention is to clearly mark which instrumentation captured an error. In addition, some instrumentations previously did not yet annotate the error as handled or unhandled which this series of PRs corrects as well.Relevant PRs
Released in
10.12.0
:mechanism
on error events captured by astro middleware (#17613)mechanism
of errors captured in Bun.serve (#17616)mechanisms
and durable object origin (#17618)mechanism
incaptureConsoleIntegration
(#17633)mechanism
(#17622)linkedErrors
mechanism logic (#17600)mechanism
of errors caught byglobalHandlersIntegration
(#17635)mechanism
s (#17543)mechanism
to cron instrumentations (#17544)mechanism.type
to worker thread errors fromchildProcessIntegration
(#17578)mechanism
ofonUnhandledRejection
andonUnhandledException
integrations (#17636)mechanism.type
in error events (#17599)reactErrorHandler
and adjust mechanism inErrorBoundary
(#17602)captureRemixServerException
(#17629)replayIntegration
in debug mode (#17606)mechanism
to error captured bywithSentryErrorBoundary
(#17607)mechanism
of error events (#17646)Released in
10.11.0
:mechanism.type
to errors captured byhttpClientIntegration
(#17254)mechanism.type
inbrowserApiErrorsIntergation
(#17251)mechanism.type
totrpcMiddleware
errors (#17287)mechanism
s and span origins toopenAiIntegration
(#17288)mechanism
to captured errors (#17312)prismaIntegration
works with Prisma 5 (#17595)We used to require to pass in the v5 version of
@prisma/instrumentation
intoprismaIntegration({ prismaInstrumentation: new PrismaInstrumentation() })
, if you wanted to get full instrumentation for Prisma v5. However, it turns out this does not work on v10 of the SDK anymore, because@prisma/instrumentation@5
requires OTEL v1.With this release, we dropped the requirement to configure anything to get v5 support of Prisma. You do not need to configure anything in the integration anymore, and can remove the dependency on
@prisma/instrumentation@5
if you had it in your application. You only need to configure thetracing
preview feature according to our docs.Other Changes
TracesSamplerSamplingContext
type (#17523)prismaIntegration
works with Prisma v5 (#17595)parentSpanId
stays consistent during trace in TwP mode (#17526)step.do
(#17582)_platform
properties in Nitro 2.11.7+ (#17596)shimmer
(#17597) - ref(nuxt): Add and adjustmechanism.type
in error events (#17599)fetchTransport
error handling (#17661)Internal Changes
.claude/settings.local.json
to.claude/settings.json
(#17591)flushIfServerless
test (#17610)Bundle size 📦
TanStack/query (@tanstack/eslint-plugin-query)
v5.89.0
Compare Source
Version 5.89.0 - 9/16/25, 8:27 AM
Changes
Feat
a2151d2
) by JoshChore
a071bc9
(#9627) (0e99327
) by renovate[bot]Packages
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v8.44.0
Compare Source
🚀 Features
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v8.44.0
Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
vitejs/vite-plugin-react (@vitejs/plugin-react)
v5.0.3
Compare Source
HMR did not work for components imported with queries with rolldown-vite (#872)
Perf: simplify refresh wrapper generation (#835)
vitest-dev/eslint-plugin-vitest (@vitest/eslint-plugin)
v1.3.12
Compare Source
v1.3.10
Compare Source
v1.3.9
Compare Source
v1.3.8
Compare Source
v1.3.7
Compare Source
v1.3.6
Compare Source
v1.3.5
Compare Source
Bug Fixes
Features
What's Changed
New Contributors
Full Changelog: vitest-dev/eslint-plugin-vitest@v1.3.4...v1.3.5
v1.3.4
Compare Source
v1.3.3
Compare Source
v1.3.2
Compare Source
v1.3.1
Compare Source
v1.3.0
: v1.3.3Compare Source
What's Changed
prefer-called-once
by @AntonioVentilii in #727warn-todo
by @Shinigami92 in #732vitest/prefer-expect-assertions
by @steveluscher in #731New Contributors
Full Changelog: vitest-dev/eslint-plugin-vitest@v1.2.7...v1.3.0
v1.2.7
Compare Source
v1.2.5
Compare Source
v1.2.4
Compare Source
v1.2.3
Compare Source
What's Changed
no-importing-from-vitest-globals
andprefer-importing-from-vitest-globals
rules by @samuelko123 in #711New Contributors
Full Changelog: vitest-dev/eslint-plugin-vitest@v1.2.2...v1.2.3
v1.2.2
Compare Source
Bug Fixes
v1.2.1
Compare Source
Bug Fixes
What's Changed
Full Changelog: vitest-dev/eslint-plugin-vitest@v1.2.0...v1.2.1
v1.2.0
Compare Source
What's Changed
Full Changelog: vitest-dev/eslint-plugin-vitest@v1.1.44...v1.2.0
v1.1.44
Compare Source
What's Changed
New Contributors
Full Changelog: vitest-dev/eslint-plugin-vitest@v1.1.43...v1.1.44
v1.1.43
Compare Source
Features
What's Changed
Full Changelog: vitest-dev/eslint-plugin-vitest@v1.1.42...v1.1.43
v1.1.42
Compare Source
What's Changed
Full Changelog: vitest-dev/eslint-plugin-vitest@v1.1.40...v1.1.42
v1.1.40
Compare Source
v1.1.39
[Compare Source](https://redirect.github.com/vitest-dev
Configuration
📅 Schedule: Branch creation - "before 7am on monday" (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.