Module release 

The release module: the changelog, the version, and the compatibility analysis behind it — all three derived.

Three capabilities, all read-only, all answered by crate::release — the same code the command line renders, the generated document is written from, and the site page shows. Neither reads a file somebody maintains: the changelog composes the layer’s own release records, decisions and the repository’s commits, and the version report reads the one place the version is authored and says whether the projection the shell tool prints is current.

Raising the version is not here. It writes tracked files, which makes it a repository mutation, and the exposure policy keeps repository mutations off every machine surface — so release bump is a command and nothing more, and this module is the read half.

Structs

AnalysisInput

Which release to measure this tree against.

ChangelogInput

Which part of the changelog to answer with.

NextInput

The input of release.next: the landing it is asked about.

Constants

ANALYSIS_ID

The compatibility analysis, named beside its declaration.

CHANGELOG_ID

The capability’s own id. Beside its declaration, so the two cannot drift apart without the test below noticing; the document carries it so that no page has to enumerate where this value is served.

CHANGELOG_URI

The URI under which the changelog is read as an MCP resource.

NEXT_ID

The landing decision, named beside its declaration.

Functions

module

The module.

produced_by

Where else the changelog can be had, read off the declarations that already say so.