Skip to content

Conversation

@richlander
Copy link
Member

@richlander richlander commented Jan 7, 2026

Rendered

The .NET project has published release notes in JSON and markdown for many years. There are challenging aspects of the current scheme that could benefit from a new approach. A new from-scratch approach is needed to resolve its problems. The new approach leans heavily on hypermedia both as inspiration and actual format to push us towards a strong and proven design paradigm.

The two major problems with the entrypoint JSON document:

  • It needs to be updated every month (with downstream implications) by virtue of its schema.
  • It references large monolithic documents that are problematic for multiple scenarios

Prototype entrypoints for graph:

The first two entrypoints are for LLMs and the last for tools as the intended replacement for releases-index.json.

Related:


## Version Index Modeling

The version index has three layers: releases, major version, patch version. Most nodes in the graph are named `index.json`. The examples should look similar to the HAL spec documents shared earlier.
Copy link
Member

@leecow leecow Jan 8, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should it be explained that major version is deliberately combining major.minor?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants