[Snyk] Upgrade @sentry/react from 8.27.0 to 8.28.0 #425
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/react from 8.27.0 to 8.28.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 1 version ahead of your current version.
The recommended version was released on 23 days ago.
Release notes
Package name: @sentry/react
-
8.28.0 - 2024-09-03
- Beta release of official NestJS SDK
- fix(browser): Remove faulty LCP, FCP and FP normalization logic (#13502)
- feat(nestjs): Add
- feat(nestjs): Automatic instrumentation of nestjs interceptors after route execution (#13264)
- feat(nextjs): Add
- feat(nextjs): Stabilize
- feat(nuxt): Wrap config in nuxt context (#13457)
- feat(profiling): Expose profiler as top level primitive (#13512)
- feat(replay): Add layout shift to CLS replay data (#13386)
- feat(replay): Upgrade rrweb packages to 2.26.0 (#13483)
- fix(cdn): Do not mangle _metadata (#13426)
- fix(cdn): Fix SDK source for CDN bundles (#13475)
- fix(nestjs): Check arguments before instrumenting with
- fix(nestjs): Ensure exception and host are correctly passed on when using @ WithSentry (#13564)
- fix(node): Suppress tracing for transport request execution rather than transport creation (#13491)
- fix(replay): Consider more things as DOM mutations for dead clicks (#13518)
- fix(vue): Correctly obtain component name (#13484)
-
8.27.0 - 2024-08-27
-
- feat: Add options for passing nonces to feedback integration (#13347)
- feat: Add support for SENTRY_SPOTLIGHT env var in Node (#13325)
- feat(deps): bump @ prisma/instrumentation from 5.17.0 to 5.18.0 (#13327)
- feat(feedback): Improve error message for 403 errors (#13441)
- fix(deno): Don't rely on
- fix(replay): Ensure we publish replay CDN bundles (#13437)
from @sentry/react GitHub release notesImportant 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
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: