You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The new preview images have a tagging scheme that's out of alignment with the proposal - instead of 8.0-preview.N, images with the 8.0.0-preview.N format are visible on mcr.microsoft.com. I'd like to request retags to fix the version numbers - this mismatch impacts tag inference for the SDK container build tooling.
Steps to Reproduce
Other Information
Screenshot of dotnet/aspnet tags matching preview.2:
The text was updated successfully, but these errors were encountered:
[Triage]
This was an inaccuracy in the original proposal. It doesn't really provide any value to have both 8.0-preview.N and 8.0.0-preview.N tags because they will always be synonymous. Normally, a two-part version number like 8.0 would be a floating tag that would be updated with each servicing release. But in the context of previews, that doesn't happen. The three-part version number will always be 8.0.0 for each preview release. So 8.0 and 8.0.0 are always equivalent for each preview release.
For that reason, we won't be publishing any 8.0-preview.N tags. We'll get the original proposal updated to reflect this.
Describe the Bug
The new preview images have a tagging scheme that's out of alignment with the proposal - instead of
8.0-preview.N
, images with the8.0.0-preview.N
format are visible on mcr.microsoft.com. I'd like to request retags to fix the version numbers - this mismatch impacts tag inference for the SDK container build tooling.Steps to Reproduce
Other Information
Screenshot of dotnet/aspnet tags matching preview.2:
The text was updated successfully, but these errors were encountered: