Point main at the production RadiantWave channel and guard it in CI

The dev->main merge left the channel block in flake.nix pointing at radiantwave-dev, so prod ISOs built from main shipped the dev app (which versions itself by short git hash) and the updater polled the dev Attic manifest. Restore the channel block to main values, re-pin flake.lock to the latest radiantwave main revision, and expose channelName so the prod build workflows can fail fast if main ever resolves to the dev channel.
2026-09-01 09:25:03 -05:00
parent 0860dea6c7
commit 6e446893f3
6 changed files with 61 additions and 7 deletions
@@ -220,11 +220,11 @@
        "nixpkgs": "nixpkgs_3"
      },
      "locked": {
-        "lastModified": 1787675420,
-        "narHash": "sha256-2Hq9IcgdDXQc2uQ4yC/5NZVjcZaFCcVS78vj+ee+y/Q=",
+        "lastModified": 1787953913,
+        "narHash": "sha256-6M0xyNIwhGiOiOyS+URYzhKdV69fRgifXYqoGmHrmaY=",
        "ref": "main",
-        "rev": "43cd93bbd7dde69c55c00a28c1691e1a192eda39",
-        "revCount": 47,
+        "rev": "fee31c87b8ece4bb025e7ec10aed03c9794e2143",
+        "revCount": 56,
        "type": "git",
        "url": "https://gitea.radiantwavetech.com/RadiantWaveTech/radiantwave.git"
      },