3 API changes to audit before your next deploy: Supabase, HubSpot, and Shopify

Release notes are easy to bookmark and easy to forget. These three changes have
clear version or removal dates, concrete failure modes, and work you can test
before they reach production.

This is not a general product-news roundup. It is a short audit list for teams
that own integrations with Supabase, HubSpot, or Shopify.

1. Supabase is replacing the Management API logs.all endpoint

Supabase will remove analytics/endpoints/logs.all on September 23, 2026.
The replacement is the ClickHouse-backed analytics/endpoints/logs endpoint.

You are affected only if a script, integration, or internal tool calls the
Management API endpoint directly. The dashboard Logs Explorer is not affected.

The migration has three important parts:

1. Change the endpoint path from logs.all to logs.
2. Convert the query to ClickHouse SQL.
3. Query the unified logs table and filter the source with source_name.

Nested log fields also move to a flatter log_attributes map, so queries that
currently unnest metadata may need more than a path replacement.

Test before shipping: run the old and new queries against the same bounded
time window. Compare row counts, source distribution, timestamps, and the
fields your alerting or export logic consumes. Add a contract test that fails
if the old endpoint returns a removal response or if the new result loses the
required source filter.

Official source: Supabase developer changelog

2. HubSpot pipeline deletes will validate references in API version 2026-09

HubSpot's 2026-09 Pipelines API version goes live on September 8, 2026.
After an integration moves to that version, deleting a pipeline or stage that
is still referenced will be blocked by default and may return HTTP 400.

Earlier API versions keep their existing behavior. The risk appears when your
integration upgrades to 2026-09 or later, not merely when the calendar reaches
September.

Audit now: find every code path that deletes a pipeline or stage. Decide
whether a referenced resource should be treated as a user-correctable conflict
or whether your workflow truly depends on the documented opt-out behavior.
Prefer removing references and retrying deliberately over making destructive
deletes automatic.

Test before shipping: seed a pipeline with an in-use stage, attempt the
delete against the target API version, and assert that the integration surfaces
the validation error without retrying indefinitely. Keep the earlier version
pinned until the new behavior and recovery path pass in staging.

Official source: HubSpot developer changelog

3. Shopify removes Customer.lastIncompleteCheckout in version 2026-10

Shopify's Customer Account API version 2026-10 removes the deprecated
Customer.lastIncompleteCheckout field and the Checkout type subtree that was
reachable through it. The field had already returned null, but its schema
removal means queries that still select it can fail validation after the version
upgrade.

There is no direct replacement field in the Customer Account API.

• For an active storefront cart or checkout, move to Storefront API cart flows.
• For completed purchase history, use Customer.orders.

Test before shipping: search stored GraphQL documents, generated types,
fragments, persisted queries, fixtures, and mocks for
lastIncompleteCheckout. Run schema validation against 2026-10, then test the
replacement flow at the boundary where your application actually needs cart or
order state.

Official source: Shopify developer changelog

A reusable migration checklist

For each upstream change:

1. Name the owning integration and team.
2. Record the vendor version or removal date.
3. Pin the current version while the migration is incomplete.
4. Add a failing contract test before changing production code.
5. Test the vendor's failure response, not only the happy path.
6. Define rollback and reconciliation steps before upgrading.

The useful unit is not "we read the changelog." It is "we know which call we
own, when it changes, and which test proves the migration is safe."

I maintain Breakwater,
a local Chrome workspace that watches official developer changelogs and keeps
migration deadlines beside the APIs your stack uses. The linked brief includes
the same three official sources and a compact review path.