Move to a tagged release of synedrion, not a branch with a fix
#509
Comments
6 tasks
This was referenced Nov 23, 2023
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the
server,kvdbandentropy-protocolcrates depend on a branch of synedrion containing a fix.Why is this issue relevant?
We want to depend on a tagged release. See #414 (comment)
What steps are required to resolve this?
As soon as a tagged version of synedrion containing the fix is up, move to it.
Does this change the spec? HTTP, extrinsic, or storage? Is it breaking? Clearly describe the new interface.
Not sure
The text was updated successfully, but these errors were encountered: