v1.3.0

• feat: Bump @sentry/* ~5.13.2

v1.2.1

• Add Support for Electron 8

v1.2.0

• meta: Update dependencies
• fix: Fixed location for win-ca write path
• feat: Allow usage without remote module
• ref: Use electron-fetch again
• fix: Add try/catch for decode

v1.1.0

• meta: Update dependencies
• feat: Support electron 7

v1.1.0-beta.0

• meta: Update dependencies
• fix: Use crashpad logic for Electron >= v6 on Windows
• fix: Use node-fetch rather than electron-fetch
• feat: Use win-ca to load Windows root CA's to give same behaviour as electron-fetch
• meta: Use Sentry logger to trace some caught exceptions

v1.0.0

A lot of internal changes making use of the latest 5.x relesase of the Browser/Node SDK.

Breaking: We persist scope data to disk in case of a native crash. Since the internal scope data changed, existing
scope data is not compatible with the new format. When upgrading to 1.x.x, existing scope data will be wiped on disk.
This only affects your app if the update occurs immediately after a crash, in which case this single event will not have
scope data attached.

• Feat: Bump @sentry/* ~5.7.1

v0.17.4

• meta: Empty release for latest npm tag

v0.17.3

• Fix: Remove webpack:/ part of base path in normalize

v0.17.2

• Fix: Add device.family and browser.name context
• Fix: undefined event_id #171

v0.17.1

• Fix electron-fetch dependency/ fixing windows crash reports #165