You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we start releasing the subtensor workspace to crates.io it would dramatically simplify the user experience of running a node (could even get to cargo install subtensor level potentially), but I see this as a side-mission / goal, the real objective here would be getting rust docs released to docs.rs/lib.rs/etc so when people google subtensor-related things they actually come up with up-to-date docs.
AC:
consolidate workspace so it is crates.io-friendly, ensure globally unique crate names, etc
set up a secure crates.io account we can use for releases, get a key for pushing to it added to CI
publish to crates.io (requires a github action / script especially since crates need to be published in a very particular order)
ability to publish to crates.io automatically as part of gh action release process
ability to spin up a new node via cargo install? or something we don't care about?
The text was updated successfully, but these errors were encountered:
If we start releasing the
subtensor
workspace to crates.ioit would dramatically simplify the user experience of running a node (could even get tobe getting rust docs released to docs.rs/lib.rs/etc so when people google subtensor-related things they actually come up with up-to-date docs.cargo install subtensor
level potentially), but I see this as a side-mission / goal, the real objective here wouldAC:
ability to spin up a new node viacargo install
? or something we don't care about?The text was updated successfully, but these errors were encountered: