If it can't be made stable, `git archive` should specifically add random content (under a feature flag to be removed after a year or two) to so as to make the generated checksum completely unreliable and force users to adopt different workflows.
A story about a Golang program that had assumed map iteration was uniformly random but it’s not, which caused a load balancer to assign work unevenly:
https://dev.to/wallyqs/gos-map-iteration-order-is-not-that-r...
A graph of the map iteration order’s distribution showing that it’s not uniformly random:
There's a long shot between "not specified" and "uniformly random".
https://docs.python.org/3/reference/datamodel.html#object.__...
> Changed in version 3.3: Hash randomization is enabled by default.
But since Python 3.6 dicts keep the insertion order, so the order of iteration is deterministic again.