API Breaking Changes and Deprecations — July 2026

The Magento extension update for Adobe Commerce removes backend rendering management. Customers using server-side rendering must now install the Algolia Adapter module to maintain this functionality, which is a breaking change.

The Magento extension update removes backend rendering management. Customers using server-side rendering must now install the Algolia Adapter module to maintain this functionality, which is a breaking change.

The Magento extension update for Adobe Commerce removes backend rendering management. Customers using server-side rendering must now install the Algolia Adapter module to maintain this functionality, which is a breaking change.

The Magento extension update removes backend rendering management. Customers using server-side rendering must now install the Algolia Adapter module to maintain this functionality, which is a breaking change.

The Magento extension update for Adobe Commerce removes backend rendering management. Customers using server-side rendering must now install the Algolia Adapter module to maintain this functionality, which is a breaking change.

The Adobe Commerce extension update removes backend rendering management. Customers using server-side rendering must now install the Algolia Adapter module to maintain this functionality, which is a breaking change.

The Magento extension update for Adobe Commerce removes backend rendering management. Customers using server-side rendering must now install the Algolia Adapter module to maintain this functionality, which is a breaking change.

The Adobe Commerce (Magento) extension update removes backend rendering management. Customers using server-side rendering must now install the new Algolia Adapter module to maintain this functionality, which is a breaking change.

The Adobe Commerce (Magento) extension update removes backend rendering management. Customers using server-side rendering must install the new Algolia Adapter module to maintain this functionality, which is a breaking change.

The Adobe Commerce (Magento) extension update removes backend rendering management. Customers using server-side rendering must install the new Algolia Adapter module to maintain this functionality, which is a breaking change.

The Adobe Commerce (Magento) extension update removes backend rendering management. Customers using server-side rendering must install the new Algolia Adapter module to maintain this functionality, which is a breaking change.

The Magento extension update for Adobe Commerce removes backend rendering management. Customers using server-side rendering must now install the new Algolia Adapter module to maintain this functionality, which is a breaking change.

The Adobe Commerce (Magento) extension update removes backend rendering management. Customers using server-side rendering must now install the Algolia Adapter module to maintain this functionality, which is a breaking change.

The Adobe Commerce (Magento) extension update removes backend rendering management. Customers using server-side rendering must install the new Algolia Adapter module to maintain this functionality, which is a breaking change.

The Adobe Commerce (Magento) extension update removes backend rendering management. Customers using server-side rendering must now install the Algolia Adapter module to maintain this functionality, which is a breaking change.

The Magento extension update removes backend rendering management. Customers using server-side rendering must now install the Algolia Adapter module to maintain this functionality, which is a breaking change.

The Adobe Commerce (Magento) extension update removes backend rendering management. Customers using server-side rendering must install the new Algolia Adapter module to maintain this functionality, which is a breaking change.

The Account Role API has been deprecated. Users should review their integrations to understand the impact and plan for migration.

The Account Role API and legacy Workers KV namespace API routes have been deprecated. Users should migrate away from these APIs to avoid future disruptions.

This release deprecates the Account Role API and legacy Workers KV namespace API routes. It also introduces new features like MCP Specification 2026-07-28 support in Agents SDK and the ability to run integration tests against Worker's production builds.

The Account Role API and legacy Workers KV namespace API routes have been deprecated. Users should migrate to newer alternatives to avoid future disruptions.

The legacy Workers KV namespace API routes have been deprecated. Users should migrate to the newer API routes to avoid future issues.

The Account Role API and legacy Workers KV namespace API routes have been deprecated. Users should migrate away from these APIs to avoid future disruptions.

The Account Role API has been deprecated. Additionally, the Zero Trust Networks route endpoints and Cloudflare Tunnel connections field will be retired on October 5, 2026, requiring users to update their configurations.

The 'Zero Trust Networks route endpoints and Cloudflare Tunnel connections' field is retiring on October 5, 2026. Users relying on this field will need to update their configurations before the sunset date to avoid service disruption.

The 'Zero Trust Networks route endpoints and Cloudflare Tunnel connections' field is retiring on October 5, 2026. Users should plan to migrate away from using this field before the sunset date to avoid service disruption.

Cloudflare is deprecating legacy Workers KV namespace API routes. Users should migrate to newer API routes to avoid future issues.

The 'Zero Trust Networks route endpoints and Cloudflare Tunnel connections' field is retiring on October 5, 2026. Additionally, Workflows pricing will add per-step billing, with step and storage billing starting no earlier than August 10, 2026.

The 'Zero Trust Networks route endpoints and Cloudflare Tunnel connections' field is retiring on October 5, 2026. Additionally, Workflows pricing will add per-step billing, with step and storage billing starting no earlier than August 10, 2026.

