[Snyk] Upgrade @sentry/vue from 7.74.1 to 8.13.0 #30
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 was automatically created by Snyk using the credentials of a real user.
![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)
Snyk has created this PR to upgrade @sentry/vue from 7.74.1 to 8.13.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.
The recommended version is 91 versions ahead of your current version.
The recommended version was released on 25 days ago.
Issues fixed by the recommended upgrade:
SNYK-JS-AXIOS-6032459
SNYK-JS-AXIOS-6144788
SNYK-JS-BRACES-6838727
SNYK-JS-FOLLOWREDIRECTS-6141137
SNYK-JS-MICROMATCH-6838728
SNYK-JS-VITE-6182924
SNYK-JS-VITE-6531286
SNYK-JS-AXIOS-6124857
SNYK-JS-DOMPURIFY-6474511
SNYK-JS-FOLLOWREDIRECTS-6444610
SNYK-JS-VITE-6098386
Release notes
Package name: @sentry/vue
Important Changes
@ sentry/nestjs
)in alpha state. The SDK is a drop-in replacement for the Sentry Node SDK (
@ sentry/node
) supporting the same set offeatures. See the docs for how to use the SDK.
Other Changes
2.20.1
(#12641)Bundle size 📦
Important Changes
This release introduces breaking changes to the
@ sentry/solid
package (which is currently out in alpha).We've made it easier to get started with the solid router integration by removing the need to pass use* hooks
explicitly to
solidRouterBrowserTracingIntegration
. ImportsolidRouterBrowserTracingIntegration
from@ sentry/solid/solidrouter
and add it toSentry.init
import { solidRouterBrowserTracingIntegration, withSentryRouterRouting } from '@ sentry/solid/solidrouter';
import { Router } from '@ solidjs/router';
Sentry.init({
dsn: 'PUBLIC_DSN',
integrations: [solidRouterBrowserTracingIntegration()],
tracesSampleRate: 1.0, // Capture 100% of the transactions
});
const SentryRouter = withSentryRouterRouting(Router);
Sentry.init()
now returns a client directly, so you don't need to explicitly callgetClient()
anymore:deleteSourcemapsAfterUpload
option (#12457)This adds an easy way to delete sourcemaps immediately after uploading them:
maxSpanWaitDuration
(#12610)Adds configuration option for the max. duration in seconds that the SDK will wait for parent spans to be finished before
discarding a span. The SDK will automatically clean up spans that have no finished parent after this duration. This is
necessary to prevent memory leaks in case of parent spans that are never finished or otherwise dropped/missing. However,
if you have very long-running spans in your application, a shorter duration might cause spans to be discarded too early.
In this case, you can increase this duration to a value that fits your expected data.
Other Changes
window.Sentry
(#12580)isRemixV2
as optional in exposed types. (#12614)Work in this release was contributed by @ n4bb12. Thank you for your contribution!
Bundle size 📦
This pre-release includes an
rrweb
version bump thatincludes quite a few upstream changes. We will test this on Sentry before a release.
Bundle size 📦
Important Changes
parentSpan
option tostartSpan*
APIs (#12567)We've made it easier to create a span as a child of a specific span via the startSpan* APIs. This should allow you to
explicitly manage the parent-child relationship of your spans better.
const span = Sentry.startInactiveSpan({ name: 'xxx', parentSpan: parent });
Sentry.startSpan({ name: 'xxx', parentSpan: parent }, () => {});
Sentry.startSpanManual({ name: 'xxx', parentSpan: parent }, () => {});
});
Other Changes
@ sentry/node
exports from framework SDKs. (#12589)Bundle size 📦
Important
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: