zx: 7.2.3 -> 8.1.2

[jlbribeiro]

Description of changes

Fixes #309047.
Changes maintainer to @jlbribeiro, following this comment by the current maintainer.

Given zx popularity and its usage as a shell scripting language, I assume it might be worth linking the 8.0.0 release changelog in the next NixOS release's notes.

edit: As we're currently in feature freeze, I'm turning this PR into a draft, and will be updating the next release notes only when that document is created.

Diff: google/zx@7.2.3...8.1.2

Changelog:

• https://github.com/google/zx/releases/tag/8.0.0
• https://github.com/google/zx/releases/tag/8.0.1
• https://github.com/google/zx/releases/tag/8.0.2
• https://github.com/google/zx/releases/tag/8.1.0
• https://github.com/google/zx/releases/tag/8.1.1
• https://github.com/google/zx/releases/tag/8.1.2

Maintainer: @hlolli (currently), to become @jlbribeiro after merge

Things done

• 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/)
• 24.11 Release Notes (or backporting 23.11 and 24.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.

[kirillrdy]

@jlbribeiro there is currently breaking change restriction to all branches

as per definition of breaking change #303285

Breaking change

A change that is likely to break downstream consumers

I know it's a leaf package, but unless someone says otherwise, this will have to wait for after 24.05 release

[jlbribeiro]

@kirillrdy That makes total sense, will have to wait then. This made me re-read the schedule and fully grasp the release cycle.
If I fully understood, I'll have to move the release notes' update to the future 24.?? (not 24.05) release notes, correct?
(first time I noticed there's a release-YY.mm and nixos-YY.mm, was only aware of the latter)

(and again, thank you for the review + direction steering)

[getchoo]

renewing my approval, but as mentioned above we should wait until 24.05

[jlbribeiro]

renewing my approval, but as mentioned above we should wait until 24.05

@getchoo Thank you.

Can you confirm, however, that this should not be merged as-is after 24.05 is released, given it would modify the wrong release notes? (I'm validating whether I understood the release cycle "rules")
Putting in in another way: did I understand correctly this package will not and must not reach the nixos-24.05, not even via a backport (as it would introduce breaking changes)? Just ensuring this doesn't get merged by mistake, given it's already approved. (couldn't find an appropriate label for this situation)

[kirillrdy]

will not and must not reach the nixos-24.05, not even via a backport (as it would introduce breaking changes)

correct

Just ensuring this doesn't get merged by mistake

set PR to draft