The last couple of automated releases didn't have any content change, but were triggered by the sorting order of abi_registry.json changing. Enforce a stable ordering by first sorting by ABI (current behavior) and then also sort by version (new behavior).
There should be no user facing changes as a result of this PR - the public API does its own sorting, this only affects the on-disk sorting of abi_registry.json as that's what causes new releases to trigger, when that changes.
Considered changing the sorting to be only by version, but that resulted in too much change to abi_registry.json. This change results in a minimal diff that is easy to verify by hand.
The last couple of automated releases didn't have any content change, but were triggered by the sorting order of
abi_registry.json
changing. Enforce a stable ordering by first sorting by ABI (current behavior) and then also sort by version (new behavior).There should be no user facing changes as a result of this PR - the public API does its own sorting, this only affects the on-disk sorting of
abi_registry.json
as that's what causes new releases to trigger, when that changes.Considered changing the sorting to be only by version, but that resulted in too much change to
abi_registry.json
. This change results in a minimal diff that is easy to verify by hand.