Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency @sentry/browser to v7.67.0 #314

Merged
merged 1 commit into from
Sep 5, 2023
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 5, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@sentry/browser (source) 7.66.0 -> 7.67.0 age adoption passing confidence

Release Notes

getsentry/sentry-javascript (@​sentry/browser)

v7.67.0

Compare Source

Important Changes
  • feat: Mark errors caught by the SDK as unhandled
    • 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)
  • fix(node): Improve mysql integration (#​8923)
  • fix(remix): Guard against missing default export for server instrument (#​8909)
  • ref(browser): Deprecate top-level wrap function (#​8927)
  • ref(node-otel): Avoid exporting internals & refactor attribute adding (#​8920)

Work in this release contributed by @​SorsOps. Thank you for your contribution!


Configuration

📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot enabled auto-merge (rebase) September 5, 2023 22:10
@renovate renovate bot merged commit cd97f53 into main Sep 5, 2023
1 check passed
@renovate renovate bot deleted the renovate/all branch September 5, 2023 22:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants