Some rought spots publishing 0.2.0 with @porcuquine today:
- check the cargo release version, folks don’t update this one frequently
- the Makefile publishes all tags, that’s not good if the operator’s local tags include those form a remote of the forked project,
- the packages are interdependent, so we need to instruct cargo-release on the dependency,
- and we probably need some massaging with cargo-release so that the path dependency from bellpepper-core to bellpepper doesn’t prevent the operator from publishing.
Some rought spots publishing 0.2.0 with @porcuquine today: