Cargo.toml already carries the metadata: description, repository,
documentation, readme, keywords, categories, and an exclude for assets and CI
config. Licence is MIT, and there are zero dependencies.
Before publishing
- Confirm
cargo package excludes extern/ — the die submodule must not end up
in the crate archive under any circumstance. That is the whole licence
boundary. Verify by unpacking the .crate and looking, not by reading the
exclude list.
cargo publish --dry-run.- Decide whether
0.1.0 is honest given the API will move. The README says
"0.1 is the shape, not a promise", which is the right framing.
Blocked on, arguably
tinymachines/6502 keeping a second copy of this source rather than depending
on it. Publishing is what makes that dependency cheap to express, so this could
equally go first.
Cargo.tomlalready carries the metadata: description, repository,documentation, readme, keywords, categories, and an
excludefor assets and CIconfig. Licence is MIT, and there are zero dependencies.
Before publishing
cargo packageexcludesextern/— the die submodule must not end upin the crate archive under any circumstance. That is the whole licence
boundary. Verify by unpacking the
.crateand looking, not by reading theexclude list.
cargo publish --dry-run.0.1.0is honest given the API will move. The README says"0.1 is the shape, not a promise", which is the right framing.
Blocked on, arguably
tinymachines/6502keeping a second copy of this source rather than dependingon it. Publishing is what makes that dependency cheap to express, so this could
equally go first.