On November 18, 2026 , Render will begin supporting separate service previews and preview environments for each pull request in a GitHub PR stack: Currently, Render creates previews only for PRs that directly target your service's linked branch. This means that only the bottom PR in a stack can generate previews.
New services on Render now default to Node.js 24.22.1 and Bun 1.4.4.
Render now supports canary builds for Bun. Canary builds let you preview upcoming Bun features before they reach a stable release. To use canary builds, do one of the following: Set your service's BUN_VERSION environment variable to canary . Add a .bun-version file to the root of your repo with the single line: canary .
Render now supports two additional compute plans for Key Value instances: 3 GB RAM with up to 3,000 simultaneous connections 50 GB RAM with up to 50,000 simultaneous connections We've also reduced pricing for existing Key Value compute plans that provide at least 1 GB RAM.
You can now manage your workflow services using Blueprints , Render's infrastructure-as-code model. Define workflows alongside other service types in your Blueprint YAML.
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.
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.
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.
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.
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.
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 .
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.
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.
| Release-notes page | Site | Feed |
|---|---|---|
| Added Blueprint support for Render Workflows render.com | render.com | None |
| Automatic Go version updates render.com | render.com | None |
| Changelog render.com | render.com | None |
Releasesby Glyph