From cc51cb6088c0e85f58c216c930dbbf0037fac0ec Mon Sep 17 00:00:00 2001 From: extiop <29679238+extiop@users.noreply.github.com> Date: Mon, 26 Oct 2026 20:27:49 +0000 Subject: [PATCH 1/2] ci(publish): publish the core crate ahead of the CLI The core crate's first release (0.8.0) went out by hand because crates.io cannot attach a Trusted Publisher to a name that does not exist yet. The crate now exists and its trusted publisher is configured on the registry, so the publish job ships both crates in dependency order: core first, so the CLI's dependency resolution finds it, then the CLI itself. No new action is introduced - the existing OIDC token covers both publishes. --- .github/workflows/git2mail.yml | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/.github/workflows/git2mail.yml b/.github/workflows/git2mail.yml index 9103755..7c5a4b5 100644 --- a/.github/workflows/git2mail.yml +++ b/.github/workflows/git2mail.yml @@ -200,12 +200,15 @@ jobs: - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1 - uses: rust-lang/crates-io-auth-action@c6f97d42243bad5fab37ca0427f495c86d5b1a18 # v1.0.5 id: auth - - name: Publish to crates.io - # git2mail-core's FIRST release goes out by hand: crates.io cannot - # attach a Trusted Publisher to a name that does not exist yet - # (pending publishers are a deferred item in RFC 3691). Once core - # exists and its trusted publisher is configured on crates.io, this - # job publishes both crates - core first, then the CLI. + - name: Publish the core crate to crates.io + # core first: the CLI's dependency resolution needs it on the + # registry before `cargo publish --package git2mail` runs. Both + # publishes go through the crate's Trusted Publisher (registered + # once 0.8.0 had landed core's first, hand-pushed release) + run: cargo publish --package git2mail-core + env: + CARGO_REGISTRY_TOKEN: ${{ steps.auth.outputs.token }} + - name: Publish the CLI to crates.io run: cargo publish --package git2mail env: CARGO_REGISTRY_TOKEN: ${{ steps.auth.outputs.token }} From ab3cacdfcde86e58f7f447ceae8252392ce711c2 Mon Sep 17 00:00:00 2001 From: extiop <29679238+extiop@users.noreply.github.com> Date: Mon, 26 Oct 2026 20:28:08 +0000 Subject: [PATCH 2/2] chore(crate): retarget the registry keywords Drop "rust" (crates.io is Rust-only by definition - the word adds no discrimination) and "leak" (on the registry, that search space belongs to memory-leak tooling, not breach investigators; the GitHub topic keeps serving the right audience unbound by the five-keyword cap). Add "cli" (registry categories are not text-searched, so the keyword is the only match for "cli" queries) and "recon" (the practitioner vocabulary for this tool class). The "wasm" dimension stays off the CLI manifest on purpose: the published artifact is a native binary, and the wasm story lives in git2mail-core and the site. The change takes effect on the registry with the next published version. --- Cargo.toml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Cargo.toml b/Cargo.toml index 9868098..d585437 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -8,7 +8,7 @@ license = "LGPL-3.0-only" description = "Pure Rust OSINT CLI: uncover the email addresses behind GitHub activity: repository, profile and keyword scans, reverse email lookup, and full user/organization investigations. 100% GitHub REST API, no scraping." repository = "https://github.com/extiop/git2mail" readme = "README.md" -keywords = ["github", "osint", "rust", "leak", "email"] +keywords = ["osint", "github", "email", "cli", "recon"] categories = ["command-line-utilities"] # MLA-style workspace: the root package is the CLI; `core/` holds the pure