lix-project/lix-releng-staging
0
0
Fork 0
Code Packages Activity

release-notes: build unreleased release notes by default

Browse source 
Surely if you have unreleased changes you want them on a page right?

`officialRelease` means "this is a *release version*", which is a
reasonable case to not want it, but we are not that here.

I understand wanting to be able to turn it off for deps reasons or
something, but other than that, uhh, seems better to just turn it on
always; it is basically free compute-wise to the point we run it on
pre-commit.

Part two of fixing lix#297.

Fixes: lix-project/lix#297
Change-Id: I0f8dd1ae42458df371aef529c456e47a7ac04ae0
This commit is contained in:
jade 2024-05-15 15:01:38 -07:00
parent 2a7b3d7c94
commit 7cfaf057e3
2 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
flake.nix
View file

@ -57,7 +57,7 @@
officialRelease = false;
# Set to true to build the release notes for the next release.
buildUnreleasedNotes = false;
buildUnreleasedNotes = true;
version = lib.fileContents ./.version + versionSuffix;
versionSuffix =

4
package.nix
View file

@ -51,9 +51,9 @@
pname ? "nix",
versionSuffix ? "",
officialRelease ? true,
officialRelease ? false,
# Set to true to build the release notes for the next release.
buildUnreleasedNotes ? false,
buildUnreleasedNotes ? true,
internalApiDocs ? false,
# Not a real argument, just the only way to approximate let-binding some