Releases · getsentry/sentry-electron

17 Oct 20:49

getsentry-bot

4.14.0

47b21bd

4.14.0

feat: Renderer process ANR detection with stack traces (#770)
- Update from v7.73.0 to
  v7.74.0 of JavaScript SDKs
fix: Hide ANR child process from dock (#777)
test: Electron v28 main process ESM (#773)

Assets 3

05 Oct 15:30

getsentry-bot

4.13.0

760ef61

4.13.0

feat: Add App Not Responding detection for main process (#753)
feat: Update from v7.68.0 to
v7.73.0 of JavaScript SDKs (#766)

Assets 3

03 Oct 13:21

getsentry-bot

4.12.0

d840e72

4.12.0

feat: Identify webContents of renderers via custom protocol (#762)
fix: Re-work Sentry minidump loader (#761)
feat: Node compatible ESM build for main process (#756)

Note: Node ESM support is in beta until Electron v28 has a beta release and can be tested with the full test suite.

Assets 3

29 Sep 13:06

getsentry-bot

4.11.1

f7d1adc

4.11.1

fix: Don't send minidumps that are too small to be valid (#748)

Assets 3

13 Sep 06:32

getsentry-bot

4.11.0

ab8b058

4.11.0

feat: Add optional BrowserWindowSession to track sessions as window in foreground (#725)
feat: Update from v7.63.0 to
v7.68.0 of JavaScript SDKs (#738)
feat: Mark errors caught by the SDK as unhandled

As per the changes in the JavaScript SDKs for
v7.67.0, 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.

Assets 3