Skip to content

build(nix): take lefthook from nixpkgs-unstable - #18

Merged
furedea merged 1 commit into
mainfrom
build/lefthook-from-unstable
Oct 18, 2026
Merged

furedea merged 1 commit into
mainfrom
build/lefthook-from-unstable

Conversation

@furedea-agent

@furedea-agent furedea-agent Bot commented Oct 17, 2026

Copy link
Copy Markdown
Contributor

What

  • Add a nixpkgs-unstable input to flake.nix and take only lefthook from it in the devShell.
    Every other package stays on nixpkgs-25.11-darwin.
  • flake.lock only gains the new nixpkgs-unstable entry; the existing nixpkgs lock is unchanged.

Why

The devShell's lefthook came from nixpkgs 25.11 (1.13.6). lefthook before 2.1.6 runs hook commands
under a pty, which the agent sandbox denies, so commits made inside nix develop failed in their hooks.
This mirrors the fix already in furedea/dotfiles.

Verification

  • nix develop -c lefthook version → 2.1.15
  • nix flake check → passes
  • nixfmt --check, statix check ., deadnix --fail . → pass
  • The commit was made via nix develop -c git commit inside the agent sandbox with hooks enabled
    (no LEFTHOOK=0 / --no-verify): pre-commit (nixfmt, statix, deadnix, ls-lint) and commit-msg
    (commitlint) all passed under lefthook v2.1.15.

Refs furedea/dotfiles#207

🤖 Generated with Claude Code

lefthook before 2.1.6 runs hook commands under a pty, which agent
sandboxes deny, so commits made inside the devShell failed in their
hooks. Take only lefthook from a new nixpkgs-unstable input and keep
every other package on nixpkgs 25.11.

Refs furedea/dotfiles#207

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@furedea
furedea merged commit 55f432b into main Oct 18, 2026
13 checks passed
@furedea
furedea deleted the build/lefthook-from-unstable branch October 18, 2026 08:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant