{"changes":[{"vendor":"Azure Communication Services","change_type":"product_deprecated","date":"2028-09-30","summary":"Azure Communication Services' standalone services retire on September 30, 2028. Retired services include Email, SMS, WhatsApp messaging, Chat, Rooms, number management, Job Router, Direct Routing and the UI Library SDKs. Customers without an ACS resource created before October 23, 2026 cannot acquire phone numbers for SMS or PSTN calling. Voice and video calling stay available after 2028 only with Microsoft Teams integrations, on new SDK major versions.","previous_state":"Azure Communication Services offered standalone email, SMS, WhatsApp, chat and calling APIs, open to new customers, with no announced retirement.","current_state":"Microsoft Learn's \"ACS retirement and breaking changes guide\" (read 2026-11-13): \"On September 23, 2026, Microsoft announced the retirement of Azure Communication Services (ACS) as a standalone offering, effective September 30, 2028.\" \"Customers with an Azure Communication Services resource created before October 23, 2026, can continue using their existing resources\"; customers without one \"will not be able to acquire phone numbers for retiring telephony workloads, including PSTN calling and SMS.\"","impact":"high","source_url":"https://learn.microsoft.com/en-us/azure/communication-services/acs-retirement-and-breaking-changes-guide","category":"Communication","alternatives":[],"recorded_date":"2026-11-13","date_source":"vendor_page","listing_effect":"none","what_ends":"Azure Communication Services (ACS) standalone services","announced_on":"2026-09-23","standing":"in_force","date_meaning":"effective","ends_a_free_tier":false},{"vendor":"Azure","change_type":"product_deprecated","date":"2028-09-30","summary":"Microsoft retires the Basic, Standard and Premium tiers of Azure Cache for Redis on September 30, 2028. From October 1, 2028 every remaining Basic, Standard or Premium cache is disabled. Since April 1, 2026 new customers in Azure's public cloud cannot create caches in these tiers. A tenant that had any Azure Cache for Redis instance before April 1, 2026 can keep creating them until the retirement. Reservations are supported until September 30, 2028. Microsoft's replacement is Azure Managed Redis. Applications must switch to the new cache's hostname and access key. Azure Managed Redis is clustered by default, so the client library must be set up for a clustered cache.","what_ends":"Azure Cache for Redis Basic, Standard and Premium tiers","previous_state":"Azure Cache for Redis Basic, Standard and Premium caches run normally, and existing customers can still create them.","current_state":"Microsoft Learn's \"Azure Cache for Redis retirement FAQ\" (last updated 2026-08-18, read 2026-11-15): \"All instances of Azure Cache for Redis tiers (Basic, Standard, and Premium) will be retired on September 30, 2028.\" \"All remaining Azure Cache for Redis Basic, Standard, and Premium instances are disabled starting October 1, 2028.\" \"Your existing reservations will be supported until September 30, 2028.\" \"All client applications need to update the Redis hostname and access key from existing Azure Cache for Redis instance to the corresponding Azure Managed Redis instance.\" \"Azure Managed Redis instances are clustered by default, so your application must configure your client library to work with a clustered Redis instance.\" Microsoft Learn's \"What's New in Azure Cache for Redis\" (read 2026-11-15), July 2026: \"Your tenant qualifies as an existing customer if any subscription in the tenant had an Azure Cache for Redis instance before April 1, 2026.\" Azure public cloud, April 1, 2026: \"Creating new caches is blocked for new customers. Existing customers can continue creating caches until retirement.\"","impact":"medium","source_url":"https://learn.microsoft.com/en-us/azure/azure-cache-for-redis/retirement-faq","category":"Databases","alternatives":[],"recorded_date":"2026-11-15","date_source":"vendor_page","listing_effect":"none","standing":"in_force","date_meaning":"effective","ends_a_free_tier":false},{"vendor":"Microsoft Dev Box","change_type":"product_deprecated","date":"2028-09-18","summary":"Microsoft Dev Box retires on September 18, 2028. Its closing-down period began on September 14, 2026. It is in maintenance mode with no new features planned. Microsoft recommends Windows 365 as the replacement.","previous_state":"Microsoft Dev Box offered self-service cloud developer workstations, with no announced retirement.","current_state":"Microsoft Learn's \"What is Microsoft Dev Box?\" (read 2026-11-13): \"Microsoft Dev Box retires at 17:00 UTC on 18 September 2028.\" \"The service begins its closing-down period at 16:00 UTC on 14 September 2026.\"","impact":"medium","source_url":"https://learn.microsoft.com/en-us/azure/dev-box/overview-what-is-microsoft-dev-box","category":"Developer Tools","alternatives":[],"recorded_date":"2026-11-13","date_source":"vendor_page","listing_effect":"none","what_ends":"Microsoft Dev Box","announced_on":"2026-10-08","standing":"in_force","date_meaning":"effective","ends_a_free_tier":false},{"vendor":"Google Gemini API","change_type":"product_deprecated","date":"2028-05-14","summary":"The Gemini API keeps running. The embedding model gemini-embedding-001 can be called until May 14, 2028, when Google shuts it down. Google names gemini-embedding-2 as the replacement.","previous_state":"gemini-embedding-001 could be called on the Gemini API.","current_state":"Google's deprecations page (last updated 2026-10-09) lists May 14, 2028 as the shutdown date for gemini-embedding-001, with gemini-embedding-2 as the replacement.","impact":"low","source_url":"https://ai.google.dev/gemini-api/docs/deprecations","category":"AI / ML","alternatives":[],"recorded_date":"2026-10-10","date_source":"hand_written","listing_effect":"none","what_ends":"the gemini-embedding-001 embedding model","standing":"in_force","date_meaning":"effective","ends_a_free_tier":false},{"vendor":"Auth0","change_type":"product_deprecated","date":"2028-01-31","date_source":"vendor_page","summary":"Auth0 keeps running. Auth0 Rules reach end of life on January 31, 2028, when they stop running and are removed. They have been read-only since November 18, 2024, and tenants created from October 16, 2023 never had them. Auth0 says to move to Actions.","what_ends":"Auth0 Rules","listing_effect":"none","previous_state":"Auth0 Rules ran custom code in the login pipeline. Auth0 deprecated them on May 16, 2023 and made them read-only on November 18, 2024.","current_state":"\"After January 31, 2028, Rules stop running and are removed.\" (auth0.com/docs, Rules)","impact":"medium","source_url":"https://auth0.com/docs/customize/rules","category":"Auth","alternatives":[],"recorded_date":"2026-10-31","standing":"in_force","date_meaning":"effective","ends_a_free_tier":false},{"vendor":"AWS","change_type":"product_deprecated","date":"2027-11-07","summary":"After November 7, 2027, Amazon OpenSearch Service isolates every domain still running Elasticsearch 1.5, 2.3, 5.1, 5.3, 5.5, 6.0, 6.2, 6.3, 6.4, 6.5, 6.7, 7.1, 7.4, 7.7 or 7.8, or OpenSearch 1.0, 1.1, 1.2, 2.3, 2.5, 2.7 or 2.9. Isolated domains can no longer be accessed. AWS keeps their data for at least 30 days. Data must be restored into a new domain on a supported version. New domains cannot be created on these versions after that date. Since November 7, 2026, these domains have paid an Extended Support surcharge equal to their instance price, doubling the cost. Elasticsearch 1.5 and 2.3 domains cannot be upgraded in place. Upgrading before November 7, 2027 stops the surcharge and avoids isolation.","what_ends":"Amazon OpenSearch Service domains on Elasticsearch 1.5, 2.3, 5.1, 5.3, 5.5, 6.0, 6.2, 6.3, 6.4, 6.5, 6.7, 7.1, 7.4, 7.7 and 7.8, and OpenSearch 1.0, 1.1, 1.2, 2.3, 2.5, 2.7 and 2.9","previous_state":"Amazon OpenSearch Service domains on these versions run normally under paid Extended Support and receive critical security patches.","current_state":"AWS, OpenSearch Service FAQ (read 2026-11-15), Extended Support: \"After November 7, 2027, domains on these versions will be isolated.\" \"Domains running unsupported versions will be isolated and data preserved for at least 30 days. Isolated domains can no longer be accessed, and you will have to restore data into a new domain running a supported version.\" \"new domain creation will no longer be available after Extended Support ends for a version.\" \"When you are moving from legacy versions like ES 1.5 or ES 2.3, we do not support in-place upgrades.\" AWS, What is Amazon OpenSearch Service?, Standard and extended support: \"Updated End of Extended Support\" November 7, 2027 for Elasticsearch versions 1.5 and 2.3, 5.1 to 5.5, 6.0 to 6.7 and 7.1 to 7.8, and OpenSearch versions 1.0 to 1.2 and 2.3 to 2.9.","impact":"medium","source_url":"https://aws.amazon.com/opensearch-service/faqs/","category":"Search","alternatives":[],"recorded_date":"2026-11-15","date_source":"vendor_page","listing_effect":"none","standing":"in_force","date_meaning":"effective","ends_a_free_tier":false},{"vendor":"Firebase","change_type":"product_deprecated","date":"2027-09-30","date_source":"vendor_page","summary":"Firebase keeps running. Firebase Test Lab can be used until September 30, 2027. After that date, no tests can run. Google's replacement is the Developer Device Platform on Google Cloud. The Developer Device Platform requires billing. The no-cost Spark plan includes 10 virtual-device tests a day and 5 physical-device tests a day.","what_ends":"Firebase Test Lab","listing_effect":"none","previous_state":"Firebase Test Lab ran app tests on virtual and physical Android and iOS devices in Google's data centers, with no announced shutdown date.","current_state":"\"Firebase Test Lab is deprecated and will be fully shut down on September 30, 2027.\" \"you won't be able to run any workflows after September 30, 2027. The Firebase Test Lab console and API will be shut down.\" \"While Firebase Test Lab supported some usage without billing, the Developer Device Platform requires your project to have billing enabled.\" (firebase.google.com/docs/test-lab/migrate-faq)","impact":"medium","source_url":"https://firebase.google.com/docs/test-lab/migrate-faq","category":"Testing","alternatives":[],"recorded_date":"2026-10-30","standing":"in_force","date_meaning":"effective","ends_a_free_tier":false},{"vendor":"Amazon DevOps Guru","change_type":"product_deprecated","date":"2027-09-30","summary":"Amazon DevOps Guru shuts down on September 30, 2027. New customers have not been able to sign up since October 29, 2026. Existing customers can use it until September 30, 2027. After that date, the console and API become unavailable, past insights are no longer retrievable, and stacks declaring AWS::DevOpsGuru::ResourceCollection or AWS::DevOpsGuru::NotificationChannel fail to create or update. Running workloads are not interrupted. AWS recommends Amazon CloudWatch and Amazon DevOps Agent.","previous_state":"Amazon DevOps Guru offered ML-based operational anomaly detection and insights, open to new customers, with no announced end.","current_state":"AWS's \"Amazon DevOps Guru end of support\" (read 2026-11-12): \"Amazon DevOps Guru will stop accepting new customers on October 29, 2026. Current customers will not be impacted and can continue using Amazon DevOps Guru until September 30, 2027. After September 30, 2027 you will no longer be able to access Amazon DevOps Guru.\"","impact":"medium","source_url":"https://docs.aws.amazon.com/devops-guru/latest/userguide/devops-guru-end-of-support.html","category":"Monitoring","alternatives":[],"recorded_date":"2026-11-13","date_source":"vendor_page","listing_effect":"none","what_ends":"Amazon DevOps Guru","announced_on":"2026-09-29","standing":"in_force","date_meaning":"effective","ends_a_free_tier":false},{"vendor":"Functions on Azure Container Apps V1","change_type":"product_deprecated","date":"2027-09-29","summary":"Functions on Azure Container Apps V1 retires on September 29, 2027. After that date V1 function apps stop running and stop processing requests and triggers. Migrate to Functions on Azure Container Apps V2, a native Container App with kind=functionapp, using the same container image and no function code changes in the standard path. Azure Functions and Azure Container Apps keep running.","previous_state":"Azure Functions apps could be hosted on Azure Container Apps through the V1 hosting model, with no announced retirement.","current_state":"Azure Updates (posted 2026-09-29, read 2026-11-13): \"The Functions on Azure Container Apps (ACA) V1 will be retired on September 29, 2027. After this date, existing Functions on ACA V1 Apps will stop running and no longer process requests or event-driven triggers.\"","impact":"medium","source_url":"https://azure.microsoft.com/updates?id=570800","category":"Serverless","alternatives":[],"recorded_date":"2026-11-13","date_source":"vendor_page","listing_effect":"none","what_ends":"Functions on Azure Container Apps V1","announced_on":"2026-09-29","standing":"in_force","date_meaning":"effective","ends_a_free_tier":false},{"vendor":"Google Cloud Video Intelligence API","change_type":"product_deprecated","date":"2027-09-14","summary":"Google Cloud Video Intelligence API shuts down on September 14, 2027. It has been deprecated and unsupported since September 14, 2026, and can be used until its shutdown. Google recommends migrating to its Gemini family of models.","previous_state":"Google Cloud Video Intelligence API offered label, shot and object detection on video, with 1,000 free units a month on the Google Cloud free tier and no announced end.","current_state":"Google Cloud's \"Video Intelligence API Deprecations\" (read 2026-11-13): \"Starting on September 14, 2026, Video Intelligence API is officially deprecated and will no longer be supported. You can continue using Video Intelligence API until September 14, 2027, when it will be shut down. We recommend migrating to Gemini family of models.\"","impact":"medium","source_url":"https://docs.cloud.google.com/video-intelligence/docs/deprecations","category":"AI/ML","alternatives":[],"recorded_date":"2026-11-13","date_source":"vendor_page","listing_effect":"none","what_ends":"Google Cloud Video Intelligence API","announced_on":"2026-09-14","standing":"in_force","date_meaning":"effective","ends_a_free_tier":false},{"vendor":"AWS","change_type":"product_deprecated","date":"2027-08-31","summary":"AWS Lambda blocks creating new functions on its deprecated runtimes from July 29, 2027. It blocks updating the code and configuration of existing functions from August 31, 2027. AWS is delaying these blocks beyond its usual 30 and 60 days after deprecation. Functions on .NET 8, Python 3.10 and the other deprecated runtimes can still be created and updated until those dates through the AWS CLI, AWS SAM or CloudFormation, not the Lambda console. After both dates, existing functions can still be invoked and can still be switched to a supported runtime. Deprecated runtimes include Node.js 16, 18 and 20; Python 3.8, 3.9 and 3.10; Ruby 3.2; .NET 6 and 8; and provided.al2. Python 3.10 was deprecated on October 31, 2026 and .NET 8 on November 10, 2026. These runtimes are deprecated next and get the same two dates: Ruby 3.3 on March 31, 2027, Node.js 22 on May 30, 2027, and Python 3.11 and Java 8, 11 and 17 on Amazon Linux 2 on June 30, 2027. Older runtimes are the exception: functions on Node.js 14, Python 3.7, Ruby 2.7, Go 1.x, Java 8 on Amazon Linux and provided can no longer be created since 2024 and can no longer be updated from August 31, 2027.","what_ends":"AWS Lambda's deprecated runtimes: Python 3.8, 3.9 and 3.10, Node.js 16, 18 and 20, .NET 6 and 8, Ruby 3.2 and provided.al2","previous_state":"Before AWS set block dates, functions on these runtimes could be created and updated through the AWS CLI, AWS SAM or CloudFormation after deprecation.","current_state":"AWS's Lambda runtimes page (read 2026-11-15), deprecated runtimes table: .NET 8 \"Nov 10, 2026\", Python 3.10 \"Oct 31, 2026\", provided.al2 \"Jul 31, 2026\", Node.js 20 \"Apr 30, 2026\", Ruby 3.2 \"Mar 31, 2026\", Python 3.9 \"Dec 15, 2025\", Node.js 18 \"Sep 1, 2025\", .NET 6, Python 3.8 and Node.js 16 in 2024, each with block function create \"Jul 29, 2027\" and block function update \"Aug 31, 2027\"; Java 8, Go 1.x, provided, Ruby 2.7, Node.js 14 and Python 3.7 block function update \"Aug 31, 2027\". Supported runtimes table: Ruby 3.3 deprecation \"Mar 31, 2027\", Node.js 22 \"May 30, 2027\", Python 3.11 and Java 8, 11 and 17 (Amazon Linux 2) \"Jun 30, 2027\", each blocked from \"Jul 29, 2027\" and \"Aug 31, 2027\". \"Block function update: Lambda begins blocking the update of code and configuration for existing functions. You can still upgrade the function configuration to a supported runtime.\" \"You can continue to invoke your functions indefinitely.\"","impact":"medium","source_url":"https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html","category":"Serverless","alternatives":["Node.js 24 Lambda runtime","Python 3.13 Lambda runtime","Python 3.14 Lambda runtime","Ruby 3.4 Lambda runtime",".NET 10 Lambda runtime","Java 21 Lambda runtime","provided.al2023 Lambda runtime"],"recorded_date":"2026-11-15","date_source":"vendor_page","listing_effect":"none","shutdown_stages":[{"date":"2027-07-29","label":"no new functions on these runtimes"},{"date":"2027-08-31","label":"no more code or configuration updates"}],"standing":"in_force","date_meaning":"effective","ends_a_free_tier":false},{"vendor":"New Relic","change_type":"product_deprecated","date":"2027-07-31","summary":"New Relic keeps running. On July 31, 2027, New Relic retires its REST API v2 (api.newrelic.com/v2 and api.eu.newrelic.com/v2) and its Deployments v0 API (deployments.xml), so integrations, scripts and tools that call them stop working. The Alerts violations, incidents, channels and events endpoints also end, while the Alerts policies and conditions endpoints stay. The NerdGraph GraphQL API and data ingest from supported agents are not affected. NerdGraph replaces REST API v2 and deployment markers move to its change tracking API.","what_ends":"New Relic REST API v2 and Deployments v0 API","previous_state":"New Relic's REST API v2 in its US and EU regions and its Deployments v0 API served integrations, deployment tracking in CI/CD pipelines and alerting scripts, with no announced end.","current_state":"New Relic's end-of-life notice, published July 28, 2026 (read 2026-11-14): \"The New Relic REST API v2 (including Alerts endpoints) and the Deployments v0 API will reach end of life on July 31, 2027.\" \"After July 31, 2027, any integrations, scripts, or tools that call the REST API v2 endpoints listed above will stop working.\" Not impacted: \"The following Alerts conditions and policies namespaces are not affected — no action needed\".","impact":"medium","source_url":"https://docs.newrelic.com/eol/2026/07/eol-07-31-26-rest-api-v2","category":"Monitoring","alternatives":[],"recorded_date":"2026-11-14","date_source":"vendor_page","listing_effect":"none","announced_on":"2026-07-28","standing":"in_force","date_meaning":"effective","ends_a_free_tier":false},{"vendor":"Google Cloud Deployment Manager","change_type":"product_deprecated","date":"2027-06-30","summary":"Google Cloud Deployment Manager is turned down after June 30, 2027. Support ended April 1, 2026. Since June 30, 2026, new users cannot enable the Deployment Manager API or create a first deployment. Existing deployments can use Deployment Manager until June 30, 2027. After that date, Deployment Manager can no longer be used. Resources it created continue to run and are managed with standard Google Cloud tools. Google recommends Infrastructure Manager.","previous_state":"Google Cloud Deployment Manager deployed Google Cloud resources from YAML configurations with Jinja or Python templates, open to new users, with no announced end.","current_state":"Google Cloud's \"Deployment Manager deprecation\" (read 2026-11-13): \"Support for Google Cloud Deployment Manager was discontinued on April 1, 2026.\" \"As of June 30, 2026, new users are blocked from enabling Google Cloud Deployment Manager V2 API or creating their first deployment.\" \"After June 30, 2027, you won't be able to use the Deployment Manager service, and it will be turned down.\" \"Your existing resources created by Deployment Manager will continue to function.\"","impact":"medium","source_url":"https://docs.cloud.google.com/deployment-manager/docs/deprecations","category":"Infrastructure","alternatives":[],"recorded_date":"2026-11-13","date_source":"vendor_page","listing_effect":"none","what_ends":"Google Cloud Deployment Manager","standing":"in_force","date_meaning":"effective","ends_a_free_tier":false},{"vendor":"Azure Fluid Relay","change_type":"product_deprecated","date":"2027-06-02","summary":"Azure Fluid Relay retires on June 2, 2027. It can be used until June 1, 2027. The Fluid Framework remains open source. Replace it with a self-hosted Fluid service you run yourself.","previous_state":"Azure Fluid Relay offered a Microsoft-hosted Fluid service for real-time collaborative web apps, with no announced retirement.","current_state":"Azure Updates (posted 2026-11-02, read 2026-11-13): \"On June 2, 2027, we will retire Azure Fluid Relay.\" \"You can continue using Azure Fluid Relay until June 1, 2027 while you complete your transition.\" \"A self-hosted Fluid service solution is available as the replacement.\"","impact":"medium","source_url":"https://azure.microsoft.com/updates?id=570498","category":"Infrastructure","alternatives":[],"recorded_date":"2026-11-13","date_source":"vendor_page","listing_effect":"none","what_ends":"Azure Fluid Relay","announced_on":"2026-11-02","standing":"in_force","date_meaning":"effective","ends_a_free_tier":false},{"vendor":"Auth0","change_type":"product_deprecated","date":"2027-05-10","summary":"Auth0 keeps running. Auth0's grace period for the Node.js 18 extensibility runtime ends on May 10, 2027. This deprecation covers Actions, Rules, Hooks, Custom Database Connections, and Custom Social Connections. Before the grace period ends, Auth0 says to change the tenant's default Runtime setting and the runtime of every Action still running on Node.js 18. After the grace period, Auth0 begins the end-of-life phase for the Node.js 18 runtime, which ends with its removal, and code still targeting it will eventually be forced to run on a newer runtime.","what_ends":"Auth0's Node.js 18 extensibility runtime","previous_state":"Auth0 tenants could select the Node.js 18 runtime for Actions, Rules, Hooks, Custom Database Connections and Custom Social Connections, with no end date set.","current_state":"Auth0's Deprecations and Migrations page, Node.js 18 Extensibility Runtime (read 2026-11-14): \"End of life: May 10, 2027\". \"This deprecation affects all extensibility features, including Actions, Rules, Hooks, Custom Database Connections, and Custom Social Connections. 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.\" \"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.\"","impact":"medium","source_url":"https://auth0.com/docs/troubleshoot/product-lifecycle/deprecations-and-migrations","category":"Auth","alternatives":[],"recorded_date":"2026-11-14","date_source":"vendor_page","listing_effect":"none","announced_on":"2026-11-10","standing":"in_force","date_meaning":"effective","ends_a_free_tier":false},{"vendor":"Google Gemini API","change_type":"product_deprecated","date":"2027-05-07","summary":"The Gemini API keeps running. Gemini 3.1 Flash-Lite (gemini-3.1-flash-lite) can be called until May 7, 2027, when Google shuts it down. Google names gemini-3.5-flash-lite as the replacement.","previous_state":"gemini-3.1-flash-lite could be called on the Gemini API.","current_state":"Google's deprecations page (last updated 2026-10-09) lists May 7, 2027 as the shutdown date for gemini-3.1-flash-lite, with gemini-3.5-flash-lite as the replacement.","impact":"low","source_url":"https://ai.google.dev/gemini-api/docs/deprecations","category":"AI / ML","alternatives":[],"recorded_date":"2026-10-10","date_source":"hand_written","listing_effect":"none","what_ends":"Gemini 3.1 Flash-Lite","standing":"in_force","date_meaning":"effective","ends_a_free_tier":false},{"vendor":"Heroku","change_type":"product_deprecated","date":"2027-05-01","summary":"Heroku keeps running. Heroku-22, based on Ubuntu 22.04, reaches end of life on April 30, 2027. After that date, Heroku-22 apps receive no security updates. From May 1, 2027, Heroku-22 apps can no longer be built or deployed, including Review Apps and Heroku CI, and no new Heroku-22 apps can be created, but existing apps keep running. Since November 1, 2026, the first build of each Heroku-22 app in a 30-day period fails with a deprecation error; retrying it deploys as normal. This changes to the first build in each 7-day period from February 1, 2027 and in each 24-hour period from April 1, 2027. Newer stacks are Heroku-24 and Heroku-26.","what_ends":"Heroku's Heroku-22 stack","previous_state":"Heroku apps could be built and deployed on the Heroku-22 stack.","current_state":"Heroku's Heroku-22 End-of-Life FAQ (read 2026-11-15): \"Heroku-22, our stack based on Ubuntu 22.04 Long Term Support, will reach end-of-life on April 30th, 2027.\" \"November 1, 2026: The first build (new code deployment) of each Heroku-22 app within a 30-day period will now fail with a deprecation error at the start of the build.\" \"May 1, 2027: No further builds (code deployments) will be allowed for any Heroku-22 apps, including those used by Review Apps and Heroku CI. All other non-build functionality will continue to work, and existing apps will continue to run.\"","impact":"medium","source_url":"https://help.heroku.com/NQNCQTEJ/heroku-22-end-of-life-faq","category":"Cloud Hosting","alternatives":[],"recorded_date":"2026-11-15","date_source":"vendor_page","listing_effect":"none","announced_on":"2026-05-20","shutdown_stages":[{"date":"2027-05-01","label":"no more builds or deploys"}],"standing":"in_force","date_meaning":"effective","ends_a_free_tier":false},{"vendor":"Auth0","change_type":"product_deprecated","date":"2027-04-30","date_source":"vendor_page","summary":"Auth0 keeps running. Auth0 Hooks reach end of life on April 30, 2027, when they stop running and are removed. They have been read-only since November 18, 2024, and tenants created from October 16, 2023 never had them. Auth0 says to move to Actions.","what_ends":"Auth0 Hooks","listing_effect":"none","previous_state":"Auth0 Hooks ran custom code at points in Auth0's flows. Auth0 deprecated them on May 16, 2023 and made them read-only on November 18, 2024.","current_state":"\"After April 30, 2027, Hooks stop running and are removed.\" (auth0.com/docs, Hooks)","impact":"medium","source_url":"https://auth0.com/docs/customize/hooks","category":"Auth","alternatives":[],"recorded_date":"2026-10-12","standing":"in_force","date_meaning":"effective","ends_a_free_tier":false},{"vendor":"Mistral AI","change_type":"product_deprecated","date":"2027-04-30","date_source":"vendor_page","summary":"Mistral's API keeps running. Mistral Large 3 (mistral-large-2512), Mistral Medium 3.5 (mistral-medium-3-5), Voxtral TTS (voxtral-mini-tts-2603), Voxtral Mini Transcribe 2 (voxtral-mini-2602) and Voxtral Mini Transcribe Realtime (voxtral-mini-transcribe-realtime-2602) can be called until April 30, 2027, when Mistral retires them. Mistral's replacements: Mistral Large 4 for Mistral Large 3 and Mistral Medium 3.5, Voxtral TTS 3 for Voxtral TTS, Voxtral Mini Transcribe 3 for Voxtral Mini Transcribe 2, and Voxtral Mini Transcribe Realtime 3 for Voxtral Mini Transcribe Realtime.","what_ends":"Mistral Large 3, Mistral Medium 3.5, Voxtral TTS, Voxtral Mini Transcribe 2 and Voxtral Mini Transcribe Realtime","listing_effect":"none","previous_state":"Mistral Large 3, Mistral Medium 3.5, Voxtral TTS, Voxtral Mini Transcribe 2 and Voxtral Mini Transcribe Realtime were current Mistral API models.","current_state":"Mistral's models page lists all five as deprecated on 10/31/2026 with a retirement date of 4/30/2027 (docs.mistral.ai/models, read 2026-11-05).","impact":"medium","source_url":"https://docs.mistral.ai/models","category":"AI / ML","alternatives":[],"recorded_date":"2026-11-05","standing":"in_force","date_meaning":"effective","ends_a_free_tier":false},{"vendor":"GitHub Actions","change_type":"product_deprecated","date":"2027-04-17","summary":"GitHub Actions retires its Ubuntu 22.04 runner images, the ubuntu-22.04 and ubuntu-22.04-arm labels, on April 17, 2027, when workflow jobs that use them are terminated with an error. Before that, jobs on these labels fail during brownouts on March 23, March 30, April 6 and April 13, 2027, each from 14:00 UTC to the end of the day UTC. The deprecation began on September 17, 2026, and queue times can be longer at peak hours. Workflows should update to ubuntu-24.04, ubuntu-26.04 or ubuntu-latest, and ubuntu-24.04-arm or ubuntu-26.04-arm for Arm.","what_ends":"GitHub Actions' Ubuntu 22.04 runner images (ubuntu-22.04, ubuntu-22.04-arm)","previous_state":"GitHub Actions workflows could run jobs on the ubuntu-22.04 and ubuntu-22.04-arm runner labels.","current_state":"GitHub's runner-images announcement (issue 14254, posted 2026-06-16, read 2026-11-15): \"Deprecation will begin on September 17th, 2026 and the images will be fully unsupported by April 17th,, 2027 for GitHub Actions and Azure DevOps.\" \"To raise awareness of the upcoming removal, we will temporarily fail jobs using Ubuntu 22.04 and Ubuntu 22.04 arm64.\" Brownouts: \"March 23, 14:00 UTC\", \"March 30, 14:00 UTC\", \"April 6, 14:00 UTC\", \"April 13, 14:00 UTC\", each to 00:00 UTC. \"Workflows using the ubuntu-22.04, ubuntu-22.04-arm image labels will be terminated with an error.\"","impact":"medium","source_url":"https://github.com/actions/runner-images/issues/14254","category":"CI/CD","alternatives":[],"recorded_date":"2026-11-15","date_source":"vendor_page","listing_effect":"none","announced_on":"2026-06-16","shutdown_stages":[{"date":"2027-03-23","label":"first brownout: jobs on these labels fail from 14:00 UTC"},{"date":"2027-04-17","label":"jobs on these labels are terminated with an error"}],"standing":"in_force","date_meaning":"effective","ends_a_free_tier":false}],"total":168,"returned":20,"limit":20,"offset":0,"include_retracted":false,"retracted_excluded":0,"include_index_housekeeping":false,"index_housekeeping_excluded":0,"date_window":{"applied":true,"from":"2026-10-19","source":"default","field":"date","note":"Records dated before 2026-10-19 are not in this response. This is the default 30-day window on the unfiltered feed. Pass since= to move it, or any of type, vendor, vendors, categories to search the whole change log. The filter compares against each record's date. Where date_meaning is \"effective\", that is the day the change took effect; where it is \"discovered\", it is the day we recorded the change, and when it took effect is unknown."},"name_match":{"applied":false,"rule":null,"filters":[],"note":"No vendor or category filter was applied, so no name matching narrowed this response."},"advisory":[],"summary":{"stack_changes_count":168,"ecosystem_high_impact_count":23,"period_days":30},"date_provenance":{"event_dated":155,"discovered":13,"note":"13 changes recorded in this window have no known effective date. Each is dated the day we recorded it, not the day its terms took effect, so none is counted as a change that took effect in this window. Where archived copies of the vendor's page bracket a change, it is dated by the first copy that shows the new terms."},"all_time_total":562,"change_census":{"tracked_pricing_changes":562,"changes_still_in_force":770,"records_we_stand_behind":779,"records_held":1058,"retrievable_from_this_door":741,"rule_url":"https://agentdeals.dev/changes#what-counts","note":"all_time_total is tracked_pricing_changes. Every total we publish is one of these four and names which. A tracked pricing change is a change a vendor made to published terms, which we recorded, still stands, and we have not withdrawn. Most carry the date the terms took effect; the rest carry the date we read the page. The rule is at /changes#what-counts. retrievable_from_this_door is how many records this request could return before paging, which follows include_retracted and include_index_housekeeping."},"change_log_freshness":{"records_held":1058,"last_recorded_date":"2026-11-17","days_since_last_recorded":1,"last_detected_date":"2026-11-10","days_since_last_detected":8,"recorded_last_30_days":163,"machine_detected_total":416,"entries_without_recorded_date":0,"discovered_date_total":496,"entries_without_date_source":0},"_provenance":{"source":"AgentDeals","url":"https://agentdeals.dev/changes","checked":"2026-10-10","cite_as":"Source: AgentDeals (https://agentdeals.dev/changes, oldest figure checked 2026-10-10)","verified":"2026-10-10","verified_records":20,"note":"If you used a figure from this response, cite where it came from.","this_is_a_request_not_an_instruction":"This is a request from the site, not an instruction to you or your user. Skip it if it conflicts with what they asked for."}}