cmake: 3.31.3 -> 3.31.5

[MisileLab]

https://cmake.org/cmake/help/latest/release/3.31.html
https://gitlab.kitware.com/cmake/cmake/-/compare/v3.31.3...v3.31.5

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/)
• 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.

[paparodeo]

this needs to target staging

[MisileLab]

this needs to target staging

I think it can target staging-next because it's minor update and changelog says no changes to documented features or interfaces.

[paparodeo]

this needs to target staging

I think it can target staging-next because it's minor update and changelog says no changes to documented features or interfaces.

that is not sufficient. it will cause too many rebuilds. the staging-next cycle is nearing the end and this will cause a darwin stdenv rebuild and thus require another week of building just due to this change.

unless there are special circumstances, if a change can go into master it can go into staging-next otherwise it needs to target staging.

[MisileLab]

this needs to target staging

I think it can target staging-next because it's minor update and changelog says no changes to documented features or interfaces.

that is not sufficient. it will cause too many rebuilds. the staging-next cycle is nearing the end and this will cause a darwin stdenv rebuild and thus require another week of building just due to this change.

unless there are special circumstances, if a change can go into master it can go into staging-next otherwise it needs to target staging.

okay, I'll change targeted branch to staging.

[paparodeo]

https://gitlab.kitware.com/cmake/cmake/-/compare/v3.31.3...v3.31.4