Skip to content

build: add crates.io package metadata - #14

Merged
plusky merged 1 commit into
mainfrom
build/crates-io-metadata
Jul 27, 2026
Merged

build: add crates.io package metadata#14
plusky merged 1 commit into
mainfrom
build/crates-io-metadata

Conversation

@plusky

@plusky plusky commented Jul 27, 2026

Copy link
Copy Markdown
Owner

What

Preparation for publishing to crates.io.

  • repository / homepage on the workspace, inherited by both crates —
    cargo warned that the manifests had none, and crates.io links them from the
    package page.
  • keywords and categories per crate, so the packages are discoverable.
  • README.md and LICENSE linked into each crate directory. Cargo only
    packages files inside the crate, so without this the published archives
    carried neither the licence text nor a rendered readme.

Verification

cargo package -p bugwarden-core is now warning-free and the archive
contains README.md and LICENSE. The equivalent check for bugwarden
cannot pass until bugwarden-core is on the index — it resolves its path
dependency against crates.io during packaging — so that one is verified at
publish time, core first.

No code change; 129 tests unchanged.

Both crates lacked the fields crates.io renders on a package page: cargo
warned about the missing repository/homepage, and neither shipped a readme
or the licence text. Add repository, homepage, keywords and categories, and
link README.md and LICENSE into each crate directory so they land inside the
published archive.
@plusky
plusky merged commit 6f26517 into main Jul 27, 2026
10 checks passed
@plusky
plusky deleted the build/crates-io-metadata branch July 27, 2026 16:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant