From cfacdf3a188483e87282853d9b9bba89709ee8c8 Mon Sep 17 00:00:00 2001
From: Etienne Lescot <etiennelescot@gmail.com>
Date: Mon, 3 Aug 2026 09:26:43 +0200
Subject: [PATCH] fix(nix): make the v1.8.0 tag buildable, since the tag is
 what Nix users get
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

promote.yml pushes the stable tag on this branch's tip, and nix/package.nix
here still carries what v1.6.0 left on 2026-07-05. `src` is the repo tree
rather than a fetched tarball, so `nix run github:…/v1.8.0` builds this file
and would refuse the mismatch on sight.

bump-nix-package.yml cannot cover it: it fires after the release is published,
reads main, and opens its PR against main — the tag is never in its path. So
the hash has to be right here, before the tag is cut.

package-lock.json is byte-identical between this branch and main, so the value
is the one CI computed on main in run 30789963366, not a fresh guess:

  sha256-SggSPoDnKzmvgXpIGP11y6h390SkoZszeMjFTaokRjQ=

Version goes straight to 1.8.0 — promote rewrites package.json at tag time but
never touches this file. With both lines correct here, the bump workflow finds
nothing to change after the release and no-ops, which is the intended resting
state rather than a repair.
---
 nix/package.nix | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/nix/package.nix b/nix/package.nix
index f30c7c7e41..0ec078312d 100644
--- a/nix/package.nix
+++ b/nix/package.nix
@@ -11,7 +11,7 @@
 buildNpmPackage {
   nodejs = nodejs_22;
   pname = "openscreen";
-  version = "1.6.0";
+  version = "1.8.0";
 
   src =
     let
@@ -33,7 +33,7 @@ buildNpmPackage {
       );
     };
 
-  npmDepsHash = "sha256-IZypOLWlDShIjCKWxlJcrdtIkMu0P/DuXaq4c0HW3FY=";
+  npmDepsHash = "sha256-SggSPoDnKzmvgXpIGP11y6h390SkoZszeMjFTaokRjQ=";
 
   env.ELECTRON_SKIP_BINARY_DOWNLOAD = "1";