feat(browser): Mark errors caught from TryCatch integration as unhandled (#8890)
feat(integrations): Mark errors caught from HttpClient and CaptureConsole integrations as unhandled (#8891)
feat(nextjs): Mark errors caught from NextJS wrappers as unhandled (#8893)
feat(react): Mark errors captured from ErrorBoundary as unhandled (#8914)
feat(remix): Mark errors caught from Remix instrumentation as unhandled (#8894)
feat(serverless): Mark errors caught in Serverless handlers as unhandled (#8907)
feat(vue): Mark errors caught by Vue wrappers as unhandled (#8905)
This release fixes inconsistent behaviour of when our SDKs classify captured errors as unhandled.
Previously, some of our instrumentations correctly set unhandled, while others set handled.
Going forward, all errors caught automatically from our SDKs will be marked as unhandled.
If you manually capture errors (e.g. by calling Sentry.captureException), your errors will continue to be reported as handled.
This change might lead to a decrease in reported crash-free sessions and consequently in your release health score.
If you have concerns about this, feel free to open an issue.
Other Changes
feat(node-experimental): Implement new performance APIs (#8911)
feat(node-experimental): Sync OTEL context with Sentry AsyncContext (#8797)
feat(replay): Allow to configure maxReplayDuration (#8769)
feat(remix): Add debugid injection and map deletion to sourcemaps script (#8814)
fix(browser): Add replay and profiling options to BrowserClientOptions (#8921)
fix(browser): Check for existence of instrumentation targets (#8939)
fix(nextjs): Don't re-export default in route handlers (#8924)
feat(browser): Mark errors caught from TryCatch integration as unhandled (#8890)
feat(integrations): Mark errors caught from HttpClient and CaptureConsole integrations as unhandled (#8891)
feat(nextjs): Mark errors caught from NextJS wrappers as unhandled (#8893)
feat(react): Mark errors captured from ErrorBoundary as unhandled (#8914)
feat(remix): Add debugid injection and map deletion to sourcemaps script (#8814)
feat(remix): Mark errors caught from Remix instrumentation as unhandled (#8894)
feat(serverless): Mark errors caught in Serverless handlers as unhandled (#8907)
feat(vue): Mark errors caught by Vue wrappers as unhandled (#8905)
This release fixes inconsistent behaviour of when our SDKs classify captured errors as unhandled.
Previously, some of our instrumentations correctly set unhandled, while others set handled.
Going forward, all errors caught automatically from our SDKs will be marked as unhandled.
If you manually capture errors (e.g. by calling Sentry.captureException), your errors will continue to be reported as handled.
This change might lead to a decrease in reported crash-free sessions and consequently in your release health score.
If you have concerns about this, feel free to open an issue.
Other Changes
feat(node-experimental): Implement new performance APIs (#8911)
feat(node-experimental): Sync OTEL context with Sentry AsyncContext (#8797)
feat(replay): Allow to configure maxReplayDuration (#8769)
fix(browser): Add replay and profiling options to BrowserClientOptions (#8921)
fix(browser): Check for existence of instrumentation targets (#8939)
fix(nextjs): Don't re-export default in route handlers (#8924)
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)
Bumps @sentry/angular from 6.19.7 to 7.67.0.
Release notes
Sourced from
@sentry/angular
's releases.... (truncated)
Changelog
Sourced from
@sentry/angular
's changelog.... (truncated)
Commits
44e1259
release: 7.67.0a74fe81
Merge pull request #8941 from getsentry/prepare-release/7.67.009f7f7e
update changelog after rebase262da82
meta: Update CHANGELOG for 7.67.0ef51993
fix(browser): Check for existence of instrumentation targets (#8939)b57e139
fix(nextjs): Don't rexport default in route handlers (#8924)29ef20e
feat(integrations): Mark errors caught fromHttpClient
andCaptureConsole
...39401f0
feat(remix): Mark errors caught from Remix instrumentation as unhandled (#8894)b102817
feat(nextjs): Mark errors caught from NextJS wrappers as unhandled (#8893)3d8b444
feat(react): Mark errors captured from ErrorBoundary as unhandled (#8914)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