What shipped in Sentry
1 release, newest first.
Clearer fingerprint rule editing
On November 12, 2026, Sentry made fingerprint rules easier to write and debug, including when Seer Agent writes them. The fingerprint rules field in Project Settings > Issue Grouping has syntax highlighting and inline feedback. Errors, shown in red, mark lines Sentry can't parse and which won't save. Warnings, shown in yellow, mark lines that will save but probably won't do what you meant, such as an unquoted title= value or a trailing # comment that ends up in the fingerprint. Expand the summary under the field to see each problem, and click to jump to that line. Syntax errors in a rule's matchers or arrow point to the exact spot and suggest a fix for a lookalike arrow (→ instead of ->), a missing ->, or a missing space before ->. The API returns the same errors, so scripts and AI agents that update rules get the same help. Seer Agent previously wrote → instead of -> and the save failed. Seer now knows the fingerprint rule syntax, including which matchers and variables exist, and asking it to set up custom grouping returns valid rules. When a rule assigns more than one fingerprint value, the issue's grouping info shows the values quoted and separated by commas. Only the display changed. Existing issues group exactly as they did before. Fingerprint rules only apply to new events.
Source for Clearer fingerprint rule editing (opens in a new tab)
Updated