chore: update flake.lock

[samlaf]

simply cloned the repo and ran nix flake update.

flake.lock hasn't been updated in 2+ years, it was still pinned to using cargo 1.63 or some very old version. Following the tutorial at https://docs.rs/prost-build/latest/prost_build/ didn't work because it would download the latest version of prost_build which requires cargo 1.71.

[caspermeijn]

I am not familiar with nix and I don't use it myself. Is this similar to dev containers (as in, you define the setup you need for development)?

I believe this has not been used by anyone for a long time. MSRV 1.64 was in August 2023 and MSRV 1.70 was in February 2024. Is it reasonable to remove flake.lock?

If we keep the setup, then it should be tested in CI so that it can't become outdated anymore. Maybe dependabot can help update it?

Alternatively, can this config be used instead dev containers? Then a single config is used in multiple places. https://github.com/devcontainers/features/tree/main/src/nix

[samlaf]

I am not familiar with nix and I don't use it myself. Is this similar to dev containers (as in, you define the setup you need for development)?

Nix is a full blown package manager, but its shell feature has a similar goal to dev containers yes. Although it runs natively so it doesn’t have the container overhead.

I believe this has not been used by anyone for a long time. MSRV 1.64 was in August 2023 and MSRV 1.70 was in February 2024. Is it reasonable to remove flake.lock?

That’s a good question it might work I’m not sure but the dependabot route would def be more canonical/rwproducible.

If we keep the setup, then it should be tested in CI so that it can't become outdated anymore. Maybe dependabot can help update it?

https://github.com/DeterminateSystems/update-flake-lock This looks like what you’d want.

Alternatively, can this config be used instead dev containers? Then a single config is used in multiple places. https://github.com/devcontainers/features/tree/main/src/nix

not sure what that repo is, but it looks like it installs nix to be used inside dev containers, I would guess similarly to how one would want to use nix inside a dockerfile to get a reproducible image build. I much prefer to not have to deal with dev containers, and just spin up the shell with nix develop github:tokio-rs/prost