You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
.github/workflows/nix-eval.yml triggers on dev only, while v2 is the default base branch. The job also only evaluates drvPath and never builds, and a stale fixed-output hash is not an evaluation error.
Result on v2: nix/electron.nix kept electron 42.10.1's hashes across two electron bumps (2026-09-21 and 2026-09-29), and the desktop build stayed broken for eight days before #50408 reported it.
Plugins
None
OpenCode version
Affected source: 2.0.19+c977050030
Steps to reproduce
Open .github/workflows/nix-eval.yml lines 4-8.
Open a pull request targeting v2: no nix-eval run is triggered.
Screenshot and/or share link
Not applicable.
Operating System
Linux x86_64
Terminal
Not applicable, this is a workflow configuration issue.
The issue doesn't use one of the required issue templates. Please use the Bug Report template, including its required Description field, and add brief reproduction steps for how the current workflow misses the desktop build failure.
Please edit this issue to address the above within 2 hours, or it will be automatically closed.
This issue might be a duplicate of existing issues. Please check:
#11755: A Nix desktop build failure that CI did not catch; the report suggests re-enabling a Nix desktop workflow.
#15400: A Nix build failure noting that nix-eval only evaluates derivations and does not run a build.
If you believe this was flagged incorrectly, please let a maintainer know.
changed the title [-]nix-eval.yml only runs on dev, so v2 packaging breakage goes unnoticed[/-][+]Nix checks do not run on v2 pull requests[/+]on Sep 29, 2026
Thanks for adding context and reproduction steps. This issue still doesn't appear to use one of the required issue templates: please update it with the Bug Report template and include its required Description field with the issue details. The reproduction context you've added can remain.
Fixed upstream by #52143 (ec541abbcd), which added v2 to the nix-eval triggers:
on:
push:
branches: [dev, v2]pull_request:
branches: [dev, v2]
Combined with #52129 (c34d09fe97), which unblocked flake evaluation on nixpkgs 26.11 and dropped the stale x86_64-darwin target, both defects reported here are addressed on v2.
Remaining gap
One point from this report is still open, tracked here for visibility rather than silently: nix-eval only evaluates drvPath and never builds, and nix-hashes.yml still has no pull_request trigger, so a stale fixed-output hash on nix/hashes.json is only caught after merge to v2. That is a separate change from the trigger fix above.
Activity
github-actions commentedon Sep 29, 2026
This issue doesn't fully meet our contributing guidelines.
What needs to be fixed:
Please edit this issue to address the above within 2 hours, or it will be automatically closed.
This issue might be a duplicate of existing issues. Please check:
If you believe this was flagged incorrectly, please let a maintainer know.
[-]nix-eval.yml only runs on dev, so v2 packaging breakage goes unnoticed[/-][+]Nix checks do not run on v2 pull requests[/+]github-actions commentedon Sep 29, 2026
Thanks for adding context and reproduction steps. This issue still doesn't appear to use one of the required issue templates: please update it with the Bug Report template and include its required Description field with the issue details. The reproduction context you've added can remain.
github-actions commentedon Sep 29, 2026
Thanks for updating the issue with reproduction details and system information!
jerome-benoit commentedon Oct 2, 2026
Fixed upstream by #52143 (
ec541abbcd), which addedv2to thenix-evaltriggers:Combined with #52129 (
c34d09fe97), which unblocked flake evaluation on nixpkgs 26.11 and dropped the stalex86_64-darwintarget, both defects reported here are addressed onv2.Remaining gap
One point from this report is still open, tracked here for visibility rather than silently:
nix-evalonly evaluatesdrvPathand never builds, andnix-hashes.ymlstill has nopull_requesttrigger, so a stale fixed-output hash onnix/hashes.jsonis only caught after merge tov2. That is a separate change from the trigger fix above.jerome-benoit commentedon Oct 2, 2026
Follow-up: the remaining gap from the closing comment is now tracked on its own — #52863.