treewide: refactor rev = version to tag = version

[guylamar2006]

Refactor rev = version; to tag = version;

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/)
• Nixpkgs 25.11 Release Notes (or backporting 25.05 Nixpkgs Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
• NixOS 25.11 Release Notes (or backporting 25.05 NixOS Release notes)
  • (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, pkgs/README.md, maintainers/README.md and other contributing documentation in corresponding paths.

---

Add a 👍 reaction to pull requests you find important.

[guylamar2006]

nixpkgs-review result

Generated using nixpkgs-review-gha

Command: nixpkgs-review pr 422472

Logs: https://github.com/guylamar2006/nixpkgs-review-gha/actions/runs/16078781485

[wolfgangwalther]

Did you check each of the github repos to confirm that none of those actually point at a branch with the version name and not to a tag?

[wolfgangwalther]

Tested basic functionality of all binary files (usually in ./result/bin/)

You checked this box. Did you really test each package's binaries? Even considering that none of them were rebuilt?

[numinit]

This and #422131 are going to need a bit more. I currently cannot verify that this or the other change are correct. In general, changes to FODs have the potential of breaking things because the hash is used to cache the output.

Now, if there's a script you've got that changes each of these one at a time, and then makes sure the fetch works the same (think a Nix build command that uses --check, see https://nix.dev/manual/nix/2.25/advanced-topics/diff-hook) then it would be much easier for folks to verify. 🙂