Milena Hristova

# Set ProducesDotNetReleaseShippingAssets property in Publishing.props - [ ] You've read the [Contributor Guide](https://github.com/dotnet/aspnetcore/blob/main/CONTRIBUTING.md) and [Code of Conduct](https://github.com/dotnet/aspnetcore/blob/main/CODE-OF-CONDUCT.md). - [ ] You've included unit or integration tests for your change,...

- [ ] This issue is blocking - [ ] This issue is causing unreasonable pain A few recent PRs to Arcades `release/7.0` branch are failing tests on Windows -...

Backport of https://github.com/dotnet/arcade/pull/14495 ### To double check: * [ ] The right tests are in and and the right validation has happened. Guidance: https://github.com/dotnet/arcade/tree/main/Documentation/Validation

Backport of https://github.com/dotnet/arcade/pull/14495

Backport of https://github.com/dotnet/arcade/pull/14495 ### To double check: * [ ] The right tests are in and and the right validation has happened. Guidance: https://github.com/dotnet/arcade/tree/main/Documentation/Validation

Remove release packages layout creation from gather-drop

3

Epic: https://github.com/dotnet/release/issues/740 Remove the release packages layout creation from gather-drop. The layout creation is moved to the release infra with https://github.com/dotnet/release/issues/828 Don't copy packages into folders, the output of gather-drop...

Failing build: https://dev.azure.com/dnceng/internal/_build/results?buildId=2406729&view=results Test build: https://dev.azure.com/dnceng/internal/_build/results?buildId=2406822&view=results ### Release Note Category - [ ] Feature changes/additions - [x] Bug fixes - [ ] Internal Infrastructure Improvements ### Release Note Description Skip...

Move release package layout creation to the release infrastructure

1

### Context The first step of the .NET staging pipeline is to gather all artifacts associated with a installer BAR ID using [darc gather-drop](https://github.com/dotnet/arcade/blob/main/Documentation/Darc.md#gather-drop). The command gathers shipping and non...

Use ReleaseCli operation for repo tagging in release pipeline

4

Investigate using [create-release-tags operation](https://dev.azure.com/dnceng/internal/_git/dotnet-release?path=/src/Microsoft.DotNet.Release/Microsoft.DotNet.ReleaseCli/src/Operations/CreateReleaseTagsOperation.cs) in the release pipeline instead of the [repo-tagging script](https://dev.azure.com/dnceng/internal/_git/dotnet-release?path=/src/scripts/repo-tagging/repo-tagging.ps1) ## Linked issues: - [ ] https://github.com/dotnet/arcade-services/issues/3008 - [ ] https://github.com/dotnet/arcade-services/issues/2455

`Publish Post-Signing Assets` fails to publish to `dotnet-8` feed

3

Publishing to `dotnet 8` feeds fail in the `Publish Post-Signing Assets` stage because there are some major-version changes that were not done. For this publishing stage dynamic feeds are generated...