Current read
The first API pivot week produced new search impressions faster than the fading WooCommerce test. The strongest early signal was the Stripe API versioning page, so the page was broadened from one exact version into a safer versioning and upgrade checklist.
Use this when: an app, integration, API request, webhook, authentication flow, SDK, or dashboard automation depends on a versioned developer platform.
API change records
| Change | Who is affected | First action |
|---|---|---|
| Stripe API versioning: what changes, what breaks, and how to upgrade safely | Teams upgrading Stripe account defaults, SDKs, per-request versions, or webhook endpoints | Inventory every Stripe version boundary before changing production |
| Shopify offline access token expires: public app migration by 2027 | Public apps still using non-expiring offline Admin API tokens | Migrate token exchange, refresh handling, and storage before January 1, 2027 |
| Shopify returnProcess replaces legacy return refund APIs | Apps creating returns, approving return requests, or handling refunds/exchanges | Move return/refund flows to returnProcess and suggestedFinancialOutcome |
| Shopify 2026-10 invalid metafield filters return errors | Apps filtering products, orders, or customers by metafields in GraphQL Admin API 2026-10+ | Audit filters and confirm metafield definitions allow filtering before upgrading |
| GitHub REST API versioning and support window | Integrations specifying or relying on GitHub REST API versions | Send X-GitHub-Api-Version explicitly and check breaking changes before upgrading |
Page format
- What changed. The official change in one sentence.
- Who is affected. Exact apps, requests, APIs, versions, or flows.
- What breaks. The failure mode to look for.
- Smallest safe action. The first migration or audit step.
- Official sources. Direct links to the platform source.