Downstream consumer here. cgroups-rs 0.5.0 (Nov 2025) still pins nix = "0.25.0" (April 2022). The nix crate has had six breaking releases since then, currently at 0.31.3.
The pin forces downstream workspaces that use a newer nix to ship two majors of nix plus the transitive duplicates (bitflags 1.x vs 2.x, cfg_aliases 0.1 vs 0.2).
The feature set used here (event, fs, process) covers nix modules with API churn (notably the I/O-safety reorg in 0.30 that switched many APIs to OwnedFd/BorrowedFd) but no large semantic changes.
Is there a known blocker to bumping, or would a PR be welcome?
Downstream consumer here. cgroups-rs 0.5.0 (Nov 2025) still pins
nix = "0.25.0"(April 2022). The nix crate has had six breaking releases since then, currently at 0.31.3.The pin forces downstream workspaces that use a newer nix to ship two majors of nix plus the transitive duplicates (bitflags 1.x vs 2.x, cfg_aliases 0.1 vs 0.2).
The feature set used here (
event,fs,process) covers nix modules with API churn (notably the I/O-safety reorg in 0.30 that switched many APIs toOwnedFd/BorrowedFd) but no large semantic changes.Is there a known blocker to bumping, or would a PR be welcome?