Look into Release-plz #395
Description
Automate releases
Release-plz could help us releasing using merging.
There is a catch as we need a crate published and a server image pushed, but @adam-cattermole looked into it a bit and it should be feasible. Question is can we release the server w/o needing a crate pushed to crates.io?
Our server's build.rs
That would probably need to change. Mostly around the versioning being directly retrieved from Cargo.toml. We probably need to swap that out for a LIMITADOR_VERSION, that'd be set in our build.rs just as we do for the others.
That would need to check whether we're building from a git local repo (which doesn't happen always, e.g. if someone would be able to build and install through crates.io - tho not a thing as of now). If so, check if git tag --points-at HEAD points to a tag that matches v{CARGO_PKG_VERSION}. If so that's the version, otherwise it's v{CARGO_PKG_VERSION}-dev; as with Release-plz main would have CARGO_PKG_VERSION pointing to the next version to be released. We'd "just" would need to make sure this is tagged before building tho...