Baixar Radius 0.61.0 per a Windows

## Announcing Radius v0.61.0

Today we're happy to announce the release of Radius v0.61.0. Check out the [highlights](#highlights) below, along with the [full changelog](#full-changelog) for more details.

We would like to extend our thanks to all the [new](#new-contributors) and existing contributors who helped make this release possible!

## Intro to Radius

If you're new to Radius, check out our website, [radapp.io](https://radapp.io), for more information. Also visit our [getting started guide](https://docs.radapp.io/getting-started/) to learn how to install Radius and create your first app.

## Highlights

### Updates to extensible Radius resources

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.

### Deploy templates directly from HTTPS URLs

`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](https://github.com/radius-project/radius/pull/12676) for details.

### Share secrets between connected resources

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](https://github.com/radius-project/radius/pull/12709) for details.

### More services in the default Kubernetes Recipe Pack

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](https://github.com/radius-project/resource-types-contrib/tree/main/recipe-packs/kubernetes) and use it. Automatic install of this recipe pack via `rad init` is still in progress.

### Live deployment progress for Radius Canvas

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](https://github.com/radius-project/radius/pull/12727) for details.

### Prevent resource-name collisions between applications

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)](https://github.com/radius-project/radius/pull/12987) for details.

## Breaking changes

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](https://github.com/radius-project/radius/pull/12952) for details.

## New contributors

Welcome to our new contributors who have merged their first PR in this release!

• @pujitha24 made their first contribution in <https://github.com/radius-project/radius/pull/12634>

## Upgrading to Radius v0.61.0

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](https://docs.radapp.io/guides/operations/kubernetes/kubernetes-upgrade/) for full details.

Review the [breaking changes](#breaking-changes) before upgrading if you use the legacy Kubernetes `Recipe` custom resource or annotation-based Deployment onboarding.

## Full changelog

• Deploy remote Bicep or JSON files over HTTPS with `rad deploy` by @zachcasper in <https://github.com/radius-project/radius/pull/12676>
• Add `--recipe-pack-group` to preview `rad env create` and `rad env update` commands by @pujitha24 in <https://github.com/radius-project/radius/pull/12634>
• Add preview support to `rad resource list` for `Radius.Core/environments` and `Radius.Core/applications` by @lakshmimsft in <https://github.com/radius-project/radius/pull/12728>
• Add live deployment progress reporting by @nithyatsu in <https://github.com/radius-project/radius/pull/12727>
• Add project-managed secrets through connections by @willdavsmith in <https://github.com/radius-project/radius/pull/12709>
• Enforce Kubernetes namespace uniqueness for `Radius.Core/environments` by @lakshmimsft in <https://github.com/radius-project/radius/pull/12718>
• Add RabbitMQ to the default Kubernetes Recipe Pack by @willdavsmith in <https://github.com/radius-project/radius/pull/12752>
• Add PostgreSQL to the default Kubernetes Recipe Pack by @willdavsmith in <https://github.com/radius-project/radius/pull/12755>
• Add Redis to the default Kubernetes Recipe Pack by @willdavsmith in <https://github.com/radius-project/radius/pull/12754>
• Cascade-delete applications and resources when deleting a `Radius.Core/environments` resource by @lakshmimsft in <https://github.com/radius-project/radius/pull/12822>
• Warn when `rad deploy` uses deprecated `Applications.*` resource types by @lakshmimsft in <https://github.com/radius-project/radius/pull/12824>
• Reject schema-invalid dynamic resource PUT requests before persistence by @nellshamrell in <https://github.com/radius-project/radius/pull/12979>
• Remove legacy `Recipe` and annotation-based Kubernetes controllers by @willdavsmith in <https://github.com/radius-project/radius/pull/12952>
• Add a read-only PVC mount for container image build contexts by @AzureMike in <https://github.com/radius-project/radius/pull/12982>
• Fix multi-cluster Bicep Recipe deletion by @brooke-hamilton in <https://github.com/radius-project/radius/pull/13054>
• Scope `resourceNameHash` to the application and environment by @kachawla in <https://github.com/radius-project/radius/pull/12987>
• Upgrade Bicep to v0.46.1 with scoped local registry trust by @willdavsmith in <https://github.com/radius-project/radius/pull/13075>

**Full Changelog**：<https://github.com/radius-project/radius/compare/v0.60.0...v0.61.0>