Repository navigation
Split publishing on a per-version basis #6700
Description
Activity
[Triage] This is needed for https://github.com/dotnet/dotnet-docker-internal/issues/7431
- added a parent issue
on Oct 13, 2025 - removed a parent issue
on Jan 8, 2026 The current release staging workflow works when using
--pathfilters like--path '*8.0*',--path '*9.0*',--path '*10.0*'. And we can correctly publish SDK only releases when setting thenoCachevariable tofalsein the staging pipeline.The unknowns here are what to do about:
- merging the dotnet-docker PR on release day.
- updating dockerfile links in the dotnet/versions repo after images are released.
- shared images between major .NET versions.
Currently publishing of .NET container images is done by publishing all .NET versions together. This is because there can be dependencies amongst the different versions via the
runtime-depsbase image.But this is problematic because any issue that pops up for a given .NET version will block publishing as a whole, affecting the publishing of all versions. For example, there have been cases in the past where something was discovered on release day that prevented the release of a Preview version and caused it to be delayed by several days. This would block the publishing of the .NET versions that are in servicing and would impact the release of security fixes. There can be no delay for this. In order to work around this, the preview changes would have to be reverted and all the images rebuilt. This in itself increases the delay of publishing those images that, ideally, should have been unaffected by the issue.