10.0.5 missing GitHub Release

[Frulfump]

[marcpopMSFT]

@mmitche Since we shipped 10.0.5 out of the 10.0.104 branch, the tag in the SDK repo ended up being identical. It's right in dotnet/dotnet. Anything we should be doing about that?

[mmitche]

I think this is just an automation oversight. Because no forward flow occurred between 10.0.4 and 10.0.5, there was no difference in sdk sha between those two releases. There are correct tags for all of these, but 10.0.5 is missing a release. Unless there is some prohibition in GitHub against having two releases based on the same sha, then this looks more like an automation failure, and there should be a 10.0.5 release here.

That said, it is a bit confusing since the sha is the same, even though the code changed a little in SDK (implicit versions). However, this isn't any different than a normal release. The VMR is the source of truth, and the releases/tags at the SDK level just represent a very close analog.

[Frulfump]

@marcpopMSFT This was just recently closed as not planned without a comment stating clearly why.

The comment above seems to suggest it's due to some automation failure, can't you create the release manually? (Or do one for just 10.0.201?)