Releases: quorumcontrol/messages
Gossip protobuf types
v2.1.2: Hermetic builds & other fixes
Our build system should now be much more hermetic and consistent. Releasing this to make sure that's the version of the compiled code we're using everywhere.
v2.1.1: Update the generated code w/ v2.1.0 changes
In v2.1.0 we inadvertently updated only the protobuf code, not the generated JS and Go code. This release updates the generated code as well.
v1.1.1: Update the generated code w/ v1.1.0 changes
In v1.1.0 we inadvertently updated only the protobuf code, not the generated JS and Go code. This release updates the generated code as well.
v2.1.0: Add v2 prefix to protobuf types
This release adds a v2
prefix to the protobuf types defined in this repo. This allows safe interoperation of v2 messages with v1 in the same project.
v1.1.0: Remove v1 prefix from protobuf types
In retrospect the addition of v1 prefixes in v1.0.0 was the opposite of what we needed. Existing v1 code expects protobuf types without a prefix, so instead we're adding a v2 prefix in the v2.1.0 release so that new v2-using code can explicitly use those new names (and they can both coexist in the same projects when desired), but existing v1-using code can continue to use compatible un-prefixed type names.
v1 prefixed protobuf types
This allows using the old pre-v2 messages in the same codebase, which is helpful for translational tools across the two versions.
move go.mod to root of directory
Go assumes a root go.mod and this satisfies that go assumption.
Move v2 major version into a directory
We have a non-standard directory layout here, this attempts to solve a usage problem in other repos by putting the major version into a directory.
Conditions
This is moves the object definitions around to support our new conditions, allowing for small scripts on ChainTree ownership.