Render changed its API changelog

===================================================================
--- before
+++ after
@@ -4,21 +4,81 @@
 
 CHANGELOG
 
 Tooling Releases
-Render CLIv2.25.0Python SDKv1.0.1TypeScript SDKv1.0.0
+Render CLIv2.26.0Python SDKv1.0.1TypeScript SDKv1.0.0
 Tooling Releases
 Render CLI
-v2.25.0
-Aug 27, 2026
+v2.26.0
+Sep 01, 2026
 Python SDKBeta
 v1.0.1
 Aug 21, 2026
 TypeScript SDKBeta
 v1.0.0
 Aug 21, 2026
 Filters
 
+September 03, 2026
+Improved
+
+SEE YOUR SERVICE'S DEPLOYS ON A NEW PAGE
+
+Services now have a new Deploys page in the Render Dashboard.
+
+The Deploys page shows a service's deploy history, live version, and roll-out status. [https://cdn.sanity.io/images/hvk0tap5/production/3199f6d4c0803a2d325fff21a2261e290e227866-1898x1314.png?w=1800&fm=webp]The Deploys page shows a service's deploy history, live version, and roll-out status.
+
+The Deploys page features:
+
+ * Your service's deploy history, without a date cutoff.
+ * A Live badge indicating the current deploy.
+ * Status of in-progress deploys.
+ * A banner flagging when auto-deploys are disabled.
+
+Previously, deploys were only visible on the Events page, interspersed with other events, and capped at a 90-day history. The Events page continues to show all service events, including deploys.
+
+Cron jobs also have new Builds and Runs pages that separate build and run history.
+
+Cron job navigation for the new Builds and Runs pages [https://cdn.sanity.io/images/hvk0tap5/production/9d773371336cbced2ba3cd984cb04c83fcc297a6-706x376.png?w=1800&fm=webp]Cron job navigation for the new Builds and Runs pages
+
+Learn more in the documentation.
+
+September 01, 2026
+New
+
+INTRODUCED THE FLEX COMPUTE PLAN FOR RENDER WORKFLOWS
+
+Render Workflows uses a new default compute plan for task runs: flex.
+
+The flex compute plan provides up to 1 CPU and 4 GB of RAM. Task runs on flex are billed only for the CPU and RAM they actually use, resulting in significantly lower costs for computationally inexpensive runs.
+
+The flex compute plan replaces the starter and standard compute plans for Render Workflows. Tasks that previously used starter or standard now automatically use flex instead.
+
+For tasks with higher resource requirements, you can assign a different compute plan in your task's definition:
+
+Learn more about compute plans for Render Workflows in the documentation.
+
+September 01, 2026
+New
+
+ADDED USAGE TELEMETRY TO THE RENDER CLI
+
+The Render CLI now automatically collects usage telemetry to help us understand common use cases and improve user experience. Telemetry is enabled by default in version 2.26.0 or later.
+
+Telemetry includes the following:
+
+ * Commands run (e.g., render services list)
+ * Command performance and completion status
+ * CLI version
+ * System information
+ * Execution context
+
+The Render CLI does not collect sensitive user data, such as command arguments, environment variable values, passwords, or the contents of your files.
+
+You can disable telemetry at any time by setting either the RENDER_CLI_DISABLE_ANALYTICS or DO_NOT_TRACK environment variables. For example:
+
+Learn more in the documentation.
+
 August 26, 2026
 New
 
 NEW COMPUTE PLANS, AND NEW IDS FOR EXISTING PLANS
@@ -112,64 +172,18 @@
 New
 
 ADD CONNECTION POOLING TO YOUR RENDER POSTGRES DATABASE
 
-Paid Render Postgres databases now support connection pooling using PgBouncer at no additional cost. Enable connection pooling if your database needs to handle more concurrent client connections than its instance type allows:
-
-Render runs PgBouncer on the same underlying host as your database to minimize the latency introduced by the additional hop.
-
-Enable connection pooling from your database's Info page in the Render Dashboard:
-
-Enabling connection pooling in the Render Dashboard [https://cdn.sanity.io/images/hvk0tap5/production/e3ad1dc154d9917a60e2020aba8bd965575a586b-1072x548.png?w=1800&fm=webp]Enabling connection pooling in the Render Dashboard
-
-You can also enable connection pooling using Blueprints or the Render API.
-
-Enabling connection pooling requires a database restart. After the restart, update your clients to use your database's new connection pool URL (port 6432) instead of its direct connection URL (port 5432).
-
-Learn more in the documentation.
-
 June 30, 2026
 New
 
 MANAGE POSTGRES AND KEY VALUE INSTANCES USING THE RENDER CLI
 
-You (and your agents) can now create, update, delete, suspend, and resume Render Postgres and Key Value instances using version 2.21.0 or later of the Render CLI.
-
-Use render kv commands to manage Key Value instances:
-
-Use render pg commands to manage Postgres databases:
-
-Run render kv --help or render pg --help for a list of supported commands, or see the full generated command reference.
-
-With these additions, the Render CLI now provides management capabilities for every Render service type.
-
-Get started with the Render CLI in the docs.
-
 June 11, 2026
 New
 
 SPECIFY DISK PERSISTENCE BEHAVIOR FOR PAID KEY VALUE INSTANCES
 
-Paid Render Key Value instances now support three different disk persistence modes:
-
- * Journal + Snapshot: Append writes to a journal and periodically save full snapshots.
-   * This matches the behavior of all paid Key Value instances before this release.
- * Snapshot only: Disable journaling while continuing to save periodic snapshots.
- * Off: Disable all disk-backed persistence.
-
-Reducing persistence can improve write performance for loss-tolerant use cases, such as a shared cache.
-
-You specify your instance's persistence mode on creation:
-
-Selecting a persistence mode during Key Value creation [https://cdn.sanity.io/images/hvk0tap5/production/665c1eccbd1438c410f517ca1bd62f78246786d5-1548x350.png?w=1800&fm=webp]Selecting a persistence mode during Key Value creation
-
-You can change your instance's persistence mode in the Render Dashboard or using the Render API. Note the following:
-
- * Changing your persistence mode requires a restart, during which your Key Value instance is unavailable for a few seconds.
- * If you change your mode to or from Off, all data in your instance is lost after the restart.
-
-Learn more about Key Value persistence modes in the documentation.
-
 June 11, 2026
 Improved
 
 REDUCED MEDIAN DOCKER SERVICE BUILD TIME BY 60%
@@ -938,19 +952,17 @@
 MARCH 31, 2023 - CHANGELOG
 
 Load More
 
-shellCopy to clipboard
-$ render kv create \
-    --name jobs-cache-staging \
-    --region oregon \
-    --plan starter \
-    --memory-policy queue \
-    --confirm
+typescriptCopy to clipboard
+const myTask = task(
+  {
+    name: 'myTask',
+    plan: '2c-4g' 
+  },
+  function myTask(ctx: TaskContext, a: number): number {
+    return a * a
+  }
+)
 
 shellCopy to clipboard
-$ render pg create \
-    --name app-db-staging \
-    --region oregon \
-    --plan basic_256mb \
-    --version 17 \
-    --confirm
\ No newline at end of file
+$ export DO_NOT_TRACK=1
\ No newline at end of file