Render changed its API changelog

===================================================================
--- before
+++ after
@@ -4,21 +4,41 @@
 
 CHANGELOG
 
 Tooling Releases
-Render CLIv2.24.0Python SDKv1.0.1TypeScript SDKv1.0.0
+Render CLIv2.25.0Python SDKv1.0.1TypeScript SDKv1.0.0
 Tooling Releases
 Render CLI
-v2.24.0
-Aug 19, 2026
+v2.25.0
+Aug 27, 2026
 Python SDKBeta
 v1.0.1
 Aug 21, 2026
 TypeScript SDKBeta
 v1.0.0
 Aug 21, 2026
 Filters
 
+August 26, 2026
+New
+
+NEW COMPUTE PLANS, AND NEW IDS FOR EXISTING PLANS
+
+We're introducing new compute plans for Render services, including memory-optimized plans with higher ratios of RAM to CPU and a new 12-CPU tier for web services, private services, and background workers.
+
+To support the expanded catalog, we're also changing compute plan IDs to a spec-based format that includes the relevant specs. For example a web service compute plan with 4 CPU and 32GB RAM now carries the ID 4c-32g. This convention allows you to more easily intuit the specs of compute plans as we add additional options.
+
+No action is needed to continue using your current compute plan(s). While you will see the IDs for plans change in the Render Dashboard and documentation, you can continue to use old plan IDs with the Render API, SDK, CLI, and Blueprints. To avoid any issues when you start using the new plan IDs, we recommend updating to the latest versions of Render clients and integrations, including the CLI and Terraform provider.
+
+You can see the mapping of old plan names to new plan IDs in the Render Dashboard.
+
+What’s new:
+
+ * Increase memory without increasing CPU. At each 2+ CPU tier (2 CPU, 4 CPU, 8 CPU, etc.) we are adding multiple plans with more RAM. For example, at 2 CPU you can now choose between web service plans with 4 GB, 8GB, and 16 GB RAM.
+ * 12-CPU plans for heavy workloads. For customers running agent platforms or other heavy workloads, we are adding a set of 12-CPU plans with up to 96GB RAM.
+ * New compute plan IDs. To keep plan IDs intuitive as we add more options, we are replacing legacy IDs (Pro Plus, Pro Ultra, etc) with simple spec-based IDs. For example, the 2 CPU 4 GB web service plan now has an ID of 2c-4g. The Render API, CLI, SDK, and Blueprints will remain backward compatible with legacy plan IDs. No action is required.
+ * "Compute plan" replaces "instance type" across the dashboard, API, CLI, and docs.
+
 August 07, 2026
 Improved
 
 REDUCED MEDIAN SERVICE BUILD TIME BY 40% (ALL RUNTIMES)
@@ -153,21 +173,8 @@
 Improved
 
 REDUCED MEDIAN DOCKER SERVICE BUILD TIME BY 60%
 
-In recent weeks, we've gradually rolled out a number of optimizations for Dockerfile-based service builds on Render. These optimizations include:
-
- * Tuning chunk size and parallelism for build image uploads
- * Speeding up build scheduling on Render infrastructure
- * Parallelizing generated image upload with export to build cache
- * Storing build cache in Render's own image registry with automatic pruning
-
-Together, these optimizations have reduced median build time for Docker-based services by 60%:
-
-Median Docker build times by week [https://cdn.sanity.io/images/hvk0tap5/production/d022dea58aa0e66b7fa95577416680bc8d45eb73-1862x1006.png?w=1800&fm=webp]Median Docker build times by week
-
-Before these optimizations (week of March 15), median build time was 87 seconds, consistent with prior weeks. After all optimizations landed, the highest weekly median observed has been 32 seconds (a conservative 60% reduction). Build times remain in this range.
-
 June 05, 2026
 Early Access
 
 AUTHENTICATE RENDER SERVICES WITH AWS USING OIDC