Generate index db for nixpkgs stable branch

[azuwis]

For now, nixos-25.05 branch for linux, nixpkgs-25.05-darwin branch for darwin.

Tested in fork https://github.com/azuwis/nix-index-database

Release https://github.com/azuwis/nix-index-database/releases/tag/2025-10-24-032934

Action https://github.com/azuwis/nix-index-database/actions/runs/18768693418

Generated commit azuwis@0ce453f

See also #127 (comment)

[Mic92]

can you look at the ci error? also we should now switch to 25.11

[azuwis]

Bump stable branch to 25.11.

As for the CI error, I have no idea how Garnix works, but I guess that's because generated.nix don't have updated content like azuwis@0ce453f yet.

[azuwis]

@Mic92 Anything left?

The CI errors should be gone once this PR get merged and workflow triggered. I can not update generated.nix in this PR, it should be updated by the workflow with the generated nix-index database assets.

[HigherOrderLogic]

Seems like the auto-merge is not working because of CI fails?

[azuwis]

I've investigated the Garnix CI error regarding packages.x86_64-linux.nix-index-stable-database:

       error: attribute 'x86_64-linux-stable' missing
       at /nix/store/g4blx8rlszy7p3qkxyd013fdy2ilw9jz-source/default.nix:28:14:
           27|       url = generated.url + pkgs.stdenv.system + "-stable";
           28|       hash = generated.hashes."${pkgs.stdenv.system}-stable";
             |              ^
           29|     }).overrideAttrs

Root Cause:

The build fails because it looks for the x86_64-linux-stable attribute in generated.nix, which doesn't exist yet. This file is updated by the scheduled workflow. These attributes will only appear once the changes to the workflow are merged and the scheduler runs.

Now the auto-merge is blocked by the CI error, this is a chicken-and-egg problem, I think we can:

• Merge as-is: Acknowledge the CI failure as a known side-effect that will self-correct once the first scheduled run completes post-merge.
• Two-step merge: Revert the changes to default.nix in this PR to get a green CI. Once merged, submit a follow-up PR to re-enable the default.nix changes.

What do you think, @Mic92 ? (Option 1 seems more efficient if you're okay with a temporary red light).