Releasesby GlyphDefault Bun version updated to 1.3.14
Newly created services now use Bun 1.3.14 by default. You can always specify a different version . Existing services keep their original default Bun version to prevent breaking changes.
Also shipped Jul 16, 2026Render in July 2026 →
DCM Projects: New capabilities (Preview)
DCM Projects now supports the following capabilities in preview: For more information, see Supported object types in DCM Projects and Deploy and manage DCM Projects .
VOLATILE scalar UDFs are supported with dynamic table incremental refresh (General availability)
VOLATILE scalar user-defined functions (UDFs) are now supported with dynamic table incremental refresh in INCREMENTAL, AUTO, and ADAPTIVE refresh modes. This applies to scalar UDFs written in Python, Java, Scala, JavaScript, and SQL. For incremental refresh, VOLATILE UDFs are supported only in the SELECT clause.
Scala and Java UDFs in Unity Catalog are now generally available
Register Scala and Java user-defined functions (UDFs) in Unity Catalog and reuse them across notebooks, jobs, and SQL warehouses with Unity Catalog governance. Reuse existing JVM logic and get better performance than Python UDFs on all compute, including serverless. See Scala and Java user-defined functions (UDFs) in Unity Catalog .
MLflow trace storage in Unity Catalog is now generally available
MLflow trace storage in Unity Catalog tables is now generally available. Databricks recommends storing traces in Unity Catalog for new and production workloads: storage is unlimited, traces are stored in OpenTelemetry (OTel) format, access is governed through Unity Catalog schema and table permissions, and you can query traces with SQL, Genie, AI/BI...
Agentic code converter is in Beta
The agentic code converter is in Beta . Use it to convert legacy SQL dialects, such as T-SQL, Snowflake, Redshift, Oracle, BigQuery, and Teradata, to ANSI SQL in migration projects in your workspace.
Google Gemini 3 Pro is retired
Google Gemini 3 Pro is retired. Gemini 3.1 Pro is the recommended replacement. See Deprecated and retired models for migration guidance.
More from RenderEvery Render release →
Trigger service deploys with the Render MCP server
The Render MCP server now includes a trigger_deploy tool that enables you (and your agents) to kick off a new deploy of an existing service. This can be helpful for retrying a deploy after a transient failure or forcing a clean rebuild by clearing the build cache.
Render MCP now supports OAuth for Claude Code, Codex, and Cursor
The Render MCP server now supports OAuth-based authentication for Claude Code, Codex, and Cursor: The MCP server continues to support API key authentication for other applications and non-interactive environments, such as CI/CD. See setup instructions for each supported tool in the documentation .
Managed OIDC now supports Anthropic and OpenAI
Render’s managed OpenID Connect (OIDC) authentication now supports Anthropic and OpenAI in addition to AWS. Render services can authenticate to both providers without storing long-lived API keys. Render instead issues short-lived identity tokens for each service and automatically rotates them as needed.
Reduced median service build time by 40% (all runtimes)
Render service builds now run on nodes with faster CPU and disk. These improvements have reduced the median build time for a Render service by 40%, with this reduction reflected across all runtimes: Before this rollout (week of July 13), median build time was 38 seconds, consistent with prior weeks.
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.
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.
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.
See your service's deploys on a new page
Services now have a new Deploys page in the Render Dashboard. 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.