-
-
Notifications
You must be signed in to change notification settings - Fork 759
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[dotnet] Automation from releases-index.json #2234
Comments
We are already using https://github.com/dotnet/core for automation, which provides all releases, instead of just the latest one. We can probably use it to add EOL dates, but we haven't decided on the schema for that yet. (Automation only supports versions+dates for now). |
Thanks for the explanation. Perhaps we can use the json and add new cycles with eol via automation. If you don't see a possibility you can close the issue. |
Releases of new cycles are also picked up by the current automation (but not automatically added, we only have a warning, such as #2236 (comment)). But it can definitively be useful to get EOL dates. |
Closing this, will track at endoflife-date/release-data#51 |
There is a json file with all the details we need for .NET: https://dotnetcli.blob.core.windows.net/dotnet/release-metadata/releases-index.json
Source is: https://learn.microsoft.com/azure/devops/pipelines/tasks/reference/use-dotnet-v2
I am not that good with automation but I think we can take all the details from there. What do you think?
The text was updated successfully, but these errors were encountered: