statix: 0-unstable-2026-05-14 -> 0.5.8-unstable-2026-05-26

[r-ryantm]

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.

meta.description for statix is: Lints and suggestions for the nix programming language

meta.homepage for statix is: https://github.com/molybdenumsoftware/statix

Updates performed

• Ran passthru.UpdateScript

To inspect upstream changes

• Compare changes on GitHub

Impact

Checks done

---

• built on NixOS
• The tests defined in passthru.tests, if any, passed
• found 0.5.8-unstable-2026-05-26 with grep in /nix/store/7n58grcqisqp64067qz6pvnqq2wzlkn4-statix-0.5.8-unstable-2026-05-26
• found 0.5.8-unstable-2026-05-26 in filename of file in /nix/store/7n58grcqisqp64067qz6pvnqq2wzlkn4-statix-0.5.8-unstable-2026-05-26

---

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

statix
vimPlugins.statix

Instructions to test this update (click to expand)

---

Either download from the cache:

nix-store -r /nix/store/7n58grcqisqp64067qz6pvnqq2wzlkn4-statix-0.5.8-unstable-2026-05-26 \
  --option binary-caches 'https://cache.nixos.org/ https://nixpkgs-update-cache.nix-community.org/' \
  --option trusted-public-keys '
  nixpkgs-update-cache.nix-community.org-1:U8d6wiQecHUPJFSqHN9GSSmNkmdiFW7GW7WNAnHW0SM=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The nixpkgs-update cache is only trusted for this store-path realization.)
For the cached download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.

Or, build yourself:

nix-build -A statix https://github.com/r-ryantm/nixpkgs/archive/159b2f1cfdbb49592ae315f0ca2c1fbef7f1ef61.tar.gz

Or:

nix build github:r-ryantm/nixpkgs/159b2f1cfdbb49592ae315f0ca2c1fbef7f1ef61#statix

After you've downloaded or built it, look at the files and if there are any, run the binaries:

ls -la /nix/store/7n58grcqisqp64067qz6pvnqq2wzlkn4-statix-0.5.8-unstable-2026-05-26
ls -la /nix/store/7n58grcqisqp64067qz6pvnqq2wzlkn4-statix-0.5.8-unstable-2026-05-26/bin

---

Pre-merge build results

We have automatically built all packages that will get rebuilt due to
this change.

This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review --extra-nixpkgs-config '{ allowBroken = false; }'
Commit: 159b2f1cfdbb49592ae315f0ca2c1fbef7f1ef61

---

x86_64-linux

✅ 2 packages built:

• vimPlugins.statix
• statix

---

Maintainer pings

cc @mightyiam @oppiliappan @JarvisCraft for testing.

Tip

As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

[mightyiam]

Is this due to #454333? Doesn't look like this should happen.

[h0nIg]

I dont think so, do you have a concrete log? Apparently 0.5.8 is the last released tag

[mightyiam]

I think it's this:
Mic92/nix-update#597

So we just wait it out, or do we close this one or what?

[JarvisCraft]

Still suggesting that you stick to stricter SemVer-tag versioning: it does not break your idea of always-stable master, but simplifies changes tracking which is especially important given that you've already had some observable breaking changes such as this one: cachix/git-hooks.nix#715

[mightyiam]

Hrm... sorry about that. From memory, I'm not sure whether that change was committed with the awareness that it is breaking.

statix needs more tests.

I'm not sure how semVer would have helped you in that situation, whether the version bump was major or not. You'd still have a breaking change to contend with.