Modifying root using tuf-on-ci-delegate leads to also creating a copy of the file in root_history/.
It seems this does not happen when create-signing-event creates a new version of root but should. This is not critical as the first signing will include the missing file... but it creates commits that are a bit unobvious.
I think this just requires CIRepository.close() to handle this special case: after writing the actual file, also write f"root_history/{version}.{role}.json".
Modifying root using tuf-on-ci-delegate leads to also creating a copy of the file in root_history/. It seems this does not happen when create-signing-event creates a new version of root but should. This is not critical as the first signing will include the missing file... but it creates commits that are a bit unobvious.
I think this just requires
CIRepository.close()to handle this special case: after writing the actual file, also writef"root_history/{version}.{role}.json".