v1.17.11 tag: Nix build fails with stale bun.lock (--frozen-lockfile)

[ndrwstn]

Description

nix build github:anomalyco/opencode/v1.17.11#default fails in the node_modules derivation:

> bun install v1.3.13
> error: lockfile had changes, but lockfile is frozen

The node_modules.nix derivation runs bun install --frozen-lockfile, but the bun.lock is stale vs package.json on the v1.17.11 tag. PR #33166 added a postPatch in nix/opencode.nix to soften the bun version check, but the node_modules derivation runs before that patch and fails first.

The dev branch already builds fine — the lockfile was regenerated at some point after the tag was cut. This is specific to the v1.17.11 release tag.

OpenCode version

v1.17.11

Steps to reproduce

nix build github:anomalyco/opencode/v1.17.11#default --no-link

Expected: builds successfully. Actual: fails with lockfile had changes, but lockfile is frozen.

Plugins

N/A

Operating System

macOS (aarch64) — also reproducible on Linux x64

Terminal

N/A

---

Tagging @jerome-benoit since you've been driving Nix fixes. The bun version check patch in #33166 was helpful but doesn't cover this case since the stale lockfile error is in node_modules.nix before opencode.nix's postPatch runs. Would a v1.17.12 tag with a regenerated bun.lock be possible?

[jerome-benoit]

It's just the tag, the release process is not nix aware.

[mausch]

The issue around pinning ghostty-web was fixed in 077deb9

[jerome-benoit]

The issue around pinning ghostty-web was fixed in 077deb9

It's totally unrelated to the fact that the release process is not nix aware.

[github-actions]

To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.