Operator has connected sentrix-labs GitHub to crates.io (trusted publishing OIDC). Plan the first batch of crates from this repo + parent sentrix-labs/sentrix workspace that get published.
Why
Third-party Rust devs can't cargo add sdk-rs today. Publishing makes the SDK discoverable + drop-in.
Candidate crates (leaf-first, dependency-free of non-published path deps)
- From this repo: top-level
sdk-rs once internal modules are stable
- From
sentrix-labs/sentrix: sentrix-primitives, sentrix-wallet, sentrix-rpc-types, sentrix-codec
Hard prerequisites
- Each crate's
Cargo.toml has all required fields: description, license (BUSL-1.1 needs to verify crates.io accepts it; might need permissive sub-license), repository, documentation
- Internal
path = "..." deps must also have version = "X.Y.Z" so cargo can resolve from crates.io fallback
- Workspace package inheritance (
version.workspace = true) is supported by crates.io
Acceptance
- First batch (≥3 crates) live at crates.io/crates/
- docs.rs auto-publishes pages
- CI workflow auto-publishes on tag push
Operator has connected sentrix-labs GitHub to crates.io (trusted publishing OIDC). Plan the first batch of crates from this repo + parent sentrix-labs/sentrix workspace that get published.
Why
Third-party Rust devs can't
cargo add sdk-rstoday. Publishing makes the SDK discoverable + drop-in.Candidate crates (leaf-first, dependency-free of non-published path deps)
sdk-rsonce internal modules are stablesentrix-labs/sentrix:sentrix-primitives,sentrix-wallet,sentrix-rpc-types,sentrix-codecHard prerequisites
Cargo.tomlhas all required fields:description,license(BUSL-1.1 needs to verify crates.io accepts it; might need permissive sub-license),repository,documentationpath = "..."deps must also haveversion = "X.Y.Z"so cargo can resolve from crates.io fallbackversion.workspace = true) is supported by crates.ioAcceptance