fix(nix): make the v1.8.0 tag buildable

[EtienneLescot]

Targets release/v1.8.0, not main — nothing from main comes along.

Why the fix on main isn't enough

src in nix/package.nix is this repo's own tree, not a tarball fetched at a tag. So what a Nix user builds depends on the ref they point at:

Command	Builds
nix run github:getopenscreen/openscreen	main
nix run github:getopenscreen/openscreen/v1.8.0	this branch's tip

And promote.yml pushes the stable tag on the release branch tip:

https://github.com/getopenscreen/openscreen/blob/main/.github/workflows/promote.yml#L84 — Push stable tag on the release branch tip

So v1.8.0 would ship the nix/package.nix this branch currently carries, untouched since 2026-07-05:

version = "1.6.0"
npmDepsHash = "sha256-IZypOLWlDShIjCKWxlJcrdtIkMu0P/DuXaq4c0HW3FY="

bump-nix-package.yml structurally cannot repair that. It fires on release: published, checks out main, and opens its PR against main. The tag is never on its path — it has never once touched a tag.

The value is already proven, not guessed

package-lock.json is byte-identical between this branch and main:

git diff --quiet origin/main origin/release/v1.8.0 -- package-lock.json # clean

So the correct hash is exactly what CI computed on main in run 30789963366:

sha256-SggSPoDnKzmvgXpIGP11y6h390SkoZszeMjFTaokRjQ=

Version

Straight to 1.8.0. promote.yml rewrites package.json at tag time but never touches nix/package.nix.

With both lines correct here, bump-nix-package.yml hits its git diff --quiet early-exit after the release and no-ops — the workflow becomes a safety net rather than the thing doing the repair after the fact.

Merging this back into main is safe

promote.yml rebase-merges this branch into main afterwards. No commit on this branch touches nix/ other than this one:

git log origin/main..origin/release/v1.8.0 -- nix/ # empty before this PR

So main keeps whatever #230 leaves it with, and this lands on top with the same hash.

Depends on nothing

Independent of #230. #230 fixes main and stops the drift recurring; this makes the v1.8.0 tag buildable. Both are wanted, in either order.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 7799f158-61d2-4b6c-92bf-a690cf0638f2

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}