Driftwatch

GitHub / GitHub REST API /

Breakingdirection flip: their tools call this safe

write_scope is no longer accepted

What changed

Usually ignored rather than rejected, so the call succeeds and does something subtly different.

Affects write_scope on POST /agents/repos/{owner}/{repo}/automations. Grep for it: nothing else will tell you.

Who is affected

Code that sends POST /agents/repos/{owner}/{repo}/automations (write_scope).

Before and after

WhereBeforeAfter
POST /agents/repos/{owner}/{repo}/automations · write_scopepresentabsent
PATCH /agents/repos/{owner}/{repo}/automations/{automation_id} · write_scopepresentabsent

Code that breaks

await client.post("/agents/repos/{owner}/{repo}/automations", {
  // write_scope is now ignored, not rejected
  write_scope: value,
});

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