Open thobson88 opened 5 months ago
Remaining tasks for crates.io:
cargo build
is broken by the new [package]
section in top-level Cargo.toml)See documentation guide.
TODO:
UPDATE: We have a major obstacle because all dependencies must themselves be published on crates.io, which is a problem for us because Trustchain depends on our forks of third party repositories (specifically SSI and RSS).
This would mean publishing our forks of those repos before publishing Trustchain, which seems daft.
To get the API docs online (which was part of the motivation for publishing), I'm going to try to build them into the new mkdocs site on GitHub pages #173.
Additional discussion on crates.io
and forks.
Obstacle overcome! See #179 and PR #180.
Next step is to check doc comments and then publish from the publish
branch.
Adding some additional modifications that might be worthwhile to include in this release:
crates/
path (e.g. ssi and polars). I think it probably makes sense to keep the overall trustchain
package (currently re-exports of the workspace member crates) as a package at the workspace level rather than a member..cargo/config.toml
to return warnings:
[build]
rustflags = ["-Wmissing-docs"]
Use GitHub account:
trustchain-devs
with emailtrustchain.devs@gmail.com
.(Note: this is a new gmail account, not to be confused with
trustchaindevstest@gmail.com
used for the demo.)TODO: decide how to publish the whole workspace, given that it's not supported by default (see here).
There's a crate for workspace publishing which looks promising, but to get the right name for the whole workspace I think we'll need to add
name = trustchain
to the top-levelCargo.toml
.That means making changes after the
v0.1.0
tagged commit, which is annoying.Alternatively we could just do some merging, update the metadata in
Cargo.toml
, tag the new release asv0.2.0
and publish that instead.