[main] Update flake.lock & generated files

[nixvim-ci]

Root lockfile

Flake lock file updates:

• Updated input 'nixpkgs':
    'github:NixOS/nixpkgs/e0042dedfbc9134ef973f64e5c7f56a38cc5cc97?narHash=sha256-PsZAY3H0e/PBoDVn4fLwGEmeSwESj7SZPZ6CMfgbWFU%3D' (2025-05-27)
  → 'github:NixOS/nixpkgs/3d1f29646e4b57ed468d60f9d286cde23a8d1707?narHash=sha256-B3BsCRbc%2Bx/d0WiG1f%2BqfSLUy%2BoiIfih54kalWBi%2B/M%3D' (2025-05-28)

Dev lockfile

Flake lock file updates:

• Updated input 'dev-nixpkgs':
    'github:NixOS/nixpkgs/e0042dedfbc9134ef973f64e5c7f56a38cc5cc97?narHash=sha256-PsZAY3H0e/PBoDVn4fLwGEmeSwESj7SZPZ6CMfgbWFU%3D' (2025-05-27)
  → 'github:NixOS/nixpkgs/3d1f29646e4b57ed468d60f9d286cde23a8d1707?narHash=sha256-B3BsCRbc%2Bx/d0WiG1f%2BqfSLUy%2BoiIfih54kalWBi%2B/M%3D' (2025-05-28)
• Updated input 'home-manager':
    'github:nix-community/home-manager/f5b12be834874f7661db4ced969a621ab2d57971?narHash=sha256-7sCuihzsTRZemtbTXaFUoGJUfuQErhKEcL9v7HKIo1k%3D' (2025-05-28)
  → 'github:nix-community/home-manager/95c988cf08e9a5a8fe7cc275d5e3f24e9e87bd51?narHash=sha256-uGnudxMoQi2c8rpPoHXuQSm80NBqlOiNF4xdT3hhzLM%3D' (2025-05-29)

---

This PR was most recently updated by workflow run 15323620281.

You can re-run the update by going to the workflow's page or by using the gh command:

gh workflow run update.yml

If needed, you can also specify workflow inputs on the command line, using the -F --field, -f --raw-field, or --json flags.
See gh workflow run --help.

[MattSturgeon]

LGTM.

@GaetanLepage are there any disablements we can re-enable now?

[GaetanLepage]

LGTM.

@GaetanLepage are there any disablements we can re-enable now?

Nope, I don't think so.

[GaetanLepage]

@Mergifyio queue

[mergify]

queue

✅ The pull request has been merged automatically

The pull request has been merged automatically at a9e4507

[mergify]

This pull request, with head sha a9e45072d82374dd3f0d971795e7d7f99e5bc6c2, has been successfully merged with fast-forward by Mergify.

This pull request will be automatically closed by GitHub.

As soon as GitHub detects that the sha a9e45072d82374dd3f0d971795e7d7f99e5bc6c2 is part of the main branch, it will mark this pull request as merged.

It is possible for this pull request to remain open if this detection does not happen, this usually happens when a force-push is done on this branch update/main, this means GitHub will fail to detect the merge.