Tracking release pipeline issues

[mthalman]

This is a tracking issue for everything related to the release pipeline.

The issues can be divided up into the following categories:

• happy-path: Issues affecting the normal operation of the pipeline.
• validation: Issues affecting the validation executed by the pipeline that ensures things have the expected state.
• idempotency: It's often necessary to run the pipeline, or a portion of it, multiple times. For portions of the logic which had already been executed previously, there should be no negative affects.
• dry-run: Issues affecting the operation of the pipeline in dry run mode.
• testability: The pipeline itself should be testable to ensure its correctness.
• output: Features related to the output produced by the pipeline.

The issues below are listed in priority order:

• [happy-path] Update Versions.props
  • 8.0: Release PR for .NET 8.0 doesn't update prebuilts/artifact versions correctly #3344
  • 7.0: Release pipeline: PrivateSourceBuildSDKVersion property not updated in generated PR #3385
• Release pipeline: Use of announcement gist results in TAG_URL variable not being set #3447
  [happy-path]
• Release pipeline: Use of service connection for publishing to package feed #3444
  [happy-path]
• Release pipeline: Error occurs if release with same tag name already exists #3449
  [idempotency]
• Release pipeline: Duplicate announcement discussion posted #3450
  [idempotency]
• Implement a mechanism to test the release pipeline #3387
  [testability]
• Release pipeline: Announcement gist should be consumed in pre-release stage #3443
  [validation]
• Release pipeline: Dry run failure in "Validate release tag" task of release stage #3415
  [dry-run]
• Provide buildable source tarballs as release artifacts #3265
  [output]
• Automate source-build partners content #3196
  [output]
• Source build release pipeline should validate the availability of the commit shas #3058
  [validation]
• Release pipeline should look up and verify the associated SDK diff run #3297
  [validation]

The following issues are time-based, meaning that they need to be done at a certain point in the release cycle and so they don't fit into the prioritized list above:

• Source-build release pipeline should collect artifacts from PreviousSourceBuiltSdk CI legs after GA #3304
  [output]

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.