API CHANGE TRACKER / PagerDuty

PagerDuty breaking change: PUT /event_orchestrations/services/{service_id}

removed `#/components/schemas/ParityDiffShared_1c2ca86a40f1053cf61d3a9950b72070fe4f0925cf8979ba6867b62cecf01744` from the request body `allOf` list

Specification capture: 2026-09-24 UTC. Published evidence last updated 2026-11-03 UTC. This is captured contract evidence, not an observed outage or a result from scanning your code.

Which field and classification rule changed?

Changed field

Operation-level change

Rule ID

request.content_removed

Classifier version

2026-10-15.2

Direction

request

Finding ID

chg_e134d7b3153003920ee7512060a3c6f3bb3da49db191cba27e2acb85feb28f79

What is the recorded before and after evidence?

Previous specification SHA-256: 0fa556204094437af83b04bddceebf2e469b8672dc675ea0d1c2dbfc0cf5822f

Revised specification SHA-256: 6c19f1f4b622e7d098e0a5a5f5ce04afdc0a21a5b9c1cb7b1649a594e88f2345

Publisher version: 2.0.0 to 2.0.0.

No before/after schema excerpt is available in this bounded snapshot. Use the source revisions and public finding to inspect the contract; no replacement behavior is inferred here.

Inspect the complete release · Public source findings · Publisher specification source

How do I check whether this affects my code?

Confirm the affected operation and field in the repository commit you authorize. Inspect supported SDK and HTTP call-site matches, review dynamic or unmatched patterns, and choose the intended application behavior before approving a proposal. Schema validation, type checks, configured runtime checks, and your CI provide different evidence.

Check an authorized repository · Review coverage · Inspect classification rules