The release.json files grow without bound (other than EOL). That's not a great architecture.

This file: https://github.com/dotnet/core/blob/main/release-notes/9.0/releases.json

Could look more like: https://github.com/dotnet/core/blob/main/release-notes/releases-index.json

And then have a release.json file in a directory like: https://github.com/dotnet/core/tree/main/release-notes/8.0/8.0.1

For most use cases, this approach would dramatically reduce the number of bytes downloaded, at least by a naive JSON reader like a serializer. It just occurred to me now, but much of the (example) premise of my Convenience of System.Text.Json post could be underminded by doing this.