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 logic which computes the EOL annotations that need to be applied has an option for querying the .NET releases JSON file to determine the EOL dates of .NET versions:
It associates those dates with the Dockerfiles having the same .NET version. This is fine for the core repos like runtime, aspnet, and sdk because the images in those repos follow the same versioning as the main .NET product. But in cases like YARP which have their own separate versioning, it's not applicable. There is danger of those versions matching an EOL .NET version and having those images incorrectly annotated as EOL when they're not.
So there's a need to be able to scope the product EOL date to specific repos so that it won't match on other repos where those dates aren't applicable.
The text was updated successfully, but these errors were encountered:
The logic which computes the EOL annotations that need to be applied has an option for querying the .NET releases JSON file to determine the EOL dates of .NET versions:
docker-tools/src/Microsoft.DotNet.ImageBuilder/src/Commands/GenerateEolAnnotationDataCommand.cs
Lines 128 to 140 in 5c9606d
It associates those dates with the Dockerfiles having the same .NET version. This is fine for the core repos like runtime, aspnet, and sdk because the images in those repos follow the same versioning as the main .NET product. But in cases like YARP which have their own separate versioning, it's not applicable. There is danger of those versions matching an EOL .NET version and having those images incorrectly annotated as EOL when they're not.
So there's a need to be able to scope the product EOL date to specific repos so that it won't match on other repos where those dates aren't applicable.
The text was updated successfully, but these errors were encountered: