[Snyk] Upgrade @sentry/tracing from 7.45.0 to 7.46.0 #511
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.
Snyk has created this PR to upgrade @sentry/tracing from 7.45.0 to 7.46.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
Release notes
Package name: @sentry/tracing
Important Changes
sentryHandle
(#7598)This release adds support for Performance Monitoring in our SvelteKit SDK for the client/server. We've also changed how you should initialize your SDK. Please read our updated SvelteKit README instructions for more details.
ignoreTransactions
option (#7594)You can now easily filter out certain transactions from being sent to Sentry based on their name.
We've added an integration that automatically instruments Undici and Node server side fetch. This supports Undici
v4.7.0
or higher and requires Nodev16.7.0
or higher. After adding the integration outgoing requests made by Undici will have associated spans and breadcrumbs in Sentry.In our Next.js and SvelteKit SDKs, this integration is automatically added.
We've added a new middleware for trpc that automatically adds TRPC information to Sentry transactions. This middleware is meant to be used in combination with a Sentry server integration (Next.js, Express, etc).
import * as Sentry from '@ sentry/node';
const t = initTRPC.context().create();
const sentryMiddleware = t.middleware(
Sentry.Handlers.trpcMiddleware({
attachRpcInput: true,
}),
);
const sentrifiedProcedure = t.procedure.use(sentryMiddleware);
@ sentry/tracing
packageWith
7.46.0
you no longer require the@ sentry/tracing
package to use tracing and performance monitoring with the Sentry JavaScript SDKs. The@ sentry/tracing
package will be removed in a future major release, but can still be used with no changes.Please see the Migration docs for more details.
LocalVariables
integration (#7637)This fixes a memory leak in the opt-in
LocalVariables
integration, which adds local variables to the stacktraces sent to Sentry. The minimum recommended version to use theLocalVariables
is now7.46.0
.Additional Features and Fixes
responseStatus
,decodedBodySize
to perf entries (#7613)pageload
transaction starts at timeOrigin (#7632)abs_path
from stack trace (reverting #7167) (#7623)NEXT_NOT_FOUND
andNEXT_REDIRECT
errors (#7642)abs_path
frames (#7619)beforeFiles
in rewrites (#7649)Work in this release contributed by @ aldenquimby and @ bertho-zero. Thank you for your contributions!
Bundle size 📦
Read more
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs