Update nix depsSha256

[kubukoz]

No description provided.

[keynmol]

What's the smallest possible workflow that we can have that makes sure the nix installation works?
Can you run the flake locally?

I'm happy to approve random hash changes (which is already terrifying), but if I could have a little bit of confidence that stuff works for Nix folks I'd be less worried

[kubukoz]

A CI workflow is easy, what's harder is an auto-updater that'll let you not worry about it at all. A failing workflow would tell you what hash to use, but it'd fail on essentially every Scala Steward PR :/

If we can figure out an auto-updater, we can have Steward run an extra command that'll update the hash as well. Its PRs would have to be either

• batched (multiple libs per PR), or
• merged sequentially (merge PR 1, update PR 2 with main, wait for CI, merge, update PR 3...)
• merged in a merge queue

At the moment, even as a Nix user I'm not too mad about the hash changes. I just stay pinned to the last version where somebody updated the hash 😅 but it's not a scalable approach.

One thing we could do right off the bat is give users the ability to override the deps hash locally, so that they don't need a PR like this.

Another thing... if we have an auto-updater, we could have a scheduled workflow that runs it. That'd sort of circumvent the problem of "a series of lib updates merged in a sequence", giving the Nix build a sort of "eventually working" status.