Skip to content

Commit e228ba9

Browse files
committed
fix(opencode): keep upstream nixpkgs so their FOD hash applies as-is
opencode's node_modules FOD is hash-pinned by their CI against the bun of their own nixpkgs (bun 1.3.13). Our nixpkgs follows a newer bun (1.4.2) which lays out node_modules differently, breaking the pin deterministically (spec FY/I7zxm vs got Ppc2Kgb9). Stop following our nixpkgs for this input: their hashes.json then applies verbatim, on every platform, with nothing for us to maintain — no hash table, no version guard, no override. Tracked upstream as anomalyco/opencode#49063 proposing a lockfile-aware FOD that removes the bun dependency entirely.
1 parent ff869e0 commit e228ba9

2 files changed

Lines changed: 21 additions & 7 deletions

File tree

‎flake.lock‎

Lines changed: 17 additions & 3 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

‎flake.nix‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -11,10 +11,10 @@
1111
url = "github:Mic92/sops-nix";
1212
inputs.nixpkgs.follows = "nixpkgs";
1313
};
14-
opencode = {
15-
url = "github:anomalyco/opencode";
16-
inputs.nixpkgs.follows = "nixpkgs";
17-
};
14+
# Workaround: their CI calibrates node_modules FOD hashes against
15+
# the bun of their own nixpkgs, which ours follows differently.
16+
# Remove when upstream pins become bun-agnostic (opencode#49063).
17+
opencode.url = "github:anomalyco/opencode";
1818
opencode-nvim = {
1919
url = "github:NickvanDyke/opencode.nvim";
2020
flake = false;

0 commit comments

Comments
 (0)