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.
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
ShopifymediumBreaking change No date announced · published 4 Oct 2026
As of GraphQL Admin API version 2026-10, functions in the segment query language now use the operators MATCHES / NOT MATCHES instead of = true / = false . For example, the previous query shopify_email.opened() = true would now be represented as shopify_email.opened MATCHES () .
The parameters for each function have also been expanded to use their own operators. For example, the query products_purchased(quantity: 5) = true would now be represented as products_purchased MATCHES (quantity = 5) . This expands the functionality of parameters. For example, the following queries were not possible before: products_purchased MATCHES (quantity != 5) , products_purchased MATCHES (quantity > 5) .
Additionally, the following named dates have been deprecated: 12_months_ago , 90_days_ago , 30_days_ago , 7_days_ago . Instead, the you can use the existing date offsets in your segment queries. For example, the named date 12_months_ago is equivalent to the date offset -12m .
Learn more about customer
ShopifymediumBreaking change No date announced · published 4 Oct 2026
We’re reducing the query complexity limit for Events subscriptions from 250 to 100 points. This change does not affect Classic Webhooks.
Shopify assigns each Events query a complexity score based on the fields it selects, the types of data those fields return, and the number of items requested in connections using first or last, following the GraphQL query cost calculation . The limit applies to each subscription query, and queries executed by Events subscriptions don’t count toward your app’s API rate limits .
What to do
Review subscription queries that exceed 100 points and shape each subscription around the changes your app handles:
Split subscriptions by the work they do : You can configure multiple subscriptions for the same topic, each with its own triggers and query.
Query the changed resource directly : For example, for a variant price change, query the affected variant’s price, SKU, and parent Product ID instead of fetching the Product’s first 250 variants. This avoids re
ShopifyhighBreaking change No date announced · published 4 Oct 2026
The deprecated automaticDiscounts query is removed from the GraphQL Admin API in version 2027-01 . If your app reads a shop’s automatic discounts through automaticDiscounts , you need to move to the discountNodes query with a method:automatic filter before you upgrade to 2027-01 . Apps on 2026-10 and earlier keep working unchanged while those versions are supported.
What changed
As of API version 2027-01 , automaticDiscounts no longer exists on QueryRoot . Requests that include automaticDiscounts on 2027-01 return a validation error instead of data. The DiscountAutomaticConnection and DiscountAutomaticEdge types are also removed, because no other fields in the schema return them.
Use discountNodes instead, with query: "method:automatic" . It returns a connection of DiscountNode objects, each exposing the discount itself on the discount field. discountNodes accepts filters similar to the removed query, including status , discount_type , discount_class , created_at , and starts_at . F
Takes effect 1 Jan 2027 · published 4 Oct 2026
The AWS CRT for JavaScript is adopting a policy that aligns with the official Node.js release schedule , providing a predictable timeline for when support for older Node.js versions is dropped. The AWS IoT Device SDK for JavaScript v2 is built on top of AWS CRT for JavaScript, so it shares the same minimum Node.js version. When AWS CRT for JavaScript drops a Node.js version, the AWS IoT Device SDK for JavaScript v2 drops it at the same time.
New support policy
Currently, AWS CRT for JavaScript and AWS IoT Device SDK for JavaScript v2 still support Node.js 14.x, which reached end of life in April 2023. Starting in January 2027, AWS CRT for JavaScript and AWS IoT Device SDK for JavaScript v2 will begin dropping support for end-of-life Node.js versions following the Node.js release schedule.
Under this policy, AWS CRT for JavaScript and AWS IoT Device SDK for JavaScript v2 will support each Node.js LTS version until 8 months past its end-of-life date, in line with the AWS SDKs and Tool
ShopifymediumBreaking change No date announced · published 4 Oct 2026
As of API version 2026-10, the static session.currentSession.staffMemberId field has been removed from the POS UI Extensions Session API. It was deprecated in 2026-07 in favour of session.staffMember, a reactive signal that updates when a different staff member pins into POS.
Before targeting API version 2026-10, replace reads of session.currentSession.staffMemberId with session.staffMember.value?.id. To react to staff changes while your extension is running, subscribe to the signal with session.staffMember.subscribe((staffMember) => { ... }), or read .value during render in a Preact component with @shopify/ui-extensions/preact imported to re-render automatically.
Extensions on 2026-07 and earlier are unaffected. The BaseData session.staffMemberId available to receipt targets is a separate API and is unchanged.
https://shopify.dev/docs/api/pos-ui-extensions/2026-10/apis/session-api
ShopifyhighBreaking change No date announced · published 4 Oct 2026
Starting today, we're updating Events payloads, trigger syntax, and delivery headers. Classic Webhook subscriptions are unaffected.
What's changed
fields_changed now describes how each path changed
The flat array becomes an object containing three arrays: added , updated , and removed .
Developers can distinguish a resource or relationship being added, a value being updated, or a resource or relationship being removed without querying just to infer what happened.
Update payload handling to read fields_changed.added , fields_changed.updated , and fields_changed.removed . Adding a variant to a Product, for example, keeps the Product's action as update and places the variant path in fields_changed.added .
Before:
{
"topic": "Product",
"action": "update",
"fields_changed": [
"product[id: 'gid://shopify/Product/123'].variants[id: 'gid://shopify/ProductVariant/456']"
]
}
After:
{
"topic": "Product",
"action": "update",
"fields_changed": {
"added": [
"product[id: 'gid://shopify/Produ
Auth0mediumBreaking change No date announced · published 4 Oct 2026
As part of our commitment to maintaining the highest security and compliance standards, we will soon be updating our authentication service configuration to increase the length and entropy of our refresh tokens.
## What is changing?
We are increasing the cryptographic entropy of our issued Refresh Tokens. As a result, the string length of newly issued Refresh Tokens will increase beyond the current ~45-character baseline.
## Why is this changing?
Higher entropy ensures that refresh tokens are even more resilient against brute-force attacks and key-guessing attempts. [Auth0's lifecycle policies](https://auth0.com/docs/troubleshoot/product-lifecycle#backward-compatible-non-breaking-changes) explicitly note that token formats and lengths are non-deterministic and subject to change without deprecation notices. However, we want to proactively notify you to ensure a seamless transition for your integrations.
## Who is impacted?
You may be impacted if your client applications, APIs, or data
Takes effect 28 Sept 2026 · published 4 Oct 2026
Agent Platform Workbench
Change
20260927.00_p0 Release
Change
Installed latest packages from upstream dependencies.
Security
Bulk security patch remediating Critical and High-severity CVEs in the Workbench custom container images.
Change
20260927.00_p0 Release
Change
Installed latest packages from upstream dependencies.
Security
Bulk security patch remediating Critical and High-severity CVEs in the Workbench custom container images.
Application Integration
Security
A Confused Deputy vulnerability was discovered in the Email Task component in
Application Integration versions prior to June 30, 2026.
For more information, see the
GCP-2026-066
security bulletin.
Security
A Deserialization of Untrusted Data vulnerability was discovered in
the JavaScript Task in Application Integration versions prior
to June 28, 2026. For more information, see the
GCP-2026-065
security bulletin.
Security
An Incorrect Authorization vulnerability was discovered in the task
configuration in A
Takes effect 4 Jan 2027 · published 4 Oct 2026
We’re updating TypeScript version support in the AWS SDK for JavaScript v3 . Starting January 4, 2027, the SDK will require TypeScript versions published within the last 2.5 years. Read on to learn what’s changing, why this change is necessary, and what actions you may need to take.
We built the AWS SDK for JavaScript with TypeScript-first development in mind, designed to deliver smaller artifacts while taking advantage of modern TypeScript features. This support policy update also aligns the SDK with the broader TypeScript ecosystem.
What’s changing and why
This change applies only if you use TypeScript with the AWS SDK for JavaScript v3.
The TypeScript ecosystem has broadly converged on supporting only recent compiler versions:
DefinitelyTyped , the central repository for community-maintained TypeScript type definitions (hosting types for 8,000+ npm packages including @types/node and @types/react ), only tests packages against TypeScript versions less than 2 years old. For more
Takes effect 2 Nov 2026 · published 4 Oct 2026
The macOS 14 runner image will be retired on November 2, 2026. To raise awareness of the upcoming removal, jobs using macOS 14 will temporarily fail during the following scheduled brownout periods:
October 5, 14:00 UTC to October 6, 00:00 UTC
October 12, 14:00 UTC to October 13, 00:00 UTC
October 16, 14:00 UTC to October 17, 00:00 UTC
October 19, 14:00 UTC to October 20, 00:00 UTC
October 23, 14:00 UTC to October 24, 00:00 UTC
October 26, 14:00 UTC to October 27, 00:00 UTC
October 29, 14:00 UTC to October 30, 00:00 UTC
October 30, 14:00 UTC to October 31, 00:00 UTC
This deprecation includes the following labels:
macos-14
macos-14-large
macos-14-xlarge
During the lead-up to retirement, GitHub may reduce macOS 14 runner capacity, which could result in longer queue times for jobs that continue to use these labels.
What you need to do
Update your workflow files to use one of the following macOS arm64 labels:
macos-latest ( macos-26 )
macos-15
macos-latest-xlarge ( macos-2
Takes effect 30 Nov 2026 · published 4 Oct 2026
The staged rollout of the stateless GitHub App installation token format, which began on April 27, 2026, is complete. By default, all newly minted GitHub App installation tokens will be in the stateless ghs_APPID_JWT format, which makes token issuance and validation faster and improves the reliability of the GitHub API.
What’s changed
Installation tokens still start with the ghs_ prefix, but they’re now about 520 characters long instead of 40.
Token permissions, repository scoping, the one-hour expiration, and the installation access token REST API endpoint are unchanged. Tokens minted before the change continue to work until they expire.
What to expect going forward
The temporary X-GitHub-Stateless-S2S-Token request header, which we introduced so you could validate the new format on demand, will be deprecated on November 30, 2026. After that date, GitHub will no longer respect the header, and all eligible apps will always receive stateless tokens. To learn more about the temporar
Takes effect 30 Nov 2026 · published 4 Oct 2026
On September 30, 2026, Anthropic notified developers using Claude Sonnet 4.5 of its upcoming retirement on the Claude API.
Retirement date Deprecated model Recommended replacement
November 30, 2026 claude-sonnet-4-5-20250929 claude-sonnet-5-5
Takes effect 23 Oct 2026 · published 4 Oct 2026
To improve reliability and make it easier for developers to choose the right models, we are deprecating a set of older OpenAI models. Access to these models will be shut down on the dates below.
Shutdown date
Model snapshot
Substitute model
October 23, 2026
gpt-3.5-turbo-0125 | gpt-3.5-turbo , gpt-3.5-turbo-completions
gpt-5.6-terra
October 23, 2026
gpt-4-0613 | gpt-4 , gpt-4-0613-completions , gpt-4-completions
gpt-5.6-sol
October 23, 2026
gpt-4-1106-preview
gpt-5.6-sol
October 23, 2026
gpt-4-turbo | gpt-4-turbo-2024-04-09 , gpt-4-turbo-completions
gpt-5.6-sol
October 23, 2026
gpt-4.1-nano | gpt-4.1-nano-2025-04-14
gpt-5.6-luna
October 23, 2026
gpt-4o-2024-05-13
gpt-5.6-sol
October 23, 2026
gpt-image-1
gpt-image-2.5-sunburst or gpt-image-2.5-flare
October 23, 2026
o1-2024-12-17 | o1
gpt-5.6-sol
October 23, 2026
o1-pro-2025-03-19 | o1-pro
gpt-5.6-sol ( reasoning.mode: pro )
October 23, 2026
o3-mini-2025-01-31 | o3-mini
gpt-5.6-sol
October 23, 2026
ft-o4-mini-2025-04-16
gpt-
OpenAIhighBreaking change Takes effect 6 Jan 2027 · published 4 Oct 2026
On May 7th, 2026, we notified developers using OpenAI’s self-serve fine-tuning platform of updates to availability.
Inference on fine-tuned models will continue to be available until the base models are deprecated.
Date
Update
May 7, 2026
Creating fine-tuning jobs or training is not available to organizations that have not previously run fine-tuning.
July 2, 2026
Creating fine-tuning jobs is no longer available to organizations that have not run inference on a fine-tuned model in the past 60 days.
Jan 6, 2027
Active existing customers will no longer be able to create new fine-tuning jobs on this date. Inference on fine-tuned models will be disabled only when the underlying base model is deprecated.
Past deprecations
Past deprecations are listed below, with the most recent announcements at the top.
Takes effect 1 Dec 2026 · published 4 Oct 2026
On June 2, 2026, we notified developers using older GPT Image models of their deprecation and removal from the API on December 1, 2026.
Shutdown date
Model / system
Recommended replacement
Dec 1, 2026
gpt-image-1-mini
gpt-image-2.5-sunburst or gpt-image-2.5-flare
Dec 1, 2026
gpt-image-1.5
gpt-image-2.5-sunburst or gpt-image-2.5-flare
Dec 1, 2026
chatgpt-image-latest
gpt-image-2.5-sunburst or gpt-image-2.5-flare
Takes effect 30 Nov 2026 · published 4 Oct 2026
On June 3, 2026, we notified developers using Agent Builder that the product is being deprecated. ChatKit remains available.
Date
Update
June 3, 2026
Deprecation announced for Agent Builder.
Nov 30, 2026
Agent Builder is scheduled to shut down.
See Migrate from Agent Builder to continue with the Agents SDK or ChatGPT Workspace Agents.
Takes effect 30 Nov 2026 · published 4 Oct 2026
On June 3, 2026, we notified developers using the Evals platform that the product is being deprecated.
Date
Update
June 3, 2026
Deprecation announced for the Evals platform.
Oct 31, 2026
Existing evals become read-only.
Nov 30, 2026
The Evals dashboard and API are scheduled to shut down.
Graders documented for eval workflows are part of this transition. Fine-tuning-related timelines remain covered in the self-serve fine-tuning section below.
See Moving from OpenAI Evals to Promptfoo for a migration path.
Takes effect 30 Nov 2026 · published 4 Oct 2026
On June 3, 2026, we notified developers using reusable prompts in the dashboard and API that reusable prompt objects are being deprecated.
Date
Update
June 3, 2026
Deprecation announced and prompt creation de-emphasized in the platform.
Nov 30, 2026
The v1/prompts API and reusable prompt objects are scheduled to shut down.
To migrate, move reusable prompt content into your application code. See Migrate from prompt objects .
Takes effect 11 Dec 2026 · published 4 Oct 2026
On June 11, 2026, we notified developers using older GPT-5 and o3 model snapshots of their deprecation and removal from the API on December 11, 2026.
Shutdown date
Model / system
Recommended replacement
Dec 11, 2026
gpt-5-2025-08-07
gpt-5.6-sol
Dec 11, 2026
gpt-5-mini-2025-08-07
gpt-5.6-terra
Dec 11, 2026
gpt-5-nano-2025-08-07
gpt-5.6-luna
Dec 11, 2026
gpt-5-pro-2025-10-06
gpt-5.6-sol ( reasoning.mode: pro )
Dec 11, 2026
o3-2025-04-16
gpt-5.6-sol
Dec 11, 2026
o3-pro-2025-06-10
gpt-5.6-sol ( reasoning.mode: pro )
Takes effect 20 Jan 2027 · published 4 Oct 2026
On July 20, 2026, we notified developers using legacy audio, realtime, and transcription model families and snapshots of their deprecation and removal from the API on January 20, 2027.
Shutdown date
Model family / snapshot
Recommended replacement
Jan 20, 2027
gpt-realtime
gpt-realtime-2.1
Jan 20, 2027
gpt-audio
gpt-audio-1.5
Jan 20, 2027
gpt-4o-audio
gpt-audio-1.5
Jan 20, 2027
gpt-4o-realtime
gpt-realtime-2.1
Jan 20, 2027
gpt-realtime-mini
gpt-realtime-2.1-mini
Jan 20, 2027
gpt-audio-mini
gpt-audio-1.5
Jan 20, 2027
gpt-4o-mini-realtime
gpt-realtime-2.1-mini
Jan 20, 2027
gpt-4o-mini-audio
gpt-audio-1.5
Jan 20, 2027
gpt-4o-mini-transcribe-2025-03-20
gpt-4o-mini-transcribe-2025-12-15
Takes effect 26 Feb 2027 · published 4 Oct 2026
On August 26, 2026, we notified developers using whisper-1 , gpt-4o-transcribe , gpt-4o-mini-transcribe , and gpt-4o-transcribe-diarize of their deprecation and removal from the API on February 26, 2027.
For information about the recommended replacements, see the transcription guide .
Shutdown date
Model / system
Recommended replacement
Feb 26, 2027
whisper-1
gpt-live-transcribe or gpt-transcribe
Feb 26, 2027
gpt-4o-transcribe
gpt-live-transcribe or gpt-transcribe
Feb 26, 2027
gpt-4o-mini-transcribe
gpt-live-transcribe or gpt-transcribe
Feb 26, 2027
gpt-4o-transcribe-diarize
gpt-live-transcribe or gpt-transcribe
Takes effect 6 Jan 2027 · published 4 Oct 2026
The following text-to-speech models are deprecated and will be removed from the API on January 6, 2027, with at least three months’ notice. Migrate to gpt-realtime-2.1-mini before the shutdown date. See the Realtime API guide to plan your migration.
Shutdown date
Model / system
Recommended replacement
Jan 6, 2027
tts-1
gpt-realtime-2.1-mini
Jan 6, 2027
tts-1-hd
gpt-realtime-2.1-mini
Jan 6, 2027
gpt-4o-mini-tts-2025-03-20
gpt-realtime-2.1-mini
Jan 6, 2027
gpt-4o-mini-tts-2025-12-15
gpt-realtime-2.1-mini
Takes effect 1 Apr 2027 · published 4 Oct 2026
The following models are deprecated and will be removed from the API on April 1, 2027, with six months’ notice. Migrate to the recommended replacements before the shutdown date.
Shutdown date
Model / system
Recommended replacement
Apr 1, 2027
gpt-5.3-codex
gpt-6-sol
Apr 1, 2027
gpt-5.4-nano
gpt-6-luna
Apr 1, 2027
gpt-5.1
gpt-6-sol