Driftwatch

PagerDuty / PagerDuty REST API /

Breakingdirection flip: their tools call this safe

status can now return "in_review"

What changed

Producer-side tools call this additive. It breaks exhaustive switches, strict parsers and generated client enums.

Affects status on IncidentReview reachable from 3 operations.

New value: in_review.

can now return "in_review"

Who is affected

Code that reads PagerDuty's IncidentReview objects, used by 3 PagerDuty operations.

Before and after

WhereBeforeAfter
IncidentReview.status"completed", "started""completed", "in_review", "started"

Code that breaks

switch (response.status) {
  // existing branches …
  // no branch for "in_review"
  default:
    throw new Error("unexpected status");
}

Based on PagerDuty’s published API specification. How severity is decided.