Driftwatch

GitHub / GitHub REST API /

Breaking

Response field write_scope removed

What changed

Reads of this field return undefined, and the failure surfaces wherever that value is used rather than at the call.

Affects PATCH /agents/repos/{owner}/{repo}/automations/{automation_id}.

Who is affected

Code that reads PATCH /agents/repos/{owner}/{repo}/automations/{automation_id} (write_scope).

Before and after

WhereBeforeAfter
PATCH /agents/repos/{owner}/{repo}/automations/{automation_id} · write_scopepresentabsent
GET /agents/automations · write_scopepresentabsent
GET /agents/repos/{owner}/{repo}/automations · automations[].write_scopepresentabsent
POST /agents/repos/{owner}/{repo}/automations · write_scopepresentabsent
GET /agents/repos/{owner}/{repo}/automations/{automation_id} · write_scopepresentabsent

Code that breaks

// response.write_scope is now undefined
const write_scope = response.write_scope;

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