Releasesby GlyphManaged 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.
Also shipped Jul 24, 2026Render in July 2026 →
Skill and plugin sharing in CoCo (Public Preview)
Skill and plugin sharing is now available in public preview. Share, discover, and govern CoCo skills and plugins across your Snowflake account. Publish them as Cortex Extension objects that teammates can find and install, with administrator certification, access control, and usage telemetry. For more information, see Share skills and plugins .
Governed tags system table is in Beta
The system.tags.governed_tags system table is in Beta . This table contains a record for each governed tag key in your account, including customer-created and system-generated tags. Use it to programmatically determine which tags in your account are governed. See Governed tags system table reference .
Git CLI commands in Git folders are now in Public Preview
Git CLI commands in Git folders are now in Public Preview . Git folders that you create from the UI automatically get Git CLI access when your workspace is eligible, so you can run standard Git commands such as git stash , interactive rebase, pre-commit hooks, Git submodules, and Large File Storage (LFS) directly from a Databricks terminal.
Diagnose and fix Lakebase issues with Genie, using telemetry in Unity Catalog (Beta)
Lakebase adds AI-assisted troubleshooting: database issues and early warnings are surfaced to you with Insights , and you can then investigate and fix them conversationally with Genie . Both draw on database telemetry captured to Unity Catalog. See Observability .
Knowledge Catalog governance workflows for data product access in preview
Governance workflows add automated controls for data product access management through a request-review mechanism.
Claude Opus 5 launches with a 1M token context window at $5 / $25 per MTok
Claude Opus 5 improves on Opus 4.8 with a 1M token context window, 128k max output and thinking on by default, at the same $5 / $25 per MTok price. It is available on the Claude API, Bedrock, Google Cloud and Microsoft Foundry.
More from RenderEvery Render release →
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 .
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.
Default 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.
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.