Rich Lander

We should decide what we want to do w/schemas for these new files. Context: https://github.com/dotnet/core/issues/9431#issuecomment-2305951062

Please stop posting these messages @admin-xspace.

Do you have any thoughts on the index file?

Here is a first take on the index format. ```json { "channel-version": "8.0", "support-phase": "active", "release-type": "lts", "release-date": "2023-11-08", "eol-date": "2026-11-10", "announcement": "https://devblogs.microsoft.com/dotnet/announcing-dotnet-8/", "release-notes": "https://github.com/dotnet/core/blob/main/release-notes/8.0/README.md", "lifecycle-policy": "https://aka.ms/dotnetcoresupport", "releases.json": "https://dotnetcli.blob.core.windows.net/dotnet/release-metadata/8.0/releases.json", "supported-os.json":...

Welcome! Great q. I added a document to a current PR that intends to offer that information. https://github.com/dotnet/core/pull/9412/files#diff-697fd03ea53fdf95355fbf05df1973f5980f311d5e67dd141ad9ee87acf2e099 I'm also working on making it easy to consume these JSON files:...

This is related: https://github.com/dotnet/core/pull/9425 https://learn.microsoft.com/en-us/visualstudio/mac/what-happened-to-vs-for-mac?view=vsmac-2022 It doesn't seem like the VS for Mac properties have any value. I asked @leecow to stop generating them in all versions.

@rbhanda

The team is working on resolving this. Thanks for reporting this.

Can you check again? That CVE has been updated/re-published.

Will this affect your use cases @mairaw?