From 7cfaf057e35b7bb329ffff344e30fdfc850566c3 Mon Sep 17 00:00:00 2001
From: Jade Lovelace <lix@jade.fyi>
Date: Wed, 15 May 2024 15:01:38 -0700
Subject: [PATCH] release-notes: build unreleased release notes by default

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: https://git.lix.systems/lix-project/lix/issues/297
Change-Id: I0f8dd1ae42458df371aef529c456e47a7ac04ae0
---
 flake.nix   | 2 +-
 package.nix | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/flake.nix b/flake.nix
index 737e89b7c..14ee8e1ad 100644
--- a/flake.nix
+++ b/flake.nix
@@ -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 =
diff --git a/package.nix b/package.nix
index 0186b7472..83a4411ec 100644
--- a/package.nix
+++ b/package.nix
@@ -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