Whenever I update an input in a flake.nix without actually updating the flake.lock the compat expression uses the input as specified in the lockfile. I think for consistency reasons it should fail during eval. Otherwise this might lead to an inconsistent state as users might forget to update the lockfile while the build succeeds.
Whenever I update an input in a
flake.nixwithout actually updating theflake.lockthe compat expression uses the input as specified in the lockfile. I think for consistency reasons it should fail during eval. Otherwise this might lead to an inconsistent state as users might forget to update the lockfile while the build succeeds.