NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules · #1139 by repository stars
Last release today
02 Oct 2026
Ships on a steady schedule
a new release about every 8 days
Nearly every release is documented
notes for 48 of 52 stable releases
Nothing withdrawn
no release was ever pulled
3 years old
1387 releases · first in 2023
One column per quarter.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
This change is due to Bitnami's deprecation of their public container registry, which affects the availability of Contour images.
Today we're happy to announce the release of Radius v0.51.0. Check out the highlights below, along with the full changelog for more details.
We would like to extend our thanks to all the contributors who helped make this release possible!
If you're new to Radius, check out our website, radapp.io, for more information. Also visit our getting started guide to learn how to install Radius and create your first app.
The existing --purge flag for rad uninstall kubernetes has been updated. When this flag is now specified in the command, all Kubernetes resources created by Radius, including resources created as a part of application deployments, will be deleted. For more information, please refer to the CLI documentation.
The rad app delete command has been updated to show deletion progress and confirmation summary in the console output. This fix addresses a usability concern where app deletion operations that take a bit more time make it look like the CLI is frozen. For more information, please refer to the CLI documentation
Previously, when deploying ACI resources, Radius used a hardcoded WestUS3 location as that was one of the first locations to have the ACI NGroups feature available. This has been fixed where the resource group's location is now dynamically retrieved and used throughout the ACI Environment creation and resource deployment process. See the how-to guide for more information on deploying to ACI using Radius.
Radius no longer automatically installs the Contour ingress controller during rad install kubernetes or rad init. This change is due to Bitnami's deprecation of their public container registry, which affects the availability of Contour images.
Applications that rely on Radius Gateway resources for ingress functionality will need to manually install and configure a Contour ingress controller before deploying Gateway resources. For more information on how to install Contour, please consult the Contour documentation. Note that Contour may not have updated their documentation yet given the recency of this issue, so we'd also recommend consulting their community discussion on this matter.
This change is temporary while we evaluate alternative ingress controller options and repository sources.
You can upgrade to this release by upgrading your Radius CLI then running rad upgrade kubernetes. Only incremental version upgrades are supported. Consult the upgrade documentation for full details.
5f3c0eb to 13f0f47 by @dependabot[bot] in https://github.com/radius-project/radius/pull/10217rad uninstall kubernetes --purge to add cleanup by @willdavsmith in https://github.com/radius-project/radius/pull/10427Full Changelog: https://github.com/radius-project/radius/compare/v0.50.0...v0.51.0
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Today we're happy to announce the release of Radius v0.50.0. Check out the highlights below, along with the full changelog for more details.
Today we're happy to announce the release of Radius v0.50.0. Check out the highlights below, along with the full changelog for more details.
We would like to extend our thanks to all the contributors who helped make this release possible!
If you're new to Radius, check out our website, radapp.io, for more information. Also visit our getting started guide to learn how to install Radius and create your first app.
Radius can now be upgraded using the new rad upgrade command. The new command upgrades the Radius control plane while preserving existing environments and applications. There is also a rad rollback command. Read more in the Radius documentation.
Properties on Radius resource types can now be arrays of objects. You can also now specify an enum type to validate inputs prior to deployment.
The YAML file schema for resource type definitions changed. name is now namespace. For example, when you use rad resource-type create -f types.yaml to create a new resource type, the types.yaml file must have namespace: Radius.Resources rather than name: Radius.Resources on line one.
Radius can now be installed in an offline environment using the rad install command or via the Helm chart by setting location of the Radius containers via the global.imageRegistry and global.imageTag parameters.
The name property in resource type definition YAML file is now namespace. See the Radius resource type section above for details.
You can upgrade to this release by upgrading your Radius CLI then running rad upgrade kubernetes. Only incremental version upgrades are supported. Consult the upgrade documentation for full details.
status in UDT postgres test by @lakshmimsft in https://github.com/radius-project/radius/pull/100721d0af45 to 5f3c0eb by @dependabot[bot] in https://github.com/radius-project/radius/pull/10163pre-upgrade container for Radius preflight checks by @willdavsmith in https://github.com/radius-project/radius/pull/9898Full Changelog: https://github.com/radius-project/radius/compare/v0.49.0...v0.50.0
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
The capabilities: ["SupportsRecipes"] property is deprecated and the Recipe support is enabled by default.
Today we're happy to announce the release of Radius v0.49.0. Check out the highlights below, along with the full changelog for more details.
We would like to extend our thanks to all the contributors who helped make this release possible!
If you're new to Radius, check out our website, radapp.io, for more information. Also visit our getting started guide to learn how to install Radius and create your first app.
Connection support between RRT->RRT is now available. For example, when connecting a Radius.Resources/webServices resource to a Radius.Resources/postgreSQL resource, the PostgreSQL properties are now included in the Recipe's context object. This makes it easier for platform engineers to reference these properties for creating secrets in Recipes.
rad resource-type createThe [rad resource-type create] (https://docs.radapp.io/reference/cli/rad_resource-type_create/) command now supports creating all specified resource types in the yaml definition at once.
RRTs now support multiple API versions. You can now version your custom resource types with the current date of your choice 2025-07-18-preview following the required format YYYY-MM-DD-preview
The capabilities: ["SupportsRecipes"] property is deprecated and the Recipe support is enabled by default.
Introduced capabilities: ["manualResourceProvisioning"] to support externally provisioned resources. This lets developers connect to resources outside of Radius, while platform engineers expose them via RRTs without needing Recipes.
You now have full control over Contour during Kubernetes installation with rad install kubernetes:
Use --contour-disabled to skip installing the Contour ingress controller.
Use --contour-chart to install from a custom Helm chart. More information [here]https://docs.radapp.io/reference/cli/rad_install_kubernetes/)
None
During our preview stage, an upgrade to Radius v0.49.0 requires a full reinstallation of the Radius control-plane, rad CLI, and all Radius apps. Stay tuned for an in-place upgrade path in the future.
rad env delete <env-name>
rad uninstall kubernetes
rad install kubernetes
<!-- Release notes generated using configuration in .github/release.yml at main -->
f8a4177 to 7629785 by @dependabot[bot] in https://github.com/radius-project/radius/pull/98467629785 to 1d0af45 by @dependabot[bot] in https://github.com/radius-project/radius/pull/9884Full Changelog: https://github.com/radius-project/radius/compare/v0.48.0...v0.49.0
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →