Migrate release automation to GoReleaser

[brooke-hamilton]

Summary

Migrate the Radius release automation from the current custom GitHub Actions workflows to GoReleaser.

Design Document

radius-project/design-notes#153 — feat: new release lifecycle (authored by @DariuszPorowski, merged 04/07/2026)

Goals

• Replace fragile custom release workflows with GoReleaser
• Reduce the number of manual steps and failure modes in the release process
• Enable retrying failed release steps without cutting a new RC
• Simplify cross-repo version coordination (core / deployment-engine / Helm chart)

Implementation

Implementation is tracked through the Task sub-issues attached to this feature. Their order, scope, dependencies, and exit criteria follow the GoReleaser release lifecycle implementation plan, based on the GoReleaser release lifecycle design.

[radius-triage]

👍 We've reviewed this issue and have agreed to add it to our backlog. Please subscribe to this issue for notifications, we'll provide updates when we pick it up.

We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.

For more information on our triage process please visit our triage overview