Three API changes to audit before your next deploy.
Supabase is replacing a log-query endpoint, HubSpot is changing delete validation, and Shopify is removing a checkout schema. Here are the exact surfaces, dates, and next checks from each official announcement.
Source first. Impact second. Deadline third.
Each item passed Breakwater's high-signal filter, came from a distinct official source, and was read manually before inclusion. The vendor page remains authoritative; this brief turns its announcement into an audit queue.
- Source type
- Official
- Lookback
- 31 days
- Signals required
- Exactly 3
- Autopost
- None
Check these contracts before upgrading.
Start with the code paths that touch these exact endpoints, API versions, or fields. If you do not use the affected surface, no action is required.
logs.all moves to logs
The Management API endpoint is removed on September 23, 2026. The replacement accepts ClickHouse SQL and exposes sources through one unified logs table.
- Deadline
- September 23, 2026
- Failure risk
- Calls to
analytics/endpoints/logs.allstop working. - Audit
- Change the path, convert SQL, and filter by
source_name.
Pipeline deletes validate references
In API version 2026-09, pipeline and stage deletes check references by default. In-use resources can return an HTTP 400 validation error.
- Live
- September 8, 2026
- Failure risk
- Existing delete flows may no longer succeed after an API-version upgrade.
- Audit
- Handle validation errors or explicitly set the documented opt-out parameter.
Customer checkout schema is removed
Customer Account API version 2026-10 removes Customer.lastIncompleteCheckout and the now-unreachable Checkout subtree.
- Effective
- API version 2026-10
- Failure risk
- Queries selecting the removed field or nested Checkout types will fail validation.
- Audit
- Use Storefront API cart flows for active state or
Customer.ordersfor purchase history.
Turn reading into a release decision.
1. Search
Search code, workflows, and saved queries for the exact endpoint, version, field, and type names above.
2. Reproduce
Add a contract test that shows today's behavior and the vendor's documented replacement behavior.
3. Assign
Give each affected integration an owner, migration date, and rollback condition.
4. Verify
Read the linked official page again immediately before rollout in case the vendor updated its guidance.
Keep the next API surprise out of production.
Install Breakwater, choose the platforms in your Stack, and turn official changelog signals into an owned migration queue.