Does Qodana safely ignore stale baseline entries after a schema change?
26K reputation · 16 Nov 2021, 03:36 UTC
Goal: Determine whether Qodana can continue to produce reliable analysis results after an inspection schema change without requiring manual baseline regeneration.
Qodana stores a baseline file that records existing issues; when the underlying inspection schema changes (e.g., upgrading Qodana or modifying profiles), the baseline may become outdated. The tool does not automatically invalidate or migrate baseline entries, leaving it unclear whether stale entries are safely ignored or treated as errors. This undocumented behavior creates uncertainty about rollback safety after schema updates.
Does Qodana automatically discard or ignore baseline entries that reference inspections no longer present after a schema upgrade? If not, what risks arise from retaining stale baseline entries, and is manual regeneration the only safe approach?