We currently have release automation of the following form: whenever the hegel-core CI job publishes a new version, it sends a dispatch event to the library repositories (hegel-rust, hegel-go, etc). The corresponding CI job in those repositories reads the hegel-core changelog and.
We should improve the library CI jobs so that they look at the diff between the current and the new version for the PROTOCOL_VERSION marker, and bump it client-side if it changed. This might span multiple individual versions, which is why we can't just send this information in the dispatch payload.
We currently have release automation of the following form: whenever the hegel-core CI job publishes a new version, it sends a dispatch event to the library repositories (hegel-rust, hegel-go, etc). The corresponding CI job in those repositories reads the hegel-core changelog and.
We should improve the library CI jobs so that they look at the diff between the current and the new version for the
PROTOCOL_VERSIONmarker, and bump it client-side if it changed. This might span multiple individual versions, which is why we can't just send this information in the dispatch payload.