NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules
Go modules, #1179 by repository stars
Latest stable
v0.62.0
Last release 15 days ago
07 Nov 2026
Ships on a steady schedule
a new release about every 8 days
Nearly every release is documented
notes for 50 of 53 stable releases
Nothing withdrawn
no release was ever pulled
3 years old
1621 releases · first in 2023
Drag across the ruler to compare, or tap a release to open it.
Clarify bug and private vulnerability reporting by @vinayada1 in #13404
Today we're happy to announce the release of Radius v0.62.0. Check out the highlights below, along with the full changelog for more details.
We would like to extend our thanks to all the new and existing 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.
rad env, rad app, rad init, rad workspace create, and rad resource list now target the Radius.Core resource model without the --preview flag. The legacy rad recipe register/unregister/list/show commands are removed. Update any scripts that pass --preview or use those commands.
The Helm chart now pins Radius component images to the full release version. Restarting pods no longer picks up later patches implicitly. Upgrade the chart to receive patched images. See Upgrading for override behavior.
Radius now embeds a pinned Kubernetes Recipe Pack from the /resource-types-contrib repo and builds the default recipe pack from it, so new environments get a working set of Recipes out of the box. See the Kubernetes Recipe Pack in the repo for more details.
Radius can now store Terraform recipe state in your own S3 bucket or Azure Blob Storage container instead of only in Kubernetes secrets. Learn more in the Terraform state docs.
Many retry and robustness fixes make the CLI and deployments more resilient to transient failures. They cover Bicep recipe downloads, Terraform provider discovery, API server reads, and managed secret deletion. Azure resource deletion now selects supported API versions and deletes in dependency order. Radius type version skew warns before deployment. Digest-pinned Bicep recipe sources are supported.
Welcome to our new contributors who have merged their first PR in this release!
Helm image pinning: This release's Helm chart pins Radius component images to the full release version. Restarting pods no longer picks up later patches implicitly; upgrade the chart to receive patched images. Existing channel aliases remain available, and explicitly configured global.imageTag, component tags, or image references keep overriding chart defaults. To adopt version-pinned defaults while retaining other settings, clear tag overrides and restore image overrides to their default names; an empty image value is invalid.
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.
0.62.0 - 2026-10-27
rad auth command details by @willtsai in #13235Note truncated.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Today we're happy to announce the release of Radius v0.62.0-rc.6. Check out the highlights below, along with the full changelog for more details.
Today we're happy to announce the release of Radius v0.62.0-rc.6. Check out the highlights below, along with the full changelog for more details.
We would like to extend our thanks to all the new and existing 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.
None.
Welcome to our new contributors who have merged their first PR in this release!
None.
Helm image pinning: This release's Helm chart pins Radius component images to the full release version. Restarting pods no longer picks up later patches implicitly; upgrade the chart to receive patched images. Existing channel aliases remain available, and explicitly configured global.imageTag, component tags, or image references keep overriding chart defaults. To adopt version-pinned defaults while retaining other settings, clear tag overrides and restore image overrides to their default names; an empty image value is invalid.
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.
0.62.0-rc.6 - 2026-10-27
Changes since v0.62.0-rc.5. See that release for earlier changes.
@AzureMike, @DariuszPorowski, @brooke-hamilton, @kachawla
The changelog is based on Keep a Changelog 1.1.0, with Radius-specific change groups and contributor sections. Radius follows Semantic Versioning under its version policy.
Today we're happy to announce the release of Radius v0.62.0-rc.5. Check out the highlights below, along with the full changelog for more details.
Today we're happy to announce the release of Radius v0.62.0-rc.5. Check out the highlights below, along with the full changelog for more details.
We would like to extend our thanks to all the new and existing 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.
None.
Welcome to our new contributors who have merged their first PR in this release!
None.
Helm image pinning: This release's Helm chart pins Radius component images to the full release version. Restarting pods no longer picks up later patches implicitly; upgrade the chart to receive patched images. Existing channel aliases remain available, and explicitly configured global.imageTag, component tags, or image references keep overriding chart defaults. To adopt version-pinned defaults while retaining other settings, clear tag overrides and restore image overrides to their default names; an empty image value is invalid.
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.
0.62.0-rc.5 - 2026-10-27
Changes since v0.62.0-rc.4. See that release for earlier changes.
The changelog is based on Keep a Changelog 1.1.0, with Radius-specific change groups and contributor sections. Radius follows Semantic Versioning under its version policy.
Today we're happy to announce the release of Radius v0.62.0-rc.4. Check out the highlights below, along with the full changelog for more details.
Today we're happy to announce the release of Radius v0.62.0-rc.4. Check out the highlights below, along with the full changelog for more details.
We would like to extend our thanks to all the new and existing 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.
Welcome to our new contributors who have merged their first PR in this release!
None.
Helm image pinning: This release's Helm chart pins Radius component images to the full release version. Restarting pods no longer picks up later patches implicitly; upgrade the chart to receive patched images. Existing channel aliases remain available, and explicitly configured global.imageTag, component tags, or image references keep overriding chart defaults. To adopt version-pinned defaults while retaining other settings, clear tag overrides and restore image overrides to their default names; an empty image value is invalid.
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.
0.62.0-rc.4 - 2026-10-26
Changes since v0.62.0-rc.3. See that release for earlier changes.
@kachawla, @nicolejms, @willdavsmith, @Reshrahim, @Copilot
The changelog is based on Keep a Changelog 1.1.0, with Radius-specific change groups and contributor sections. Radius follows Semantic Versioning under its version policy.
Today we're happy to announce the release of Radius v0.62.0-rc.3. Check out the highlights below, along with the full changelog for more details.
Today we're happy to announce the release of Radius v0.62.0-rc.3. Check out the highlights below, along with the full changelog for more details.
We would like to extend our thanks to all the new and existing 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.
None.
Welcome to our new contributors who have merged their first PR in this release!
None.
Helm image pinning: This release's Helm chart pins Radius component images to the full release version. Restarting pods no longer picks up later patches implicitly; upgrade the chart to receive patched images. Existing channel aliases remain available, and explicitly configured global.imageTag, component tags, or image references keep overriding chart defaults. To adopt version-pinned defaults while retaining other settings, clear tag overrides and restore image overrides to their default names; an empty image value is invalid.
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.
0.62.0-rc.3 - 2026-10-23
Changes since v0.62.0-rc.2. See that release for earlier changes.
@radius-dependabot-manager[bot], @DariuszPorowski
The changelog is based on Keep a Changelog 1.1.0, with Radius-specific change groups and contributor sections. Radius follows Semantic Versioning under its version policy.
Today we're happy to announce the release of Radius v0.62.0-rc.2. Check out the highlights below, along with the full changelog for more details.
Today we're happy to announce the release of Radius v0.62.0-rc.2. Check out the highlights below, along with the full changelog for more details.
We would like to extend our thanks to all the new and existing 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.
Welcome to our new contributors who have merged their first PR in this release!
Helm image pinning: This release's Helm chart pins Radius component images to the full release version. Restarting pods no longer picks up later patches implicitly; upgrade the chart to receive patched images. Existing channel aliases remain available, and explicitly configured global.imageTag, component tags, or image references keep overriding chart defaults. To adopt version-pinned defaults while retaining other settings, clear tag overrides and restore image overrides to their default names; an empty image value is invalid.
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.
0.62.0-rc.2 - 2026-10-23
@DariuszPorowski, @kachawla, @radius-release[bot], @radius-files-sync[bot], @vinayada1, @nicolejms, @radius-dependabot-manager[bot], @Copilot, @dependabot[bot], @radius-resource-types[bot], @sk593, @AzureMike, @lakshmimsft, @itpropro, @brooke-hamilton, @allexistence, @willdavsmith, @willtsai, @nithyatsu, @Reshrahim, @pujitha24, @zachcasper
The changelog is based on Keep a Changelog 1.1.0, with Radius-specific change groups and contributor sections. Radius follows Semantic Versioning under its version policy.
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
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
Nothing published for this version
Nothing published for this version
This pull request was generated by the Prepare Release workflow. The plan below is the reviewable release-controller input.
This pull request was generated by the Prepare Release workflow.
The plan below is the reviewable release-controller input.
schemaVersion: 2
version: v0.62.0-rc.1
releaseType: rc
channel: "0.62"
releaseDate: "2026-10-22"
chartVersion: 0.62.0-rc.1
source:
productRef: HEAD
productCommit: 39cd7d3be4134135a85bbe20e3d4e47b6b32eaa7
releaseCommit: null
releaseCommitResolution: release PR squash commit on main
releaseBranch: release/0.62
releasePlanPath: .github/release-plans/v0.62.0-rc.1.yaml
previousVersion: v0.61.1
siblingRepositories:
- name: recipes
repository: radius-project/recipes
sourceCommit: 13f6a59b71831debc7c21e75250c48ecd6796fee
sourceRef: main
- name: dashboard
repository: radius-project/dashboard
sourceCommit: c72ac750645222c2d18378934636c9b39e5588a9
sourceRef: main
- name: bicep-types-aws
repository: radius-project/bicep-types-aws
sourceCommit: 829e215a8b107d28d249fbf8aa659a7df597fe41
sourceRef: main
expectedOutputs:
repository: radius-project/radius
cliAssets:
- arch: amd64
name: rad_darwin_amd64
os: darwin
- arch: arm64
name: rad_darwin_arm64
os: darwin
- arch: amd64
name: rad_linux_amd64
os: linux
- arch: arm
name: rad_linux_arm
os: linux
- arch: arm64
name: rad_linux_arm64
os: linux
- arch: amd64
name: rad_windows_amd64.exe
os: windows
- arch: arm64
name: rad_windows_arm64.exe
os: windows
images:
- category: production
name: applications-rp
radiusBuild: true
requiredPlatforms:
- linux/amd64
- linux/arm/v7
- linux/arm64
- category: non-go
name: bicep
radiusBuild: true
requiredPlatforms:
- linux/amd64
- linux/arm/v7
- linux/arm64
- category: production
name: controller
radiusBuild: true
requiredPlatforms:
- linux/amd64
- linux/arm/v7
- linux/arm64
- category: downstream
name: dashboard
radiusBuild: false
requiredPlatforms:
- linux/amd64
- category: downstream
name: deployment-engine
radiusBuild: false
requiredPlatforms:
- linux/amd64
- linux/arm/v7
- linux/arm64
- category: production
name: dynamic-rp
radiusBuild: true
requiredPlatforms:
- linux/amd64
- linux/arm/v7
- linux/arm64
- category: production
name: pre-upgrade
radiusBuild: true
requiredPlatforms:
- linux/amd64
- linux/arm/v7
- linux/arm64
- category: production
name: ucpd
radiusBuild: true
requiredPlatforms:
- linux/amd64
- linux/arm/v7
- linux/arm64
imageRegistry: ghcr.io/radius-project
helm:
expectedImages:
- alpine
- applications-rp
- bicep
- controller
- dashboard
- deployment-engine
- dynamic-rp
- kubectl
- pre-upgrade
- ucpd
ociReference: oci://ghcr.io/radius-project/helm-chart/radius
orasReference: ghcr.io/radius-project/helm-chart/radius
siblingRepositories:
- radius-project/bicep-types-aws
- radius-project/dashboard
- radius-project/recipes
ociArtifacts:
- artifactType: application/vnd.ms.bicep.provider.artifact
name: aws-bicep-types
repository: biceptypes.azurecr.io/aws
- artifactType: application/vnd.ms.bicep.provider.artifact
name: radius-bicep-types
repository: biceptypes.azurecr.io/radius
includedBackports: []Signed-off-by: radius-release[bot] <294554884+radius-release[bot]@users.noreply.github.com>
Co-authored-by: radius-release[bot] <294554884+radius-release[bot]@users.noreply.github.com>
Today we're happy to announce the release of Radius v0.62.0-rc.1. Check out the highlights below, along with the full changelog for more details.
We would like to extend our thanks to all the new and existing 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.
rad env, rad app, rad init, rad workspace create, and rad resource list now target the Radius.Core resource model without the --preview flag. The legacy rad recipe register/unregister/list/show commands are removed. Update any scripts that pass --preview or use those commands.
The Helm chart now pins Radius component images to the full release version. Restarting pods no longer picks up later patches implicitly. Upgrade the chart to receive patched images. See Upgrading for override behavior.
Radius now embeds a pinned Kubernetes Recipe Pack from the /resource-types-contrib repo and builds the default recipe pack from it, so new environments get a working set of Recipes out of the box. See the Kubernetes Recipe Pack in the repo for more details.
Radius can now store Terraform recipe state in your own S3 bucket or Azure Blob Storage container instead of only in Kubernetes secrets. Learn more in the Terraform state docs.
Many retry and robustness fixes make the CLI and deployments more resilient to transient failures. They cover Bicep recipe downloads, Terraform provider discovery, API server reads, and managed secret deletion. Azure resource deletion now selects supported API versions and deletes in dependency order. Radius type version skew warns before deployment. Digest-pinned Bicep recipe sources are supported.
Welcome to our new contributors who have merged their first PR in this release!
Helm image pinning: This release's Helm chart pins Radius component images to the full release version. Restarting pods no longer picks up later patches implicitly; upgrade the chart to receive patched images. Existing channel aliases remain available, and explicitly configured global.imageTag, component tags, or image references keep overriding chart defaults. To adopt version-pinned defaults while retaining other settings, clear tag overrides and restore image overrides to their default names; an empty image value is invalid.
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.
0.62.0-rc.1 - 2026-10-22
@kachawla, @radius-files-sync[bot], @vinayada1, @nicolejms, @DariuszPorowski, @radius-dependabot-manager[bot], @Copilot, @dependabot[bot], @radius-resource-types[bot], @sk593, @AzureMike, @lakshmimsft, @itpropro, @brooke-hamilton, @allexistence, @willdavsmith, @willtsai, @nithyatsu, @Reshrahim, @pujitha24, @zachcasper
The changelog is based on Keep a Changelog 1.1.0, with Radius-specific change groups and contributor sections. Radius follows Semantic Versioning under its version policy.
This patch fixes an issue where the deployment engine created Kubernetes resources even when their Bicep conditions evaluated to false , causing unwan
This patch fixes an issue where the deployment engine created Kubernetes resources even when their Bicep conditions evaluated to false, causing unwanted resources such as HorizontalPodAutoscalers to remain in the cluster after rad app delete completed successfully. Check out the changelog for more details of what was addressed in this patch.
false are now skipped without invoking their providers, while dependent resources can continue deploying. This prevents unwanted, untracked resources from being created and left behind after application deletion.Review the breaking changes before upgrading if you use the legacy Kubernetes Recipe custom resource or annotation-based Deployment onboarding.
Today we're happy to announce the release of Radius v0.61.0. Check out the highlights below, along with the full changelog for more details.
We would like to extend our thanks to all the new and existing 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.
This release adds more support for managing Radius.Core resources: rad resource list --preview can now list preview environments and applications; rad env create and rad env update --preview can reference a Recipe Pack in another resource group; and each Radius.Core environment must use a unique Kubernetes namespace. Deleting a preview environment now also deletes its applications and resources, rather than leaving them behind.
rad deploy now warns when a template uses the older Applications.* resource types and suggests the corresponding Radius.* replacements where available. Support for the old types will be removed in an upcoming release, so use the warning to migrate your templates. The deployment continues normally in this release.
rad deploy now supports deploying Bicep and ARM JSON templates hosted at HTTPS URLs. Radius validates the URL, resolves relative Bicep module references from the remote template’s location, and redacts URL credentials from command output. See #12676 for details.
Connections to Recipe-backed resources can now provide both ordinary values and references to producer-managed secrets. Radius stores Recipe secret outputs in managed Radius.Security/secrets resources and makes references available to consuming Recipes without decrypting or exposing secret values. See #12709 for details.
The default Kubernetes Recipe Pack now includes PostgreSQL, RabbitMQ, and Redis, expanding the backing services that can be deployed without configuring a custom Recipe Pack. You can download the pack manually and use it. Automatic install of this recipe pack via rad init is still in progress.
Radius deploy workflows now publish rotating deployment-progress snapshots that Radius Canvas can use to display resource status while a deployment is running. The snapshots redact environment-variable values and are retained for one day. See #12727 for details.
Recipe-created cloud resources are now named using their application and environment, preventing separate applications or environments from accidentally sharing the same resource. This avoids conflicts during deployment and helps protect resources from being changed or deleted by another application. See [#12987](https://github.com/radius-project/radius/pull/12987) for details.
This change affects you only if you used Radius’s older Kubernetes onboarding features for your application workloads. It does not remove support for running Radius on Kubernetes or affect workloads that don’t rely on these features.
If you applied a Kubernetes manifest that creates a Recipe custom resource in your cluster, Radius will no longer act on that object to provision backing services or refresh generated connection Secrets. This is the legacy Kubernetes Recipe resource—not a Radius Recipe definition or a Recipe Pack. If you added radapp.io/enabled or related annotations to a Kubernetes Deployment so Radius would provide connection settings as environment variables, Radius will no longer inject or update those settings.
To keep using Radius to deploy and connect application resources, migrate these workloads to Bicep/ARM deployments or Flux GitOps before upgrading. Both remain supported. Helm may leave old Recipe custom resource definitions and objects in the cluster; the upgrade does not migrate or clean them up.See #12952 for details.
Welcome to our new contributors who have merged their first PR in this release!
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.
Review the breaking changes before upgrading if you use the legacy Kubernetes Recipe custom resource or annotation-based Deployment onboarding.
rad deploy by @zachcasper in https://github.com/radius-project/radius/pull/12676--recipe-pack-group to preview rad env create and rad env update commands by @pujitha24 in https://github.com/radius-project/radius/pull/12634rad resource list for Radius.Core/environments and Radius.Core/applications by @lakshmimsft in https://github.com/radius-project/radius/pull/12728Radius.Core/environments by @lakshmimsft in https://github.com/radius-project/radius/pull/12718Radius.Core/environments resource by @lakshmimsft in https://github.com/radius-project/radius/pull/12822rad deploy uses deprecated Applications.* resource types by @lakshmimsft in https://github.com/radius-project/radius/pull/12824Recipe and annotation-based Kubernetes controllers by @willdavsmith in https://github.com/radius-project/radius/pull/12952resourceNameHash to the application and environment by @kachawla in https://github.com/radius-project/radius/pull/12987Full Changelog: https://github.com/radius-project/radius/compare/v0.60.0...v0.61.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
One column per quarter.