This release adds support for Remix v2 future flags, in particular for new error handling utilities of Remix v2. We heavily recommend you switch to using v2_errorBoundary future flag to get the best error handling experience with Sentry.
To capture errors from v2 client-side ErrorBoundary, you should define your own ErrorBoundary in root.tsx and use Sentry.captureRemixErrorBoundaryError helper to capture the error.
// root.tsx
import { captureRemixErrorBoundaryError } from "@sentry/remix";
For server-side errors, define a handleError function in your server entry point and use the Sentry.captureRemixServerException helper to capture the error.
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 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)
Updates the requirements on @sentry/integrations to permit the latest version.
Release notes
Sourced from
@​sentry/integrations
's releases.Changelog
Sourced from
@​sentry/integrations
's changelog.... (truncated)
Commits
e3e38dd
release: 7.59.20ec99a2
Merge pull request #8573 from getsentry/prepare-release/7.59.28299b9a
meta: Update CHANGELOG for 7.59.21b0193c
Merge pull request #8572 from getsentry/master2344e56
meta: Update CHANGELOG for 7.59.1 (#8566)3db1547
Merge pull request #8560 from getsentry/prepare-release/7.59.05eb0bdd
meta: Update CHANGELOG for 7.59.0564af01
feat(tracing): Bring http timings out of experiment (#8563)c2bd091
feat(core): Allow multiplexed transport to send to multiple releases (#8559)6b009c0
fix(tracing): Improve network.protocol.version (#8502)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 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)