holochain request for lair-keystore updates to be in the changelog

I describe the full issue here, but holochain repo and releases would need to be the end place where lair-keystore changes are reported, when the lair-keystore version gets bumped. : https://github.com/holochain/lair/issues/113

Of particular importance to developers is whether or not the change breaks the keystore format, because then we need to facilitate end-users to abandon or migrate their existing keys to update to any new version of our software (if we, like Acorn, release the conductor ourselves as a built-in)

Jun 16 '23 12:06 Connoropolous

Thanks for raising this @Connoropolous, there is a similar issue about documenting compatibility here but Lair is not included in that so linking here because it clearly needs to be. I don't think we knew this was a breaking change for end users of hApps though so this is worse than just people not knowing what works with what. I will track this down.

The commit in Lair is here https://github.com/holochain/lair/commit/43be404da0fd9d57bf4429c44def405bd6490f61, the bump in Holochain happened here https://github.com/holochain/holochain/pull/2466 and the publish of that version happened here https://github.com/holochain/holochain/pull/2482.

@steveej @neonphog FYI, a topic for today's sync