The 'Zero Trust Networks route endpoints and Cloudflare Tunnel connections' field is retiring on October 5, 2026. Additionally, new Durable Object namespaces must now use the SQLite storage backend, which could be a breaking change for new deployments.

A field related to Zero Trust Networks route endpoints and Cloudflare Tunnel connections is being retired on October 5, 2026. Users should review their configurations to avoid potential disruptions.

The ability to test Durable Object eviction with `cloudflare:test` helpers and track memory usage for Workers and Durable Objects in the dashboard has been removed. This could impact developers relying on these features for testing and monitoring.

Cloudflare AMP/SXG has reached its end of life. Users should be aware that this feature is no longer supported.

The Datadog Agent now defaults to forwarding metrics to the v3 API, which is a breaking change for users forwarding to non-Datadog endpoints. Additionally, the `agent status py` subcommand has been removed, and Linux systemd unit names for the process manager have changed, requiring updates to custom automation.

Several Gemini API models (gemini-2.5-pro, gemini-2.5-flash, gemini-2.5-flash-lite, gemini-2.5-flash-image) are being shut down in October 2026. Users of these models, especially with Firebase AI Logic, must migrate to newer models like gemini-3.6-flash or gemini-3.1-flash-image to prevent service disruption and 404 errors.

Firebase AI Logic now supports new Gemini models (gemini-3.6-flash, gemini-3.5-flash-lite, gemini-3.1-flash-lite-image). However, these new models deprecate sampling parameters (temperature, topP, topK) and no longer support prefilling model turns, which will cause a 400 error if attempted. Additionally, App Check is now automatically enforced for AI Logic, requiring configuration for local development.

Firebase Extensions is deprecated and will be sunset on March 31, 2027. After this date, users will lose the ability to update, reconfigure, or uninstall extensions via the Firebase console or CLI, though deployed extensions will continue to execute. Publishers are advised to migrate to Cloud Functions for Firebase.

The shutdown date for the Gemini Developer API (Google AI) has been extended from June 24, 2026, to as early as June 30, 2026. Users should note this slight change in the timeline for the API's deprecation.

GitHub Models has been retired. Users should be aware that this feature is no longer available.

The Copilot Billing Preview app will be retired on August 3. Users should transition off this preview app.

GitHub Copilot is announcing the upcoming deprecation of Gemini 2.5 Pro and Gemini 3 Flash models. Users relying on these specific models for Copilot functionality should prepare for their removal.

GitHub Models is being fully retired on July 30, 2026. Additionally, there are upcoming access restrictions to public API endpoints and UI views, which may impact integrations.

Support for Model Context Protocol (MCP) servers and tools in Cloud API Registry will be shut down on July 30, 2026. This means you will no longer be able to retrieve, list, enable, or disable MCP servers and tools using the Cloud API Registry API.

The preview models `gemini-3.1-flash-image-preview` and `gemini-3-pro-image-preview` have been retired and are no longer accessible. Users must update their code to use `gemini-3.1-flash-image` or `gemini-3-flash-image` instead to avoid service disruption.

Batch jobs can no longer locate Compute Engine resources outside the job's location, with enforcement starting July 31, 2026, or June 30, 2027, depending on project history. Additionally, customer-supplied encryption keys (CSEKs) for Compute Engine disks, snapshots, images, and machine images are deprecated and will be disabled on July 20, 2027.

The `gcloud storage rsync` command now defaults to decompressing downloaded gzip files, matching `gcloud storage cp`. This is a breaking change as it alters previous behavior, requiring users to use the new `--do-not-decompress` flag to retain the old behavior.

The standalone GenAI Incident Summary feature in Apigee Advanced API Security Abuse Detection, currently in Preview, is deprecated and will be shut down on July 9, 2026. Users should be aware that this feature will no longer be available.

The Grok 4.1 model family on the Gemini Enterprise Agent Platform is deprecated and will be shut down on August 20, 2026. API requests to these models will fail after this date, requiring migration to newer xAI models or alternatives.

The OpenAI Python SDK now requires Python 3.10 or higher. Users on older Python versions will need to upgrade their environment to continue using the latest SDK version.

This changelog indicates several deprecations, including the useBuyerJourneyIntercept API, cumulative marketing engagements, and merchant-owned delivery profile APIs. It also notes the removal of Customer.lastIncompleteCheckout and Checkout types in the Customer Account API by 2026-10, and the deprecation of discountedUnitPrice on DraftOrderLineItem.

