chore(cargo): add publish metadata to the three new crates #320

Merged

jqueuniet merged 1 commit from chore/publish-metadata into main

2026-09-04 19:39:40 +02:00

jqueuniet commented

2026-09-04 19:36:34 +02:00

Owner

dm2-convert, dm2-ffi and dm2-wasm were added without description, keywords or categories. crates.io requires a description, so cargo publish rejects them outright; without keywords and categories the crates that did upload would land unlisted and unsearchable.

Filled all three in, matching the wording and tagging convention of the crates published for 0.1.x.

crate	keywords	categories
`dm2-convert`	dungeon-master, gamedev, conversion, json, parser	game-development, parser-implementations
`dm2-ffi`	dungeon-master, gamedev, ffi, c-api, bindings	game-development, external-ffi-bindings
`dm2-wasm`	dungeon-master, gamedev, wasm, webassembly, bindings	game-development, wasm

An audit of all thirteen manifests found these three were the only ones missing metadata.

Verification

All four category slugs checked against the live crates.io category API — an invalid slug is a hard publish error.
cargo metadata re-parses cleanly; every publishable crate now carries a description.
cargo publish --workspace --dry-run not run here: it fails in this environment before reaching the manifests, on cargo's git-status pass. Still worth running before the real publish.

Note

The three new crates also set homepage.workspace = true, which the 0.1.x crates omit (homepage and repository are the same URL). Left as-is — happy to align it if you'd rather.

`dm2-convert`, `dm2-ffi` and `dm2-wasm` were added without `description`, `keywords` or `categories`. crates.io **requires** a description, so `cargo publish` rejects them outright; without keywords and categories the crates that did upload would land unlisted and unsearchable. Filled all three in, matching the wording and tagging convention of the crates published for 0.1.x. | crate | keywords | categories | | --- | --- | --- | | `dm2-convert` | dungeon-master, gamedev, conversion, json, parser | game-development, parser-implementations | | `dm2-ffi` | dungeon-master, gamedev, ffi, c-api, bindings | game-development, external-ffi-bindings | | `dm2-wasm` | dungeon-master, gamedev, wasm, webassembly, bindings | game-development, wasm | An audit of all thirteen manifests found these three were the only ones missing metadata. ### Verification - All four category slugs checked against the live crates.io category API — an invalid slug is a hard publish error. - `cargo metadata` re-parses cleanly; every publishable crate now carries a description. - `cargo publish --workspace --dry-run` **not** run here: it fails in this environment before reaching the manifests, on cargo's git-status pass. Still worth running before the real publish. ### Note The three new crates also set `homepage.workspace = true`, which the 0.1.x crates omit (homepage and repository are the same URL). Left as-is — happy to align it if you'd rather.

jqueuniet added 1 commit

2026-09-04 19:36:34 +02:00

chore(cargo): add publish metadata to the three new crates

CI / msrv (1.90) (push) Successful in 43s

Details

CI / audit (push) Successful in 23s

Details

CI / stable (push) Successful in 1m17s

Details

CI / msrv (1.90) (pull_request) Successful in 45s

Details

CI / audit (pull_request) Successful in 22s

Details

CI / stable (pull_request) Successful in 1m17s

Details

a7e9ebc52d

dm2-convert, dm2-ffi and dm2-wasm were added without `description`,
`keywords` or `categories`, so `cargo publish` rejects them (crates.io
requires a description) and the ones that did upload would carry no
keywords or categories. Fill all three in, matching the wording and
tagging convention of the crates published for 0.1.x.

Categories checked against the crates.io category list:
game-development, parser-implementations, external-ffi-bindings and
wasm are all valid slugs.

jqueuniet merged commit a7e9ebc52d into main

2026-09-04 19:39:40 +02:00

jqueuniet deleted branch chore/publish-metadata

2026-09-04 19:39:40 +02:00

No reviewers

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

jqueuniet/dm2-tools!320

No description provided.

Rows
Columns