Metric 0.1.10

Issue grouping

• Grouping revision 2 gives exceptions without application frames a more specific
  Issue. When the event has no usable stack or message for the existing strategies,
  Metric uses the exception type and library frames when available, then falls back
  to the exception type and normalized value. URLs in that value are normalized so
  changes to a host or build-specific asset URL can still group into the same Issue.
• Messages without exceptions or an event-level stack can group by application
  frames from a thread stack. This lets messages from the same stack group together
  even when their text includes a different pod name. Distinct messages with the
  same grouping frames can share an Issue. Messages with native thread stacks
  continue to group by text.
• When the exception and event stacks have no frames, event details use the
  crashed thread, the current thread if there is no crashed thread, or the only
  thread in the event. If the selected thread has no frames, the stack view shows
  no frames.

Upgrades and downgrades

New projects use grouping revision 2. Existing projects keep their pinned revision
when Metric is upgraded. An explicit revision change affects events processed
afterward. Previously stored events and Issues keep their original grouping.

Before downgrading to 0.1.9, move any projects pinned to revision 2 back to revision

1. The 0.1.9 server cannot group their incoming events while they are pinned to
   revision 2. See ADR-0053
   for the project setting in MongoDB and PostgreSQL.

Both storage backends continue to use schema generation 22. See
Update Metric for the upgrade procedure.