flake.lock pinned to outdated nixpkgs rev causing build failure #8775

Closed
opened 2026-02-16 18:10:48 -05:00 by yindo · 4 comments
Owner

Originally created by @MBanucu on GitHub (Feb 7, 2026).

Originally assigned to: @rekram1-node on GitHub.

The flake.lock is pinned to nixpkgs rev 2f594d5af95d4fdac67fba60376ec11e482041cb (2026-01-14), which includes bun 1.3.6. However, the build script requires bun@^1.3.8, causing builds to fail with 'This script requires bun@^1.3.8, but you are using bun@1.3.6'.

The flake.lock was updated to this rev in commit f1df6f2d18 ('chore: update flake.lock (#9938)') on 2026-01-22.

The packageManager in package.json was updated to 'bun@1.3.8' in commit 898778daa9 ('chore: upgrade bun to 1.3.8 (#11892)') on 2026-02-06, making the script require bun 1.3.8+.

Please update the flake.lock to a newer nixpkgs rev that includes bun 1.3.8 or later. Running 'nix flake update' in the repo should fix this.

Originally created by @MBanucu on GitHub (Feb 7, 2026). Originally assigned to: @rekram1-node on GitHub. The flake.lock is pinned to nixpkgs rev 2f594d5af95d4fdac67fba60376ec11e482041cb (2026-01-14), which includes bun 1.3.6. However, the build script requires bun@^1.3.8, causing builds to fail with 'This script requires bun@^1.3.8, but you are using bun@1.3.6'. The flake.lock was updated to this rev in commit f1df6f2d18f1c19a67b1232f7e4c01fa91a9cb62 ('chore: update flake.lock (#9938)') on 2026-01-22. The packageManager in package.json was updated to 'bun@1.3.8' in commit 898778daa933a97a0e21270ab11b466bca634bc9 ('chore: upgrade bun to 1.3.8 (#11892)') on 2026-02-06, making the script require bun 1.3.8+. Please update the flake.lock to a newer nixpkgs rev that includes bun 1.3.8 or later. Running 'nix flake update' in the repo should fix this.
yindo added the nix label 2026-02-16 18:10:48 -05:00
yindo closed this issue 2026-02-16 18:10:49 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Feb 7, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #9583: Build failure: Bun version mismatch (expects 1.3.5, system has 1.3.6)
  • #8469: Relax bun version check to allow patch differences

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Feb 7, 2026): This issue might be a duplicate of existing issues. Please check: - #9583: Build failure: Bun version mismatch (expects 1.3.5, system has 1.3.6) - #8469: Relax bun version check to allow patch differences Feel free to ignore if none of these address your specific case.
Author
Owner

@MBanucu commented on GitHub (Feb 7, 2026):

This is auto generated and might not be accurate. The flake is broken, but the reason might not be it.

@MBanucu commented on GitHub (Feb 7, 2026): This is auto generated and might not be accurate. The flake is broken, but the reason might not be it.
Author
Owner

@MBanucu commented on GitHub (Feb 7, 2026):

The packageManager in package.json was updated to 'bun@1.3.8' in commit 898778d ('chore: upgrade bun to 1.3.8 (#11892)') on 2026-02-06, making the script require bun 1.3.8+.

Please update the flake.lock to a newer nixpkgs rev that includes bun 1.3.8 or later. Running 'nix flake update' in the repo should fix this.

Now it is more accurate. This is most probably the reason.

@MBanucu commented on GitHub (Feb 7, 2026): > The packageManager in package.json was updated to 'bun@1.3.8' in commit [898778d](https://github.com/anomalyco/opencode/commit/898778daa933a97a0e21270ab11b466bca634bc9) ('chore: upgrade bun to 1.3.8 ([#11892](https://github.com/anomalyco/opencode/pull/11892))') on 2026-02-06, making the script require bun 1.3.8+. > > Please update the flake.lock to a newer nixpkgs rev that includes bun 1.3.8 or later. Running 'nix flake update' in the repo should fix this. Now it is more accurate. This is most probably the reason.
Author
Owner

@MBanucu commented on GitHub (Feb 8, 2026):

#11919
Tested, fixed, good.

We don't have to automate anything. Doing everything manually has a good side: You learn a lot and the quality is assured.

@MBanucu commented on GitHub (Feb 8, 2026): #11919 Tested, fixed, good. We don't have to automate anything. Doing everything manually has a good side: You learn a lot and the quality is assured.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#8775