Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
r-ryantm wants to merge 1 commit into
base: master
Choose a base branch
from
+4 −4
Open

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions pkgs/by-name/st/statix/package.nix
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,16 +8,16 @@

rustPlatform.buildRustPackage (finalAttrs: {
pname = "statix";
version = "0-unstable-2026-05-14";
version = "0.5.8-unstable-2026-05-26";
Copy link
Copy Markdown
Contributor

@mightyiam mightyiam May 27, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Copy Markdown
Contributor

@h0nIg h0nIg May 27, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Copy Markdown
Contributor

@mightyiam mightyiam May 27, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

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

Copy link
Copy Markdown
Contributor

@JarvisCraft JarvisCraft May 27, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Copy Markdown
Contributor

@mightyiam mightyiam May 28, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.


src = fetchFromGitHub {
owner = "molybdenumsoftware";
repo = "statix";
rev = "f0d256d60d9b9736b274a0edc0492be472318166";
hash = "sha256-dylteN19qQ/MclInQ+x4vf+rBGNIsaKWJ+WgiS0ZBjI=";
rev = "0aca60966fed04f832e80a5b2edaa54e2ca18a5e";
hash = "sha256-VhID6wpTRe6i8Cb3dcp/S4FJEq2iwExn75Wps9paAHI=";
};

cargoHash = "sha256-lODAnIGw8MncMT5xicWORSbCChn2HQXENsOStJYHepQ=";
cargoHash = "sha256-XqZlJsWp3RFOXMMB4dPXeVFiH+MFlxf5iPd2vVSKJEs=";

buildFeatures = lib.optional withJson "json";

Expand Down
Loading