From 57993913211aa6d0b4c3461de9c9eef87063f825 Mon Sep 17 00:00:00 2001
From: satoshi <satoshi@bitcoin.com>
Date: Sat, 23 May 2026 13:47:24 +0300
Subject: [PATCH] Fix config generation error for zmq-enabled on upgrade

The field was moved to the top level but not marked nullable, so
upgrades from older configs (where it lived under advanced) failed
with "Field Is Not Nullable". The entrypoint already falls back to
true via yq's // operator.
---
 scripts/procedures/getConfig.ts | 1 +
 1 file changed, 1 insertion(+)

diff --git a/scripts/procedures/getConfig.ts b/scripts/procedures/getConfig.ts
index 09a50be..2193e36 100644
--- a/scripts/procedures/getConfig.ts
+++ b/scripts/procedures/getConfig.ts
@@ -109,6 +109,7 @@ export const getConfig: T.ExpectedExports.getConfig = compat.getConfig({
     "name": "Enable ZMQ Block Notifications",
     "description":
       "Subscribe to Bitcoin Core's hashblock ZMQ topic for sub-second block detection on the dashboard. Requires zmqpubhashblock enabled on bitcoind.",
+    "nullable": true,
     "default": true,
   },
   "advanced": {