Enum values changed in PATCH /repos/{owner}/{repo}/code-scanning/alerts/{alert_number} (code-scanning-alert-dismissed-reason)

What changed

Enum values changed in PATCH /repos/{owner}/{repo}/code-scanning/alerts/{alert_number} (code-scanning-alert-dismissed-reason) Affected surface: PATCH /repos/{owner}/{repo}/code-scanning/alerts/{alert_number}. Root cause: schema `code-scanning-alert-dismissed-reason`. Detected at Fri, 14 Aug 2026 14:43:23 UTC UTC.

Diff

{
  "added_enums": [
    "mitigated"
  ],
  "path": "PATCH /repos/{owner}/{repo}/code-scanning/alerts/{alert_number}",
  "schema_path": "schema code-scanning-alert-dismissed-reason"
}

Likely impact

This is an additive change. Existing integrations are unaffected; this is mostly useful if you want to take advantage of the new surface.

Recommended action

Audit any switch/match statements over this enum. Removed values become unhandled paths.