Skip to content

Commit c933a9a

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 c933a9a

2 files changed

Lines changed: 22 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: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -11,10 +11,11 @@
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+
# opencode's node_modules FOD is hash-pinned by their CI against the
15+
# bun of their own nixpkgs: keeping their nixpkgs (no follows) makes
16+
# their pin hold verbatim on every platform, with nothing for us to
17+
# maintain.
18+
opencode.url = "github:anomalyco/opencode";
1819
opencode-nvim = {
1920
url = "github:NickvanDyke/opencode.nvim";
2021
flake = false;

0 commit comments

Comments
 (0)