[main] Update flake.lock & generated files #4249
Conversation
f4a550d to
b089bc3
Compare
This comment was marked as resolved.
This comment was marked as resolved.
0e2fee3 to
c6f6e39
Compare
17d21b3 to
9cc08b4
Compare
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
1de46d2 to
5df2783
Compare
| buf_lint = pkgs.buf; | ||
| clazy = states.linuxOnly pkgs.clazy; | ||
| clangtidy = pkgs."clang-tools"; | ||
| clj-kondo = states.linuxOnly pkgs.clj-kondo; |
There was a problem hiding this comment.
Q: Should we simplify this whole thing and migrate from us maintaining platform checks to just use lib.meta.availableOn and returning a message automatically when it's no longer supported? Or do we want to keep maintaining this?
There was a problem hiding this comment.
alright, I think you're right about that.
There was a problem hiding this comment.
unless I'm thinking of another part of our codebase?
Looking closer, as this is plugin-specific it feels like these exclusions shouldn't be part of the user-facing module. Instead, they feel like things that should only be in our tests.
The problem with having hard-coded disablements in the user-facing module is that the user may be using a different nixpkgs or an override of the package.
(this is the kinda thing too big to address in an update bump PR, though)
There was a problem hiding this comment.
The problem with having hard-coded disablements in the user-facing module is that the user may be using a different nixpkgs or an override of the package.
I agree. I thought about that previously when a package was fixed and I had to wait for a nixvim bump to get it working again.
be9df71 to
5ccc0a7
Compare
|
Hmm we seem to have a lot affected by GHC atm might need to wait and see if it gets cached soon. |
61cc6d6 to
29f335c
Compare
flake.lock updates:
• Updated input 'flake-parts':
'github:hercules-ci/flake-parts/3107b77cd68437b9a76194f0f7f9c55f2329ca5b?narHash=sha256-91qqW8lhL7TLwgQWijoGBbiD4t7/q75KTi8NxjVmSmA%3D' (2026-04-01)
→ 'github:hercules-ci/flake-parts/5250617bffd85403b14dbf43c3870e7f255d2c16?narHash=sha256-EPIFsulyon7Z1vLQq5Fk64GR8L7cQsT%2BIPhcsukVbgk%3D' (2026-05-01)
• Updated input 'nixpkgs':
'github:NixOS/nixpkgs/566acc07c54dc807f91625bb286cb9b321b5f42a?narHash=sha256-psVTpH6PK3q1htMJpmdz1hLF5pQgEshu7gQWgKO6t6Y%3D' (2026-04-15)
→ 'github:NixOS/nixpkgs/c6d65881c5624c9cae5ea6cedef24699b0c0a4c0?narHash=sha256-WNGcmeOZ8Tr9dq6ztCspYbzWFswr2mPebM9LpsfGxPk%3D' (2026-05-01)
flake/dev/flake.lock updates:
• Updated input 'dev-nixpkgs':
'github:NixOS/nixpkgs/566acc07c54dc807f91625bb286cb9b321b5f42a?narHash=sha256-psVTpH6PK3q1htMJpmdz1hLF5pQgEshu7gQWgKO6t6Y%3D' (2026-04-15)
→ 'github:NixOS/nixpkgs/c6d65881c5624c9cae5ea6cedef24699b0c0a4c0?narHash=sha256-WNGcmeOZ8Tr9dq6ztCspYbzWFswr2mPebM9LpsfGxPk%3D' (2026-05-01)
• Updated input 'git-hooks':
'github:cachix/git-hooks.nix/580633fa3fe5fc0379905986543fd7495481913d?narHash=sha256-8Psjt%2BTWvE4thRKktJsXfR6PA/fWWsZ04DVaY6PUhr4%3D' (2026-04-07)
→ 'github:cachix/git-hooks.nix/3cfd774b0a530725a077e17354fbdb87ea1c4aad?narHash=sha256-PcRvlWayisPSjd0UcRQbhG8Oqw78AcPE6x872cPRHN8%3D' (2026-04-21)
• Updated input 'home-manager':
'github:nix-community/home-manager/d401492e2acd4fea42f7705a3c266cea739c9c36?narHash=sha256-iAJIzHngGZeLIkjzuuWI6VBsYJ1n89a/Esq0m8R1vjs%3D' (2026-04-16)
→ 'github:nix-community/home-manager/b9311028044a9e9b2cf27db15ef0a87d464e212d?narHash=sha256-CYpc%2Bmk28rmcQWGygeM8CA%2BZ8SZYy8BOyQtiW18spao%3D' (2026-05-03)
• Updated input 'nix-darwin':
'github:lnl7/nix-darwin/06648f4902343228ce2de79f291dd5a58ee12146?narHash=sha256-KM2WYj6EA7M/FVZVCl3rqWY%2BTFV5QzSyyGE2gQxeODU%3D' (2026-04-01)
→ 'github:lnl7/nix-darwin/8c62fba0854ba15c8917aed18894dbccb48a3777?narHash=sha256-8wURyQMdDkGUarSTKOGdCuFfYiwa3HbzwscUfn3STDE%3D' (2026-05-03)
- Updated efmls-configs-sources.json - Updated lint-linters.json
Upstream changed behavior.
|
@khaneliman good for review. CI is green. |
Root lockfile
Dev lockfile
Generated files
This PR was most recently updated by workflow run 25279375703.
You can re-run the update by going to the workflow's page or by using the
ghcommand:If needed, you can also specify workflow inputs on the command line, using the
-F --field,-f --raw-field, or--jsonflags.See
gh workflow run --help.