This diff indicates several breaking changes, including invalid metafield queries returning errors, removal of Customer.lastIncompleteCheckout and Checkout types in the Customer Account API by 2026-10, and changes to POS UI extensions. It also notes deprecations such as useBuyerJourneyIntercept API and cumulative marketing engagements.

The GraphQL Admin API now returns errors for invalid metafield queries, which was previously not the case. This is a breaking change that may require updates to existing queries.

This diff indicates several breaking changes, including invalid metafield queries returning errors, POS UI extensions changing discount calculations, and the removal of Customer.lastIncompleteCheckout and Checkout types in the Customer Account API by 2026-10. Additionally, the useBuyerJourneyIntercept API and cumulative marketing engagements are being deprecated.

The GraphQL Admin API now returns errors for invalid metafield queries, which is a breaking change. Previously, these queries might have silently failed or returned unexpected results.

This changelog indicates several breaking changes, including the removal of `Customer.lastIncompleteCheckout` and `Checkout` types in the Customer Account API by 2026-10, and changes to POS UI extensions. It also notes deprecations such as `useBuyerJourneyIntercept` and `cumulative marketing engagements`, requiring developers to update their applications to avoid failures.

This diff indicates several breaking changes, including the removal of Customer.lastIncompleteCheckout and Checkout types in the Customer Account API by 2026-10, and changes to POS UI extensions. It also highlights deprecations such as the useBuyerJourneyIntercept API and cumulative marketing engagements.

This changelog indicates several upcoming deprecations and breaking changes across various Shopify APIs, including the removal of Customer.lastIncompleteCheckout and Checkout types, deprecation of useBuyerJourneyIntercept API, cumulative marketing engagements, and merchant-owned delivery profile APIs, as well as the removal of discountedUnitPrice on DraftOrderLineItem.

This changelog indicates several upcoming deprecations and breaking changes across various Shopify APIs, including the removal of Customer.lastIncompleteCheckout and Checkout types, deprecation of useBuyerJourneyIntercept API, cumulative marketing engagements, and merchant-owned delivery profile APIs. Developers should review these changes to prepare for migrations and prevent service disruptions.

This changelog indicates several breaking changes, including the removal of Customer.lastIncompleteCheckout and Checkout types in the Customer Account API (2026-10), and the deprecation of useBuyerJourneyIntercept API on checkout UI extensions. Additionally, POS UI extensions 2026-07 now require per-unit fixed-amount line item discounts, removing auto-conversion.

From POS UI extensions 2026-07, FixedAmount line item discounts must be computed per-unit by apps, as the total-to-unit auto-conversion functionality has been removed. This is a breaking change requiring apps to update their discount calculation logic.

From POS UI extensions 2026-07, FixedAmount line item discounts must be computed per-unit by apps, as the total-to-unit auto-conversion has been removed. This is a breaking change requiring apps to update their discount calculation logic.

The useBuyerJourneyIntercept and block_progress APIs are deprecated for checkout UI extensions. Developers must migrate to Shopify Functions for cart and checkout validation or discount code rejection to avoid future issues.

The Customer Account API will remove the deprecated Customer.lastIncompleteCheckout field and the unreachable Checkout type subtree in version 2026-10. This is a breaking change that will require updates to applications using these fields.

This update includes several deprecations, such as `usePopularProducts` in Shop Minis, `isCumulative` in `marketingEngagementCreate`, `discountedUnitPrice` on `DraftOrderLineItem`, and merchant-owned delivery profile APIs. Developers should review these changes and migrate their integrations to the recommended alternatives to avoid future issues.

The `conference_participant` field has been removed from the Voice Insights Call Summary. This is a breaking change that may affect applications relying on this field.

The RCS error code for unconfirmed delivery is changing from 30036 to 30046, which may require updates to error handling logic. Additionally, the `conference_participant` field has been removed from Voice Insights Call Summary, impacting any integrations relying on this data.

The `conference_participant` field has been removed from the Voice Insights Call Summary. This is a breaking change that may affect applications relying on this field.

The conference list endpoint will change its default behavior to only show in-progress conferences starting July 13, 2026. This is a breaking change for users who rely on the current default behavior to retrieve all conferences.

The `conference_participant` field has been removed from the Voice Insights Call Summary. This is a breaking change that may affect applications relying on this field.

Vercel has announced the deprecation of Node.js 20, with its removal scheduled for October 1, 2026. Users should plan to migrate to a newer Node.js version before this date.

Node.js 20 is being deprecated, with the removal scheduled for October 1, 2026. Users should plan to migrate to a newer Node.js version before this date to avoid service interruptions.

Vercel is deprecating Node.js 20, with removal scheduled for October 1, 2026. Users should plan to migrate to a newer Node.js version before this date to avoid service interruptions.