Publish to crates.io
What is the feature you would like to see?
It will benefit this project's visibility to post to crates.io even if the template is rarely used as a Rust dependency. Therefore this should be done for the 1st deliverable.
Contribution Guidelines
- [X] I agree to follow this project's Contribution Guidelines
@ozgunozerk Is this pending something? If so, we should move it to backlog or next sprint and tag it as on hold
@orangelash this is blocked by #70 (which is blocked by an external issue. I contributed to that repo for solving the relevant issue).
We can publish this repo with manual efforts to github and crates.io, but it will be better to have this process automated. Imo, having the release in crates.io would be good, but is not a major concern. Hence, I'm inclined towards tagging this issue as on hold or blocked, and implement the automated releases when the relevant issues are unblocked.
I'm closing the milestone and moving this back to the backlog and setting the right label. We can discuss to which milestone we should associate it.