Investigate pulling the RC tagged version of bicep during release verification

[sk593]

Engineering Improvement

Area for Improvement (required)

This issue is to investigate pulling the RC tagged version of bicep during the release verification workflow or somewhere in the release process.

Observed behavior (required)

We ran into an issue with the 0.27 release process where the samples verification workflow failed while downloading bicep but was not caught in any other workflows. This is because the samples repo is the only place that tests pulling an RC tagged version of bicep here: https://github.com/radius-project/samples/blob/a420f9e02151240905ceb63c0da881f268d5d527/.github/workflows/test.yaml#L189

We found that the RC tagged version of bicep was not getting uploaded and had to create a fix during the 0.27 release process.

Desired behavior (required)

Ideally, we would have caught this download failure earlier in the release process, before we ran the samples verification workflow. We have a release verification workflow that runs once we create an RC version of the release, but there's no step to test bicep downloads, see here: https://github.com/radius-project/radius/blob/main/.github/scripts/release-verification.sh

Proposed Fix (optional)

We'd like to investigate if we can test bicep downloads earlier in the release process so that we catch possible errors sooner.

System information

rad Version (required)

Operating system (required)

Additional context

AB#10635

[radius-triage-bot]

👋 @sk593 Thanks for filing this issue.

A project maintainer will review this issue and get back to you soon.

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

[radius-triage-bot]

👍 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

[radius-triage-bot]

We've prioritized work on this issue. Please subscribe to this issue for notifications, we'll provide updates as we make progress.

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

[nicolejms]

Removing important since we will need to revisit how we decide what version of the public bicep release we will be using each release.