vulkan-headers,vulkan-loader: 1.3.283.0 -> 1.3.289

[fgaz]

Description of changes

Prerequisite for packaging vulkan-enabled skia 124, which is itself a prerequisite for updating ladybird, which I maintain

edit: this wasn't actually needed. I have no idea why I thought it was, maybe I confused a different vulkan error

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.

[AndersonTorres]

Have you considered migrating them to by-name?

[fgaz]

Have you considered migrating them to by-name?

Won't the automatic migration take care of that? I thought we weren't supposed to migrate manually.

[JohnRTitor]

Won't the automatic migration take care of that? I thought we weren't supposed to migrate manually.

Technically it is allowed to migrate them manually, but only during update PRs or fixing other stuff.

[AndersonTorres]

Won't the automatic migration take care of that? I thought we weren't supposed to migrate manually.

The manual migration is allowed in a PR in which another modification takes place.
Updates and refactors are the best opportunity for this.
(This can be useful, since the recent merge bot can merge updates from Ryanbot inside by-name hierarchy.)

Besides it, the mere migration of files is not recommended.

[Ralith]

Usually we try to keep the whole Vulkan SDK family in sync, e.g. #281591

[fgaz]

I was just informed about the vulkan version tagging scheme. This PR updates vulkan to a regular release, not a SDK. Is that fine or should we wait?

[AndersonTorres]

Given the mass-rebuild, I would wait.

[fgaz]

Makes sense, closing.