nixpkgs/nixos/doc/manual/release-notes/release-notes.md

# Release Notes {#ch-release-notes}

This section lists the release notes for each stable version of NixOS and current unstable revision.

```{=include=} sections
rl-2411.section.md
rl-2405.section.md
rl-2311.section.md
rl-2305.section.md
rl-2211.section.md
rl-2205.section.md
rl-2111.section.md
rl-2105.section.md
rl-2009.section.md
rl-2003.section.md
rl-1909.section.md
rl-1903.section.md
rl-1809.section.md
rl-1803.section.md
rl-1709.section.md
rl-1703.section.md
rl-1609.section.md
rl-1603.section.md
rl-1509.section.md
rl-1412.section.md
rl-1404.section.md
rl-1310.section.md
```
nixos-render-docs: add structural includes, use for manual this adds support for structural includes to nixos-render-docs. structural includes provide a way to denote the (sub)structure of the nixos manual in the markdown source files, very similar to how we used literal docbook blocks before, and are processed by nixos-render-docs without involvement of xml tooling. this will ultimately allow us to emit the nixos manual in other formats as well, e.g. html, without going through docbook at all. alternatives to this source layout were also considered: a parallel structure using e.g. toml files that describe the document tree and links to each part is possible, but much more complicated to implement than the solution chosen here and makes it harder to follow which files have what substructure. it also makes it much harder to include a substructure in the middle of a file. much the same goes for command-line arguments to the converter, only that command-lined arguments are even harder to specify correctly and cannot be reasonably pulled together from many places without involving another layer of tooling. cli arguments would also mean that the manual structure would be fixed in default.nix, which is also not ideal. 2023-02-11 08:48:06 +01:00			`# Release Notes {#ch-release-notes}`

			`This section lists the release notes for each stable version of NixOS and current unstable revision.`

			```{=include=} sections
24.05 is Vicuña 2024-05-22 18:15:34 +02:00			`rl-2411.section.md`
nixos/doc: include section for 24.05 People are actively writing release notes already and with this it's ensured that the contents are actually valid. Also, when writing release notes for something, I'd like to be able to see a preview. 2023-12-14 19:20:33 +01:00			`rl-2405.section.md`
23.11 is Tapir 2023-05-22 21:14:06 +02:00			`rl-2311.section.md`
nixos-render-docs: add structural includes, use for manual this adds support for structural includes to nixos-render-docs. structural includes provide a way to denote the (sub)structure of the nixos manual in the markdown source files, very similar to how we used literal docbook blocks before, and are processed by nixos-render-docs without involvement of xml tooling. this will ultimately allow us to emit the nixos manual in other formats as well, e.g. html, without going through docbook at all. alternatives to this source layout were also considered: a parallel structure using e.g. toml files that describe the document tree and links to each part is possible, but much more complicated to implement than the solution chosen here and makes it harder to follow which files have what substructure. it also makes it much harder to include a substructure in the middle of a file. much the same goes for command-line arguments to the converter, only that command-lined arguments are even harder to specify correctly and cannot be reasonably pulled together from many places without involving another layer of tooling. cli arguments would also mean that the manual structure would be fixed in default.nix, which is also not ideal. 2023-02-11 08:48:06 +01:00			`rl-2305.section.md`
			`rl-2211.section.md`
			`rl-2205.section.md`
			`rl-2111.section.md`
			`rl-2105.section.md`
			`rl-2009.section.md`
			`rl-2003.section.md`
			`rl-1909.section.md`
			`rl-1903.section.md`
			`rl-1809.section.md`
			`rl-1803.section.md`
			`rl-1709.section.md`
			`rl-1703.section.md`
			`rl-1609.section.md`
			`rl-1603.section.md`
			`rl-1509.section.md`
			`rl-1412.section.md`
			`rl-1404.section.md`
			`rl-1310.section.md`
			```