API CHANGE TRACKER / DigitalOcean

DigitalOcean breaking change: PATCH /v2/action-gateway/connections/{id}

api removed without deprecation

Specification capture: . Published evidence last updated . 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
operation.endpoint_removed
Classifier version
2026-10-15.2
Direction
operation
Finding ID
chg_e492941ebfccf489dbe0fac65e1a2145816ec440e3201ccb71abe9ba421b8dd4

What is the recorded before and after evidence?

Previous specification SHA-256: 90c27c47e4777578fab0e8fe95c5f5557a08a4c02b2ba2396967001c5df3695a

Revised specification SHA-256: 0d7ebc52b50bc0a7ee221c1d8ee99013f77b2391d68761fc762f9b7dc0d0e2de

Publisher version: 2.0 to 2.0.

  ...
  get:
    $ref: resources/action_gateway/connections_get.yml
- patch:
-   $ref: resources/action_gateway/connections_update.yml

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