chore: bump nix package to v1.7.0

[EtienneLescot]

Automated bump triggered by release v1.7.0 (opened manually — the bot-triggered PR creation failed because GitHub Actions isn't permitted to create PRs on this repo).

• version → 1.7.0
• npmDepsHash → sha256-cb8loUzQs4fz3um0xbYgtjQdcRZh/Ptk2YPgv3FHP/s= (computed via prefetch-npm-deps package-lock.json by the bump-nix-package workflow)

Merge this so Nix users (NixOS, Home Manager, nix run github:getopenscreen/openscreen) pick up the new release.

Summary by CodeRabbit

• Chores
  • Updated the package to version 1.7.0.
  • Refreshed the recorded dependency integrity data for builds.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: c67133d3-321c-4572-8ac5-0da76f6e7685

📥 Commits

Reviewing files that changed from the base of the PR and between 46bf3eb and c1cfcc6.

📒 Files selected for processing (1)

• nix/package.nix

---

📝 Walkthrough

Walkthrough

The Nix derivation version is bumped from 1.6.0 to 1.7.0, and its npm dependency hash is updated.

Changes

Nix package update

Layer / File(s)	Summary
Package version and dependency hash nix/package.nix	Updates the package version to 1.7.0 and replaces the npmDepsHash value.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• getopenscreen/openscreen#71: Updates the same Nix package version and npm dependency hash.

Suggested reviewers: enriquefft

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description has a summary, but most required template sections are missing, including issue, change type, release impact, testing, and desktop impact.	Fill in the template sections for related issue, type of change, release impact, desktop impact, screenshots/video, and testing.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the Nix package version bump to 1.7.0.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/bump-nix-1.7.0

---

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.}

[EtienneLescot]

Superseded by #230, which carries the same version → 1.7.0 bump plus the two fixes this PR couldn't have delivered on its own.

This PR's hash was stale too. It recorded sha256-cb8loUzQs4fz3um0xbYgtjQdcRZh/Ptk2YPgv3FHP/s=, computed from main as it stood on 2026-07-19. The value the current lockfile actually resolves to is:

sha256-SggSPoDnKzmvgXpIGP11y6h390SkoZszeMjFTaokRjQ=

src here is the repo's own tree rather than a fetched tarball, so npmDepsHash has to track main continuously — and package-lock.json moved 10 times in the two weeks this sat open. Merging it would have left nix build failing, just on a different wrong hash.

#230 also fixes the reason this PR had to be opened by hand (gh pr create running under GITHUB_TOKEN against a repo that forbids Actions from creating PRs), and adds a check that catches hash drift on the PR that causes it instead of at the next release.

Not closing because the work was wrong — closing because the hash inside it has a two-week shelf life and that shelf life is the actual bug.