Deprecations, shutdowns and breaking changes from the vendors developers depend on, reviewed by the StackClock team. Check which ones affect your stack or follow the RSS feed.
ShopifycriticalBreaking change Takes effect 1 Dec 2026 · published 20 Nov 2026
Starting December 1, 2026 for public apps, and January 1, 2027 for custom apps, the abandoned checkout recovery URL requires approval for all four protected customer fields (name, email, phone, and address) on all supported Admin API versions and unstable . If your app reads AbandonedCheckout.abandonedCheckoutUrl or abandoned_checkout_url but doesn't need it, stop using the field. If your app needs it, request access before your date. This is a breaking change made for security reasons.
Which apps and when
| App | Date | How to get access |
|
Takes effect 31 Oct 2027 · published 20 Nov 2026
Twilio Notify’s end-of-life date has moved from January 31, 2027 to October 31, 2027.
After October 31, 2027, requests to the Notify API will stop working, and push notifications and SMS sent through Notify won’t reach your users.
For customers using SMS, we recommend moving to the Bulk Messaging API .
For push notifications, the replacement is the new Push Notifications API, now in private beta, and customers can request access to the Push Notifications API .
Need a hand?
These resources have more information:
How to transition off Notify
Push Notifications API Private Beta Access
Learn more
Nov 18, 2026
GA
Elastic SIP trunking
Takes effect 16 Nov 2026 · published 17 Nov 2026
As of today, November 16, 2026, we have deprecated the following models across most GitHub Copilot experiences (including Copilot Chat, inline edits, ask and agent modes, and code completions). Note that Claude Opus 4.8 is still available to individual GitHub Copilot subscribers on annual plans.
These deprecations were announced on October 15, 2026 .
Model
Deprecation date
Suggested alternative
Claude Opus 4.8
2026-11-16
Claude Opus 5.5
Claude Opus 5
2026-11-16
Claude Opus 5.5
GPT-5.6 Terra
2026-11-16
GPT-6.1 Sol or GPT-6 Luna
Claude Opus 5 has been removed from the model picker but remains available for runtime refusal fallback through existing authorized access. Existing enterprise model policies continue to apply.
Please update your workflows and integrations to use supported models. Under default model enablement, the suggested alternatives are automatically enabled for Copilot Enterprise and Copilot Business customers unless an administrator has turned off the global defaul
Takes effect 15 Jan 2027 · published 16 Nov 2026
Storefront MCP search_shop_policies_and_faqs is deprecated. Migrate to UCP MCP's ask_business tool by January 15, 2027.
What's changing
The search_shop_policies_and_faqs tool on the Storefront MCP server ( https://{shop}.myshopify.com/api/mcp ) is deprecated in favor of the UCP Ask MCP tool.
UCP MCP implements the UCP ask capability ( dev.ucp.common.ask ) and exposes the following tool at the https://{shop-domain}/api/ucp/mcp endpoint:
ask_business : Answer a buyer's question about the store's policies and services, using the store's knowledge base and policies.
The deprecated tool will be maintained until January 15, 2027, but all documentation will refer to Ask MCP.
What you should do
If you're building with search_shop_policies_and_faqs :
Migrate calls to ask_business , and update endpoints to use https://{shop-domain}/api/ucp/mcp .
Include a meta object carrying ucp-agent.profile in every request. Your agent profile must declare dev.ucp.common.ask .
Send the question in a
ShopifyhighBreaking change No date announced · published 16 Nov 2026
As of Storefront API version 2027-01 , the metafields field on the Market object matches each requested key in any case, as Market.metafield already does. This is a breaking change for apps and custom storefronts that request a market metafield key in a different case from the stored key, or that read a key that the buyer's markets store that differ by letter case. If your app does either, review its Market.metafields queries before you move it to 2027-01 .
What changed
In version 2027-01 , Market.metafields returns a metafield when the requested key matches the stored key in any case. In earlier versions, Market.metafields returns a metafield only when the requested key and the stored key have the same case.
For example, a market stores a metafield with the namespace custom and the key colour :
In version 2026-10 and earlier, the entry for { namespace: "custom", key: "Colour" } is null .
In version 2027-01 , the entry returns the stored metafield.
Who's affected
The change appl
Takes effect 14 Dec 2026 · published 14 Nov 2026
We will deprecate the following models across all GitHub Copilot experiences (including Copilot Chat, inline edits, ask and agent modes, and code completions) on December 14, 2026:
Model
Deprecation date
Suggested alternative
Claude Fable 5
2026-12-14
Claude Fable 5.2
Claude Haiku 4.5*
2026-12-14
Claude Haiku 5.5
Gemini 3.8 Flash
2026-12-14
Gemini 4 Hydrogen
Gemini 4 Argon
2026-12-14
Gemini 4 Carbon
Grok 4.6
2026-12-14
Grok 4.7
Kimi K3
2026-12-14
To be announced
*Claude Haiku 4.5 will remain available to individual GitHub Copilot subscribers on annual plans. The deprecation of Claude Haiku 4.5 does not apply to these customers.
Please update your workflows and integrations to use the supported models before this date. Under default model enablement, the suggested alternatives are automatically enabled for Copilot Enterprise and Copilot Business customers unless an administrator has turned off the global default or explicitly disabled the model. If you’ve turned off the global
Takes effect 8 Dec 2026 · published 12 Nov 2026
GitHub Actions hosted runners will be ending support for ARM32 job execution on Windows and Linux by 8th Dec 2026. This follows our end of support for node20 where Node 24 does not support ARM32.
This includes the removal of support on hosted runners for native AArch32 User-space execution.
Join the discussion within GitHub Community .
The post Actions for ARM32 Linux & Windows retirement appeared first on The GitHub Blog .
Takes effect 10 May 2027 · published 11 Nov 2026
The **Node.js 18 extensibility runtime will progressively become unavailable for selection**, starting with tenants that no longer actively use it. This deprecation affects all extensibility features, including Actions, Custom Database Connections, Custom Social Connections, Rules, and Hooks.
Before the **grace period ends on May 10, 2027**, update your tenant’s default Runtime setting, as well as manually update the runtime for any individual Action still executing on Node.js 18.
Extensibility that remains unmigrated and targets the Node.js 18 runtime will eventually be forced to run on a newer runtime. In addition, any Actions-based Marketplace integrations that depend on the Node.js 18 runtime, and for which the third-party owner or author does not provide an updated version targeting a newer runtime, may become unsupported.
**After the grace period ends, Auth0 will begin the end-of-life phase for the Node.js 18 extensibility runtime, culminating in its complete removal.**
For m
Takes effect 8 Feb 2027 · published 11 Nov 2026
Netlify Visual Editor is deprecated as of November 10, 2026, and will reach end of life on February 8, 2027. After that date, Visual Editor will no longer be available or supported.
Your sites stay live and your content stays right where it is. The only thing that changes is how you make edits.
Timeline
Date: November 10, 2026
What happens: Visual Editor is deprecated. No new teams or projects can enable it.
Date: February 8, 2027
What happens: Visual Editor reaches end of life and is no longer available or supported.
If your team already has Visual Editor enabled, you can keep using it until February 8, 2027, and the Visual Editor docs still apply until then. No new teams or projects can enable Visual Editor.
How to keep editing
The Visual Editor, previously called "Netlify Create", was designed before prompting updates was a common way people worked. Depending on how your team works, here’s how to keep editing:
Using a CMS? Keep editing there. Nothing changes for you.
Alread
Takes effect 10 Feb 2027 · published 10 Nov 2026
The gpt-image-2 model and gpt-image-2-2026-04-21 snapshot are deprecated and will be removed from the API on February 10, 2027.
Shutdown date
Model / system
Recommended replacement
February 10, 2027
gpt-image-2 | gpt-image-2-2026-04-21
gpt-image-2.6-sunburst or gpt-image-2.6-flare
ShopifyhighBreaking change No date announced · published 6 Nov 2026
Starting in API version 2027-01 , in customer account full-page extensions the Navigation API currententrychange event sets event.from to the page the customer navigated away from, instead of the page they navigated to. This is a breaking change for customer account full-page extensions that read the new page from event.from . Update them to read shopify.navigation.currentEntry before you move them to 2027-01 .
What changed
In customer account full-page extensions ( customer-account.page.render and customer-account.order.page.render ), currententrychange passes a NavigationCurrentEntryChangeEvent whose from property is documented as the previous history entry. In API version 2026-10 and earlier, from is the new entry instead, the same value as shopify.navigation.currentEntry . Starting in 2027-01 , from is the previous entry.
Who's affected
Full-page extensions on API version 2027-01 or later that use event.from to find the page the customer navigated to are affected.
Extensions o
ShopifyhighBreaking change No date announced · published 6 Nov 2026
In REST Admin API version 2027-01 and later, the line_item_id property on the Gift Card resource is read-only. Shopify ignores the property in create and update requests. Remove it from those requests before you upgrade.
What changed
In REST Admin API version 2027-01 and later, apps can't add, replace, or clear a gift card's line-item association through Gift Card create or update requests. Shopify ignores any line_item_id value in those requests.
Gift Card responses still include existing line-item and order associations. Earlier API versions keep their current behavior.
Who's affected
This change affects you if all of the following are true:
Your app uses the REST Admin API Gift Card resource.
Your app includes line_item_id when it creates or updates gift cards.
You plan to upgrade your app to API version 2027-01 or later.
If your app only reads line_item_id from Gift Card responses, or stays on an API version earlier than 2027-01, then this change doesn't affect you.
Why t
Takes effect 1 Feb 2027 · published 5 Nov 2026
The gpt-5.5-cyber-preview model is deprecated and will be removed from the API on February 1, 2027. Migrate to the most capable cyber model available to you before the shutdown date.
Shutdown date
Model / system
Recommended replacement
February 1, 2027
gpt-5.5-cyber-preview
The most capable cyber model available to you.
ShopifymediumBreaking change No date announced · published 30 Oct 2026
Shopify Tax managed mode helps Shopify apply the correct tax behavior for US sales by managing some store settings and API behavior directly. To keep those settings consistent, some Admin API writes now validate against the requirements of managed mode.
Managed mode sets requirements that Shopify uses to keep tax behavior consistent across a store. In some cases, the API now prevents apps from writing settings that would conflict with those requirements. In other cases, tax behavior now depends on more specific product or store data instead of simple boolean settings.
For app developers, the main pattern is:
Requests that already use the required settings, or that omit settings the app doesn't need to manage, continue to work.
Requests that try to override managed-mode requirements might now return validation errors.
These changes affect apps that configure markets, publish products, create custom line items, or preview checkout branding for stores that use Shopify Tax managed mod
ShopifyhighBreaking change Takes effect 1 Jan 2027 · published 30 Oct 2026
Public apps still using non-expiring offline access tokens must migrate to use expiring offline access tokens before January 1, 2027 to remain listed in the Shopify App Store and continue accepting new installs.
New client credentials access helps your backend recover access without waiting for a merchant to reopen your app. Using a request signed with your app's private key, your backend can obtain a fresh, short-lived access token without a refresh token.
The enforcement timeline has been updated with incremental penalties for non-compliant apps:
January 1, 2027: Non-compliant apps are delisted from the Shopify App Store and blocked from new installs. Existing installations can continue making affected API requests until April 1.
January 15, 2027: Merchants using non-compliant apps see warnings in Shopify admin about the risk of service interruption and the action they can take.
April 1, 2027: Affected Admin API requests using non-expiring offline access tokens return HTTP 403.
AnthropiccriticalShutdown Takes effect 21 Oct 2026 · published 21 Oct 2026
These models were retired November 6, 2024.
On September 4, 2024, Anthropic notified developers using Claude 1 and Instant models of their upcoming retirements.
Retirement date Deprecated model Recommended replacement
November 6, 2024 claude-1.0 claude-haiku-4-5-20251001
November 6, 2024 claude-1.1 claude-haiku-4-5-20251001
November 6, 2024 claude-1.2 claude-haiku-4-5-20251001
November 6, 2024 claude-1.3 claude-haiku-4-5-20251001
November 6, 2024 claude-instant-1.0 claude-haiku-4-5-20251001
November 6, 2024 claude-instant-1.1 claude-haiku-4-5-20251001
November 6, 2024 claude-instant-1.2 claude-haiku-4-5-20251001
API parameter deprecations
Anthropic occasionally deprecates request parameters that no longer apply to current models. A new model can reject a deprecated parameter, and a new API version can remove it for every model.
Parameter Status Behavior Recommended replacement
temperature , top_p , top_k Removed in API version 2026-10-21 Returns a 400 error . Earlier API versi
No date announced · published 20 Oct 2026
Starting with macOS 27 and Xcode 27, Apple no longer includes Intel (x86_64) code in some of the system binaries and libraries that CodeQL relies on to trace builds. As a result, CodeQL can’t support traced scans on these versions or analyze Swift 6.4.
What’s affected
Xcode 27: When Xcode 27 is installed, traced extraction isn’t available for C/C++, C#, Go, Java, Kotlin, or Swift.
macOS 27: Traced extraction may not be available for the previously mentioned languages.
Swift 6.4: CodeQL doesn’t support Swift 6.4 on any platform.
Intel-based Macs: CodeQL support for Intel-based Macs will be deprecated in mid-December 2026.
How to keep your scans running
If you scan Swift or use traced builds for other languages, pin your workflows to macOS 26 or earlier and Xcode 26 or earlier. If you use GitHub Actions, pin the runner image and toolchain in your workflow rather than relying on the latest versions.
For C/C++, C#, and Java, you can switch to build mode none , which doesn’t require
Takes effect 19 Oct 2026 · published 20 Oct 2026
As of today, October 19, 2026, we have deprecated the following models across most GitHub Copilot experiences (including Copilot Chat, inline edits, ask and agent modes, and code completions).
These deprecations were announced on September 18, 2026 .
Model
Deprecation date
Suggested alternative
Gemini 3.7 Flash
2026-10-19
Gemini 3.8 Flash
GPT-5.5
2026-10-19
GPT-6.1 Sol
GPT-5.4
2026-10-19
GPT-6.1 Sol
GPT-5.4 mini
2026-10-19
GPT-6 Luna
GPT-5 mini
2026-10-19
GPT-6 Luna
Grok 4.5
2026-10-19
Grok 4.7
Please update your workflows and integrations to use supported models. Copilot Enterprise administrators may need to enable access to alternative models through their model policies in Copilot settings. As an administrator, you can verify availability by checking your individual Copilot settings and confirming that the policy is enabled for the specific model. Once enabled, you’ll see the model in the Copilot Chat model selector in VS Code and on github.com. No action is required to rem
Takes effect 16 Nov 2026 · published 15 Oct 2026
We will deprecate the following models across all GitHub Copilot experiences (including Copilot Chat, inline edits, ask and agent modes, and code completions) on November 16th, 2026:
Model
Deprecation date
Suggested alternative
Claude Opus 4.8*
2026-11-16
Claude Opus 5.5
Claude Opus 5
2026-11-16
Claude Opus 5.5
GPT-5.6 Terra
2026-11-16
GPT-6.1 Sol or GPT-6 Luna
*Claude Opus 4.8 will remain available to individual GitHub Copilot subscribers on annual plans so they retain an Opus offering. The deprecation of Claude Opus 4.8 does not apply to these customers.
Please update your workflows and integrations to use the supported models before this date. Under default model enablement, the suggested alternatives are automatically enabled for Copilot Enterprise and Copilot Business customers unless an administrator has turned off the global default or explicitly disabled the model. If you’ve turned off the global default, you can enable access to the alternative models through their model
Takes effect 15 Oct 2026 · published 15 Oct 2026
As of October 15, 2026, email notifications for repository push events have been retired and are no longer sent.
We shut down this feature to help prevent spam and abuse. Because recipients didn’t have to consent before receiving these emails, the feature could be misused to send unwanted messages through GitHub’s email infrastructure.
To continue sending email notifications for repository push events, you can use a GitHub Actions workflow triggered by push events to send emails through your own SMTP server or email provider.
The post Email notifications for repository push events have been retired appeared first on The GitHub Blog .
Takes effect 14 Jan 2027 · published 13 Oct 2026
On October 14, 2026, we notified developers using certain GPT-4 series models of their deprecation and removal from the API on January 14, 2027.
Shutdown date
Model / system
Recommended replacement
January 14, 2027
GPT-4o ( gpt-4o-2024-08-06 , gpt-4o-2024-11-20 )
gpt-6-luna
January 14, 2027
GPT-4o mini ( gpt-4o-mini-2024-07-18 )
gpt-6-luna
January 14, 2027
GPT-4.1 ( gpt-4.1-2025-04-14 )
gpt-6-luna
January 14, 2027
GPT-4.1 mini ( gpt-4.1-mini-2025-04-14 )
gpt-6-luna
Fine-tuned versions of these models follow the same shutdown schedule as their underlying base models.
ShopifyhighBreaking change No date announced · published 11 Oct 2026
In POS UI extensions API version 2026-10 , Cart API mutations reject when Shopify POS doesn't confirm that the cart changed. In earlier versions these mutations resolve whether or not POS applied the write. This is a breaking change for apps that adopt 2026-10 , and those apps need to handle a rejected promise on every cart mutation they call. Apps on 2026-07 and earlier are unaffected.
What changed
POS reports the outcome of every cart write. Only a success result confirms that the cart changed. Earlier API versions resolve the mutation regardless of that result, so an app can't tell an applied write from a dropped one, and an app can show a fee or a discount as applied when the cart never changed.
In 2026-10 , these mutations reject unless POS confirms the write: bulkCartUpdate , removeLineItem , applyCartDiscount , addCartCodeDiscount , removeAllDiscounts , setCustomer , removeCustomer , addLineItemProperties , bulkAddLineItemProperties , removeLineItemProperties , setLineItemDis
Takes effect 2 Nov 2026 · published 11 Oct 2026
The Global Catalog REST API, which was deprecated in April 2026, stops serving traffic on November 2, 2026. If your app still calls it, you need to migrate to Global Catalog MCP, which implements the Universal Commerce Protocol (UCP), before that date.
Google CloudmediumDeprecation No date announced · published 6 Oct 2026
Identity Service for GKE is deprecated in GKE 1.36 and earlier (since July 1, 2026) and is not supported in GKE 1.37 and later. Before upgrading clusters to 1.37, disable the feature and migrate to Workforce Identity Federation.
ShopifymediumBreaking change No date announced · published 4 Oct 2026
As of API version 2027-01 , the metafieldInteger collection source condition inputs and types is removed from GraphQL Admin API. If you use metafieldInteger to create or read collection source conditions, you need to migrate to metafieldInt before you upgrade to API version 2027-01 .
What changed
With metafieldInt , the value field on integer metafield conditions changes type from Int to String , to align with the metafield value field on the Storefront API. For details, see the Storefront Metafield.value field reference .
The following types and fields are replaced:
CollectionSourceInclusionConditionMetafieldInteger is replaced by CollectionSourceInclusionConditionMetafieldInt
CollectionSourceInclusionConditionMetafieldIntegerRelation is replaced by CollectionSourceInclusionConditionMetafieldIntRelation
CollectionSourceInclusionConditionInput.metafieldInteger is replaced by CollectionSourceInclusionConditionInput.metafieldInt
CollectionSourceInclusionConditionUpdateInput.metafi