4 commits

Author	SHA1	Message	Date
John Ericson	bec3c5cfcd	JSON for Hash now has to be Base16 ... Fix #14532. As discussed on the call today: 1. We'll stick with `format = "base16"` and `hash = "<hash>"`, not do `base16 = "<hash>"`, in order to be forward compatible with supporting more versioning formats. The motivation we discussed for someday *possibly* doing this is making it easier to write very slap-dash lang2nix tools that create (not consume) derivations with dynamic derivations. 2. We will remove support for non-base16 (and make that the default, not base64) in `Hash`, so this is strictly forward contingency, *not* yet something we support. (And also not something we have concrete plans to start supporting.)	2025-12-03 16:08:05 -05:00
John Ericson	4f1c8f62c3	Futher cleans up store object info JSON v2 ... Since we haven't released v2 yet (2.32 has v1) we can just update this in-place and avoid version churn. Note that as a nice side effect of using the standard `Hash` JSON impl, we don't neeed this `hashFormat` parameter anymore.	2025-11-06 23:28:56 -05:00
John Ericson	9c04c629e5	UnkeyedValidPathInfo::fromJSON Remove support for older version ... It turns out this code path is only used for unit tests (to ensure our JSON formats are possible to parse by other code, elsewhere). No user-facing functionality consumes this format. Therefore, let's drop the old version parsing support.	2025-11-06 19:27:31 -05:00
John Ericson	8cc3ede0fa	Add change-log entry for derivation format changes	2025-11-06 15:19:44 -05:00