---
name: Render Changelog
slug: render-changelog
type: feed
source_url: https://render.com/changelog
organization: Render
organization_slug: render
total_releases: 12
latest_date: 2026-04-16
last_updated: 2026-04-19
tracking_since: 2025-12-17
canonical: https://releases.sh/render/render-changelog
organization_url: https://releases.sh/render
---
Render shipped Workflows, a durable task orchestration system now in public beta with TypeScript and Python SDKs for building long-running background processes—handling queuing, retries, state management, and parallel execution on Render's private network. Beyond that, the platform expanded Blueprint flexibility by supporting custom file paths and added validation via CLI and API, while the CLI itself gained workspace listing and non-interactive database querying. Audit logs now capture session closures and connection metadata (source IP, user agent), and free web services extended their spindown logic to respect active WebSocket traffic alongside HTTP requests.
Audit logs gained visibility into shell session lifecycles and client context. The `EndShellEvent` type now complements existing `StartShellEvent` tracking, while new `source_ip` and `user_agent` metadata fields let you see where shell access originated.
## Create new services from the Render CLI
You (and your agents) can now create new services directly from the terminal using the [Render CLI's](https://render.com/docs/cli) `services create` command:
```
render services create \
--name hello-world \
--type web_service \
--runtime node \
--region virginia \
--plan free \
--repo https://github.com/render-examples/express-hello-world \
--branch main \
--build-command "yarn" \
--start-command "node app.js" \
--output json
```
As shown, you provide your service's initial configuration (service type, runtime, region, etc.) as individual options to this command.
For all supported options, run `render help services create` or see the generated [command reference](https://render.com/docs/cli-reference#services-create).
Get started with the Render CLI in the [docs.](https://render.com/docs/cli)
## Automatic Go version updates
Render's native Go environment now automatically updates to the latest stable Go 1.x version, usually within 24 hours of a new release. After an update, your service starts using the new version with its next deploy.
Previously, we handled Go version updates manually, which meant delays between a new Go release and availability on Render. This is now fully automated.
If you need to pin to a specific Go version, you can deploy using a Docker image. Learn more about [supported languages and versions](https://render.com/docs/language-support) in the docs.
## Render Workflows now in public beta
[Render Workflows](https://render.com/workflows) is now in public beta, with SDK support for TypeScript and Python. Define durable tasks and chain them into long-running background processes for agent logic, data pipelines, billing flows, and more.
Deploy your task definitions as a Workflow service, trigger runs from your app (or via API/Dashboard), and let Render handle queuing, retries, state management, and parallel execution. Workflows run on Render’s private network with unified logs and metrics so you can debug runs in one place.
Explore examples in the [Workflows Playground](https://render.com/workflows/playground?example=hello-world&lang=typescript) or get started with `render workflows init` in the Render CLI. Learn more in the [announcement post](https://render.com/blog/durability-as-code-introducing-render-workflows) and [documentation](https://render.com/docs/workflows).
## Audit log updates: Added the EndShellEvent type, plus metadata for source IP and user agent
Workspace audit logs now include the `EndShellEvent` event type, which indicates that a workspace member closed an active [dashboard shell or SSH](https://render.com/docs/ssh) session to a Render service. Audit logs already included `StartShellEvent`, which is logged when a shell session starts.
Audit log events also now include `source_ip` and `user_agent` properties in their metadata field whenever these values are available:
```
{
"source_ip": "192.0.2.0",
"user_agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7)…",
}
```
Learn more about audit logs in the [docs](https://render.com/docs/audit-logs).
## Free web services now remain active while receiving WebSocket messages
Free web services now spin down after going 15 minutes without receiving *either* of the following:
- An incoming HTTP request
- An incoming WebSocket message from an existing connection
Previously, only incoming HTTP requests delayed spindown. This meant that a service could spin down even while actively receiving WebSocket traffic.
Learn more about free web services in the [docs](https://render.com/docs/free#free-web-services).
## Updated version defaults: Python to 3.14.3, uv to 0.10.2
Newly created Python services now use Python 3.14.3 and uv version 0.10.2 by default. You can always specify a different version of both [Python](https://docs.render.com/python-version) and [uv](https://render.com/docs/uv-version).
*Existing* Python services keep their original default versions to prevent breaking changes.
## Render CLI v2.8.0
**New command:** `render workspaces`
By default, `render workspaces` lists your available workspaces in an interactive menu. Optionally, you can also list workspaces in plaintext, JSON, or YAML format. For example, the following command lists workspaces in YAML:
```
render workspaces -o yaml
```
---
**Non-interactive mode for `render psql`**
You can now pass queries directly through `render psql` and print the response in plaintext, JSON, or YAML. For example:
```
render psql my-database -c "SELECT id, name FROM projects LIMIT 5;" -o json
```
---
**Show latest available version**
The `render --version` command now informs you if a new version of the Render CLI is available.
---
For more details, see the release on [GitHub](https://github.com/render-oss/cli/releases/tag/v2.8.0). Get started with the Render CLI in the [docs](https://render.com/docs/cli).
## Blueprints now support custom filenames and paths
Blueprints (Render's [infrastructure-as-code model](https://render.com/docs/infrastructure-as-code)) now support custom filenames and paths for YAML configuration files. Previously, Blueprints required a file named `render.yaml` in your repository's root directory.
You can specify a custom path when creating a new Blueprint in the [Render Dashboard](https://dashboard.render.com/):
You can also update an existing Blueprint's file path from its **Settings** page.
If you don't set a custom path, Render defaults to using `render.yaml` in your repository root. Learn more in the [documentation](https://render.com/docs/infrastructure-as-code#setup).
## Service events no longer erroneously report scaling down to zero instances
In rare cases, Render would erroneously emit an **Autoscaler starting to scale down to 0 instances** event for services with autoscaling enabled. These events were triggered by momentary latency in scaling metrics, and they did *not* modify the instance count of the affected service.
This behavior is now resolved.
## Validate Blueprint files using the Render CLI or API
The Render CLI and API now support validation of `render.yaml` files used with [Render Blueprints](https://render.com/docs/infrastructure-as-code). This enables you to quickly verify that Blueprint changes are valid in your local dev environment or as part of CI.
- **CLI:** Run `render blueprints validate render.yaml`
Requires version 2.7.1 or later of the CLI. Learn how to [upgrade](https://render.com/docs/cli#1-install-or-upgrade).
- **API:** Provide your `render.yaml` file to the new [Validate Blueprint](https://api-docs.render.com/reference/validate-blueprint) endpoint.
New to the Render API? [Start here.](https://render.com/docs/api)
These additions complement existing IDE support for Blueprint validation. Learn more in the [documentation](https://render.com/docs/blueprint-spec#validating-blueprints).
## Default Node.js version updated to 22.22.0
Newly created Node.js services now use Node.js 22.22.0 by default. You can always [specify a different version](https://render.com/docs/node-version).
*Existing* Node.js services keep their original default version to prevent breaking changes.
## Improved logs UX in the Render dashboard and CLI
We've made several improvements to the Render dashboard to make logs easier to consume:
- Expanded logs container to view more log lines at once
- Click individual log lines to open a detail view
- Toggle live tail mode
- Light and dark mode support to match your selected dashboard theme
Additionally, the `render logs` CLI command now supports paginated infinite scroll, making it easier to navigate extensive log histories.
Learn more about using the [Render logs UI](https://render.com/docs/logging) and the [Render CLI](https://render.com/docs/cli).