I am only aware of nixos release notes. However, as a “rolling release” distro, we have software version updates and nixos module changes (especially breaking ones) quite frequently.
Because of such breaking changes, people may want to be notified about parts of nixos that they’re using, not all of them (like the big list in each os release note)
I can imagine a structured changelog provided with nixos that reflects all the software or module changes. Something like this:
- software nixpkgs.x: from v0.1 to 0.2 (nixpkgs git commit m to commit n): some note - software nixpkgs.x: from v0.2 to 0.3 (nixpkgs git commit p to commit q): some note - software pkgs.y: from v1.5 to 1.9 (nixpkgs git commit u to commit v): some migration guides - nixos module foo.bar.bazz (from nixpkgs git commit r to commit s) ...
That changelog should be amended when:
- a PR gets merged to nixpkgs repo and the PR author has something say (it’s totally okay to have empty change note if it’s not a breaking change)
- a nixos maintainer submit such a change note. Especially useful when a breaking change is only discovered when people filing bugs.
People will then open a user interface designed to pinpoint to the change notes they’re interested in.