This release contains the beta version of @sentry/nestjs! For details on how to use it, check out the
README. Any feedback/bug reports
are greatly appreciated, please reach out on GitHub.
fix(browser): Remove faulty LCP, FCP and FP normalization logic (#13502)
This release fixes a bug in the @sentry/browser package and all SDKs depending on this package (e.g. @sentry/react
or @sentry/nextjs) that caused the SDK to send incorrect web vital values for the LCP, FCP and FP vitals. The SDK
previously 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!
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 SentryModule to your
application, which led to issues in certain scenarios. You will now have to either add the SentryGlobalFilter to
your main module providers or decorate the catch() method in your existing global exception filters with the newly
released @WithSentry() decorator. See the docs for
more details.
This release contains the beta version of @sentry/nestjs! For details on how to use it, check out the
README. Any feedback/bug reports
are greatly appreciated, please reach out on GitHub.
fix(browser): Remove faulty LCP, FCP and FP normalization logic (#13502)
This release fixes a bug in the @sentry/browser package and all SDKs depending on this package (e.g. @sentry/react
or @sentry/nextjs) that caused the SDK to send incorrect web vital values for the LCP, FCP and FP vitals. The SDK
previously 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!
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 SentryModule to your
application, which led to issues in certain scenarios. You will now have to either add the SentryGlobalFilter to
your main module providers or decorate the catch() method in your existing global exception filters with the newly
released @WithSentry() decorator. See the docs for
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot]
commented
6 days ago
Bumps @sentry/node from 7.119.0 to 8.28.0.
Release notes
Sourced from
@sentry/node's releases.... (truncated)
Changelog
Sourced from
@sentry/node's changelog.... (truncated)
Commits
e78f15erelease: 8.28.0f834625Merge pull request #13560 from getsentry/prepare-release/8.28.0c2258fbmeta: Update CHANGELOG for 8.28.09e585e7Merge branch 'develop' into prepare-release/8.28.09b8f9eafix(nestjs): Ensure exception and host are correctly passed on when using@Wi...e8ed7c2Merge remote-tracking branch 'origin/master' into prepare-release/8.28.05605401meta: Update CHANGELOG for 8.28.0c9c346cref: Add external contributor to CHANGELOG.md (#13552)a8ff09fchore(nestjs): Add note aboutSentryGlobalGraphQLFilterin nestjs README (#...83864fachore(nestjs): Promote NestJS SDK to beta state (Readme) (#13521)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show