[Snyk] Upgrade @sentry/react from 7.16.0 to 8.30.0 #909
Conversation
Snyk has created this PR to upgrade @sentry/react from 7.16.0 to 8.30.0. See this package in npm: @sentry/react See this project in Snyk: https://app.snyk.io/org/q1blue-rxw/project/5b430cad-b455-40c7-a7ff-af5a8804e8ca?utm_source=github&utm_medium=referral&page=upgrade-pr
|
|
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again.
Next stepsWhat is a critical CVE?Contains a Critical Common Vulnerability and Exposure (CVE). Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Take a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with
|
Snyk has created this PR to upgrade @sentry/react from 7.16.0 to 8.30.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 205 versions ahead of your current version.
The recommended version was released on 21 days ago.
Release notes
Package name: @sentry/react
Important Changes
kafkajsintegration (#13528)This release adds a new integration that instruments
kafkajslibrary with spans and traces. This integration isautomatically enabled by default, but can be included with the
Sentry.kafkaIntegration()import.Other Changes
@ opentelemetry/instrumentation-undicifor fetch tracing (#13485)trackComponentslist matches components with or without<>(#13543)Work in this release was contributed by @ Zen-cronic and @ odanado. Thank you for your contributions!
Important Changes
This release marks the beta releases of the
@ sentry/solidand@ sentry/solidstartSentry SDKs. For details on how touse them, check out the
Sentry Solid SDK README and the
Sentry SolidStart SDK README
respectively. Please reach out on GitHub if you have
any feedback or concerns.
Adds the SDK option to only wrap ES modules with
import-in-the-middlethat specifically need to be instrumented.Sentry.init({
dsn: 'PUBLIC_DSN',
registerEsmLoaderHooks: { onlyIncludeInstrumentedModules: true },
});
All internal OpenTelemetry instrumentation was updated to their latest version. This adds support for Mongoose v7 and v8
and fixes various bugs related to ESM mode.
Other Changes
generic-poolintegration (#13465)browserTracingIntegrationby default (#13561)sentrySolidStartViteplugin to simplify source maps upload (#13493)context.waitUntilcall in request handler (#13549)generic-poolspan origins with underscores (#13579)Work in this release was contributed by @ Zen-cronic. Thank you for your contribution!
Important Changes
This release contains the beta version of
@ sentry/nestjs! For details on how to use it, check out theREADME. Any feedback/bug reports
are greatly appreciated, please reach out on GitHub.
This release fixes a bug in the
@ sentry/browserpackage and all SDKs depending on this package (e.g.@ sentry/reactor
@ sentry/nextjs) that caused the SDK to send incorrect web vital values for the LCP, FCP and FP vitals. The SDKpreviously incorrectly processed the original values as they were reported from the browser. When updating your SDK to
this version, you might experience an increase in LCP, FCP and FP values, which potentially leads to a decrease in your
performance score in the Web Vitals Insights module in Sentry. This is because the previously reported values were
smaller than the actually measured values. We apologize for the inconvenience!
Other Changes
SentryGlobalGraphQLFilter(#13545)bundleSizeOptimizationsto build options (#13323)captureRequestError(#13550)@ Injectable(#13544)Work in this release was contributed by @ leopoldkristjansson, @ mhuggins and @ filips123. Thank you for your
contributions!
Important Changes
fix(nestjs): Exception filters in main app module are not being executed (#13278)
With this release nestjs error monitoring is no longer automatically set up after adding the
SentryModuleto yourapplication, which led to issues in certain scenarios. You will now have to either add the
SentryGlobalFiltertoyour main module providers or decorate the
catch()method in your existing global exception filters with the newlyreleased
@ WithSentry()decorator. See the docs formore details.
Other Changes
Deno.permissions.querySync(#13378)Work in this release was contributed by @ charpeni. Thank you for your contribution!
Important Changes
feat(node): Add
fsInstrumentation(#13291)This release adds
fsIntegration, an integration that instruments thefsAPI to the Sentry Node SDK. Theintegration creates spans with naming patterns of
fs.readFile,fs.unlink, and so on.This integration is not enabled by default and needs to be registered in your
Sentry.initcall. You can configurevia options whether to include path arguments or error messages as span attributes when an fs call fails:
WARNING: This integration may add significant overhead to your application. Especially in scenarios with a lot of
file I/O, like for example when running a framework dev server, including this integration can massively slow down
your application.
Other Changes
feat(browser): Add spotlightBrowser integration (#13263)
feat(browser): Allow sentry in safari extension background page (#13209)
feat(browser): Send CLS as standalone span (experimental) (#13056)
feat(core): Add OpenTelemetry-specific
getTraceDataimplementation (#13281)feat(nextjs): Always add
browserTracingIntegration(#13324)feat(nextjs): Always transmit trace data to the client (#13337)
feat(nextjs): export SentryBuildOptions (#13296)
feat(nextjs): Update
experimental_captureRequestErrorto reflectRequestInfo.pathchange in Next.js canary(#13344)
feat(nuxt): Always add tracing meta tags (#13273)
feat(nuxt): Set transaction name for server error (#13292)
feat(replay): Add a replay-specific logger (#13256)
feat(sveltekit): Add bundle size optimizations to plugin options (#13318)
feat(sveltekit): Always add browserTracingIntegration (#13322)
feat(tracing): Make long animation frames opt-out (#13255)
fix(astro): Correctly extract request data (#13315)
fix(astro): Only track access request headers in dynamic page requests (#13306)
fix(nuxt): Add import line for disabled
autoImport(#13342)fix(nuxt): Add vue to excludeEsmLoaderHooks array (#13346)
fix(opentelemetry): Do not overwrite http span name if kind is internal (#13282)
fix(remix): Ensure
originis correctly set for remix server spans (#13305)Work in this release was contributed by @ MonstraG, @ undead-voron and @ Zen-cronic. Thank you for your contributions!
Important Changes
This release contains the alpha version of
@ sentry/solidstart, our SDK for Solid Start!For details on how to use it, please see the README. Any feedback/bug reports are
greatly appreciated, please reach out on GitHub.
Other Changes
bundleSizeOptimizationsvite options to integration (#13250)getTraceMetaTagsfunction (#13201)useOperationNameForRootSpantographqlIntegration(#13248)wrapServerRouteWithSentrywrapper (#13247)contextoverevent(#13266)defaultIntegrations: undefined(#13261)Bundle size 📦