Data and Schema Compatibility
Detects removed serialization attributes and enum member removals that may break wire formats or persisted data.
Why this rule exists
Removing an enum value or [JsonPropertyName] attribute breaks every consumer that has that value persisted in a database, on a queue, or in a snapshot. The deploy succeeds; the next read fails.
Code example
public enum OrderStatus
{
Pending,
- Processing,
Shipped
} public enum OrderStatus
{
Pending,
[Obsolete("Use Fulfilled")] Processing,
Shipped,
+ Fulfilled,
}Configuration
Disable or adjust the severity of this rule in .gauntletci.json:
{
"rules": {
"GCI0021": { "enabled": true, "severity": "Block" }
}
}See Configuration for the full schema.
Related rules
Breaking Change Risk
Detects removed public APIs and changed public method signatures that may break callers.
Data Integrity Risk
Detects unchecked casts, mass assignment without validation, and SQL ON CONFLICT IGNORE patterns that silently discard errors.
SQL Column Truncation Risk
Detects short nvarchar(N) or varchar(N) column definitions that may silently truncate data when real-world values exceed the column width.
Discussed in
Implemented in src/GauntletCI.Core/Rules/Implementations/GCI0021_*.cs.
Eric Cogen -- Founder, GauntletCI
Twenty years in .NET production. Most of those years, the bugs that hurt me were not the ones tests caught. They were the assumptions I did not know I was making: a removed guard clause, a renamed method that still did the old thing, a catch {} that turned a page into a silent dashboard lie. GauntletCI is the checklist I wish I had run before every commit. It runs the rules I learned the hard way, so you do not have to.