Sentry

----

- The ``message`` attribute on Event/Group is now purely used for search storage.
- The ``sentry.interfaces.Message`` interface now contains a ``formatted`` attribute.
- ``SENTRY_MANAGED_USER_FIELDS`` now defaults to an empty list.
- Issues now render based on the type of data present, which are represented by
the type and metadata attributes in API responses.
- Stacktrace rendering has been greatly simplified and unified across languages.
- Client's may now pass the 'contexts' attribute, which will eventually supercede 'extra'.
- Various named contexts are now automatically generated and summarized for Cocoa and JavaScript
issues.
- Added JSON formatting for logs with ``system.logging-format``.
- Added a ``loglevel`` command line flag to most commands.
- Added two factor authentication support.
- Added support for setting IP address of an event automatically on event submission for all platforms.
- Added unsubscribe links to mails.
- Added email verification.
- Added ability to link/unlink Issues, support is dependent on plugins.
- Can now toggle between minified/original code in stacktraces where sourcemaps were applied.
- Can now upload release artifacts with tilde prefix (~) to omit protocol + host in URL lookups.

Schema Changes
~~~~~~~~~~~~~~

- Added ``User.is_password_expired`` column.
- Added ``User.last_password_change`` column.
- Added ``UserEmail`` model.
- Added unique index on ``GroupTagValue(group_id, key, value)``
- Remove unique index on ``GroupTagValue(project_id, group_id, key, value)``
- Added index on ``GroupTagValue(project_id, key, value)``
- Added ``GroupSubscription`` model.

Features

- Send trace origin (2957)

[Trace origin](https://develop.sentry.dev/sdk/performance/trace-origin/) indicates what created a trace or a span. Not all transactions and spans contain enough information to tell whether the user or what precisely in the SDK created it. Origin solves this problem. The SDK now sends origin for transactions and spans.

- Create User and Breadcrumb from map (2820)

Fixes

- Improved performance serializing profiling data (2863)
- Possible crash in Core Data tracking (2865)
- Ensure the current GPU frame rate is always reported for concurrent transaction profiling metrics (2929)
- Move profiler metric collection to a background queue (2956)

Removed

- Remove experimental `stitchAsyncCode` from SentryOptions (2973)

The `stitchAsyncCode` experimental option has been removed from `SentryOptions` as its behavior was unpredictable and sometimes resulted in unexpected errors. We plan to add it back once we fix it, but we don't have an ETA for it.

------

- Fixed issue with new Unsubscribe links in emails not working.
- Fixed bug with raven-js compatibility with IE8.
- Fixed bug handling IPv6 addresses.

----

- Added option to upload a profile image as an alternative to Gravatar.
- Deprecated ``sentry celery`` subcommand in favor of ``sentry run {worker|cron}``.
- Breadcrumb interface now rendered in event UI.
- Project notification settings page now indicates if current user is subscribed to active project.
- User is now automatically redirected to login page if their session expires inside React client application.
- Added new auth tokens to deprecate the usage of the older API keys.

Schema Changes
~~~~~~~~~~~~~~

- Added ``ProjectPlatform`` model.
- Added index on``EventTag`` index.
- Added unique index on ``UserReport`` model.
- Added ``UserAvatar`` model.
- Added ``EventTag.group_id`` column.
- Added ``ApiToken`` model.
- Added ``Authenticator`` model.

Features

- feat: Core data operation in the main thread (2879)

Fixes

- Crash when serializing invalid objects (2858)
- Don't send screenshots with either width or height of 0 (2876)
- GPU frame alignment with stack traces in profiles (2856)

------

- Fixed issue in running 8.4 migrations on MySQL only.
- Fixed issue that caused an infinite loop in ``patch_context.py`` under a race condition.
- Silently ignore breadcrumb data coming from clients instead of showing an error in the UI.