chore(deps): Update all non-major dependencies #73
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:
5.1.0
->5.2.0
9.30.0
->9.39.0
8.34.1
->8.37.0
8.34.1
->8.37.0
17.0.1
->17.2.0
9.29.0
->9.31.0
8.16.2
->8.16.3
15.8.1.100
->15.8.1.113
Release Notes
fastify/fastify-type-provider-typebox (@fastify/type-provider-typebox)
v5.2.0
Compare Source
What's Changed
node:
prefix for builtins by @Fdawgs in https://github.com/fastify/fastify-type-provider-typebox/pull/202node:
prefix to bypass require.cache call for builtins by @Fdawgs in https://github.com/fastify/fastify-type-provider-typebox/pull/209New Contributors
Full Changelog: fastify/fastify-type-provider-typebox@v5.1.0...v5.2.0
getsentry/sentry-javascript (@sentry/node)
v9.39.0
Compare Source
Important Changes
afterStartPageloadSpan
hook to improve spanId assignment on web vital spans (#16893)This PR adds a new afterStartPageloadSpan lifecycle hook to more robustly assign the correct pageload span ID to web vital spans, replacing the previous unreliable "wait for a tick" approach with a direct callback that fires when the pageload span becomes available.
This PR implements client-side parameterized routes for Next.js by leveraging an injected manifest within the existing app-router instrumentation to automatically parameterize all client-side transactions (e.g.
users/123
andusers/456
now become becomeusers/:id
).This PR changes the default behavior in the Node SDK to drop HTTP spans with 401-404 and 3xx status codes by default to reduce noise in tracing data.
Other Changes
vercel.ai.X
(#16908)disableSentryWebpackConfig
flag (#17013)tracing/errors.ts
(#16888)beforeSendLog
inconsoleSandbox
(#16968)source=route
(#16984)Work in this release was contributed by @janpapenbrock. Thank you for your contribution!
Bundle size 📦
v9.38.0
Compare Source
Important Changes
This release publishes the
@sentry/node-native
SDK.Other Changes
debug
to replacelogger
(#16906)nextHopProtocol
when adding resource spans (#16900)Bundle size 📦
v9.37.0
Compare Source
Important Changes
feat(nuxt): Parametrize SSR routes (#16843)
When requesting dynamic or catch-all routes in Nuxt, those will now be shown as parameterized routes in Sentry.
For example,
/users/123
will be shown as/users/:userId()
in Sentry. This will make it easier to identify patterns and make grouping easier.Other Changes
beforeStartNavigationSpan
lifecycle hook (#16863)wrapRequestHandler
(#16852)instrumentation-client.ts|js
(#16855)redirect()
calls as errors in Cloudflare (#16853)deleteSourcemapsAfterUpload
jsdoc default value (#16867)Work in this release was contributed by @zachkirsch. Thank you for your contribution!
Bundle size 📦
v9.36.0
Compare Source
Important Changes
This release adds a new SDK
@sentry/node-core
which ships without any OpenTelemetry instrumententation out of the box. All OpenTelemetry dependencies are peer dependencies and OpenTelemetry has to be set up manually.Use
@sentry/node-core
when:Use
@sentry/node
when:The ANR integration has been deprecated and will be removed in future versions. Use
eventLoopBlockIntegration
from@sentry/node-native
instead._experiments.ignoreMutations
option (#16816)This replay option allows to configure a selector list of elements to not capture mutations for.
Other changes
@sentry/replay-internal
(#16794)diagnoseSdkConnectivity
request (#16840)Work in this release was contributed by @Spice-King and @stayallive. Thank you for your contributions!
Bundle size 📦
v9.35.0
Compare Source
Context
andContexts
types (#16763)eventLoopBlockIntegration
(#16709)parentSpan
is considered (#16776)require
for fastify integration (#16789)@sentry/cloudflare
as optional peerDependency (#16782)@Cron
decorated tasks (#16792)Work in this release was contributed by @0xbad0c0d3 and @alSergey. Thank you for your contributions!
v9.34.0
Compare Source
Important Changes
feat(nuxt): Add Cloudflare Nitro plugin (#15597)
A Nitro plugin for
@sentry/nuxt
which initializes Sentry when deployed to Cloudflare (cloudflare-pages
preset).Remove the previous server config file:
sentry.server.config.ts
Add a plugin in
server/plugins
(e.g.server/plugins/sentry-cloudflare-setup.ts
)Add this code in your plugin file
or with access to
nitroApp
:Other Changes
Bundle size 📦
v9.33.0
Compare Source
Important Changes
vercelAiIntegration
to cloudflare & vercel-edge (#16732)The
vercelAiIntegration
is now available as opt-in for the Cloudflare and the Next.js SDK for Vercel Edge.To use it, add the integration in
Sentry.init
And enable telemetry for Vercel AI calls
The Node.js SDK now includes instrumentation for Postgres.js.
If you're on Fastify v5, you no longer need to call
setupFastifyErrorHandler
. It is done automatically by the node SDK. Older versions still rely on callingsetupFastifyErrorHandler
.Other Changes
waitUntil
(#16681)ai
from default server external packages (#16736)Work in this release was contributed by @0xbad0c0d3. Thank you for your contribution!
v9.32.0
Compare Source
Important Changes
Enhances CLS (Cumulative Layout Shift) spans by adding attributes detailing the elements that caused layout shifts.
instrumentWorkflowWithSentry
to instrument workflows (#16672)We've added support for Cloudflare Workflows, enabling comprehensive tracing for your workflow runs. This integration uses the workflow's instanceId as the Sentry trace_id and for sampling, linking all steps together. You'll now be able to see full traces, including retries with exponential backoff.
Adds the ability to send logs to Sentry via a pino transport.
Other Changes
errorHandler
option (#16718)CloudEventsContext
compatible withCloudEvent
(#16705)false
(#16695)@opentelemetry/resources
(#16727)Work in this release was contributed by @flaeppe. Thank you for your contribution!
Bundle size 📦
v9.31.0
Compare Source
Important Changes
Adds an option to automatically generate a random tunnel route for the Next.js SDK. This helps prevent ad blockers and other tools from blocking Sentry requests by using a randomized path instead of the predictable
/monitoring
endpoint.scope
&client
togetTraceData
(#16633)Adds the ability to pass custom
scope
andclient
parameters to thegetTraceData
function, providing more flexibility when generating trace data for distributed tracing.Other Changes
x-forwarded-host
andx-forwarded-proto
headers (#16687)@sentry/opentelemetry
dependency (#16677)@sentry/pino-transport
(#16652)safeJoin
usage in console logging integration (#16658)CloudEvent
type compatible (#16661)instrumentation-client.js
file (#16637)Bundle size 📦
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v8.37.0
Compare Source
🩹 Fixes
❤️ Thank You
You can read about our [versioning strategy](https://main--typescript-es
Configuration
📅 Schedule: Branch creation - "before 3am 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.