yazi-unwrapped: 25.2.11 -> 25.2.26

[FlameFlag]

Breaking Changes

• separator_open and separator_close have been replaced with the new sep_left and sep_right. feat!: allow different separators to be applied individually to the left and right sides of the status bar sxyazi/yazi#2313
• The [completion] component has been renamed to [cmp]. feat!: allow to specify layer for keymap commands sxyazi/yazi#2399

Things done

Changelog: https://github.com/sxyazi/yazi/releases/tag/v25.2.26
Diff: sxyazi/yazi@v25.2.11...v25.2.26

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[ddogfoodd]

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 385283

---

x86_64-linux

✅ 2 packages built:

• yazi
• yazi-unwrapped

[ddogfoodd]

does the env.VERGEN_BUILD_DATE in line 44 require an update as well?

Other than that, builds and works fine for me on x86_64-linux, thanks

[FlameFlag]

does the env.VERGEN_BUILD_DATE in line 44 require an update as well?

Yeap you're right

[uncenter]

does the env.VERGEN_BUILD_DATE in line 44 require an update as well?

Yeap you're right

Fwiw the update script should be handling this? Might be better to use that in the future :)

[uncenter]

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 385283

---

aarch64-darwin

✅ 2 packages built:

• yazi
• yazi-unwrapped

[eljamm]

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 385283

---

x86_64-linux

✅ 2 packages built:

• yazi
• yazi-unwrapped

---

aarch64-linux

✅ 2 packages built:

• yazi
• yazi-unwrapped

---

x86_64-darwin

✅ 2 packages built:

• yazi
• yazi-unwrapped

---

aarch64-darwin

✅ 2 packages built:

• yazi
• yazi-unwrapped

[ddogfoodd]

Fwiw the update script should be handling this? Might be better to use that in the future :)

Thanks, good to know. Can one just run that or do we have to wait for the bot? Just asking in case there is an important bugfix or change in one release, so that people might not want to wait.

[uncenter]

Can one just run that or do we have to wait for the bot?

One can run nix run nixpkgs#nix-update -- yazi-unwrapped -u, but it actually seems like the update script is running into a bit of a jam at the moment.

Update script error

Crashing on this part:

++ nix-prefetch '{ sha256 }: (import /Users/uncenter/Dev/Forks/nixpkgs {}).yazi-unwrapped.cargoDeps.overrideAttrs (_: { outputHash = sha256; })'
error:
       … while calling the 'zipAttrsWith' builtin
         at /nix/store/4yng3wz3ri8q2g64aysa72j1n3dsa0i2-source/lib/attrsets.nix:1578:8:
         1577|       );
         1578|     in f [] [rhs lhs];
             |        ^
         1579|

       … while evaluating a branch condition
         at /nix/store/4yng3wz3ri8q2g64aysa72j1n3dsa0i2-source/lib/attrsets.nix:1352:5:
         1351|     as:
         1352|     if cond then as else {};
             |     ^
         1353|

       (stack trace truncated; use '--show-trace' to show the full, detailed trace)

       error: expected a set but found null: null
+ cargoHash=

Last time the update script was updated was before useFetchCargoVendor was enabled, maybe that is messing with it?

[FlameFlag]

Fwiw the update script should be handling this? Might be better to use that in the future :)

I initially tried to use the script with nix-shell ./maintainers/scripts/update.nix --argstr package yazi-unwrapped --argstr skip-prompt true, but I ran into the same issue as described in #385283 (comment), so I did the update manually

[eljamm]

Yea, the update script silently broke a while ago I guess, but I've been working on fixing it in #385409.

[XYenon]

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 385283

---

x86_64-linux

✅ 2 packages built:

• yazi
• yazi-unwrapped

[uncenter]

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 385283

---

aarch64-darwin

✅ 2 packages built:

• yazi
• yazi-unwrapped