Skip to content

Nix checks do not run on v2 pull requests #52123

Closed

Description

@jerome-benoit

Description

.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

  1. Open .github/workflows/nix-eval.yml lines 4-8.
  2. 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.

Activity

  1. github-actions commented on Sep 29, 2026

    @github-actions
    Contributor

    This issue doesn't fully meet our contributing guidelines.

    What needs to be fixed:

    • 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.

  2. 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
  3. github-actions commented on Sep 29, 2026

    @github-actions
    Contributor

    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.

  4. github-actions commented on Sep 29, 2026

    @github-actions
    Contributor

    Thanks for updating the issue with reproduction details and system information!

  5. jerome-benoit commented on Oct 2, 2026

    @jerome-benoit
    ContributorAuthor

    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.

  6. jerome-benoit commented on Oct 2, 2026

    @jerome-benoit
    ContributorAuthor

    Follow-up: the remaining gap from the closing comment is now tracked on its own — #52863.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions