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

fix(deps): update dependency @sentry/browser to ^7.72.0 #615

Merged
merged 1 commit into from
Oct 2, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 2, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@sentry/browser (source) ^7.70.0 -> ^7.72.0 age adoption passing confidence

Release Notes

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

v7.72.0

Compare Source

Important Changes
  • feat(node): App Not Responding with stack traces (#​9079)

This release introduces support for Application Not Responding (ANR) errors for Node.js applications.
These errors are triggered when the Node.js main thread event loop of an application is blocked for more than five seconds.
The Node SDK reports ANR errors as Sentry events and can optionally attach a stacktrace of the blocking code to the ANR event.

To enable ANR detection, import and use the enableANRDetection function from the @sentry/node package before you run the rest of your application code.
Any event loop blocking before calling enableANRDetection will not be detected by the SDK.

Example (ESM):

import * as Sentry from "@​sentry/node";

Sentry.init({
  dsn: "___PUBLIC_DSN___",
  tracesSampleRate: 1.0,
});

await Sentry.enableANRDetection({ captureStackTrace: true });
// Function that runs your app
runApp();

Example (CJS):

const Sentry = require("@​sentry/node");

Sentry.init({
  dsn: "___PUBLIC_DSN___",
  tracesSampleRate: 1.0,
});

Sentry.enableANRDetection({ captureStackTrace: true }).then(() => {
  // Function that runs your app
  runApp();
});
Other Changes
  • fix(nextjs): Filter RequestAsyncStorage locations by locations that webpack will resolve (#​9114)
  • fix(replay): Ensure replay_id is not captured when session is expired (#​9109)

v7.71.0

Compare Source

  • feat(bun): Instrument Bun.serve (#​9080)
  • fix(core): Ensure global event processors are always applied to event (#​9064)
  • fix(core): Run client eventProcessors before global ones (#​9032)
  • fix(nextjs): Use webpack module paths to attempt to resolve internal request async storage module (#​9100)
  • fix(react): Add actual error name to boundary error name (#​9065)
  • fix(react): Compare location against basename-prefixed route. (#​9076)
  • ref(browser): Refactor browser integrations to use processEvent (#​9022)

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


Configuration

📅 Schedule: Branch creation - "before 5am on monday" in timezone Europe/Vienna, 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 added the dependencies label Oct 2, 2023
@renovate renovate bot enabled auto-merge October 2, 2023 00:28
@renovate renovate bot merged commit fd38ea6 into master Oct 2, 2023
24 checks passed
@renovate renovate bot deleted the renovate/sentry-javascript-monorepo branch October 2, 2023 00:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants