Repository navigation
ci(publish): publish the core crate ahead of the CLI - #66
Merged
Merged
Conversation
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.
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR summary
What does this PR do?
Make the tag-pushed release job publish both crates in dependency order:
git2mail-corefirst (the CLI's dependency resolution needs it on the registry), then the CLI. Core'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 job ships both. Also retargets the registry keywords per the discoverability audit (droprustandleak, addcliandrecon); takes effect on the registry with the next published version.Type of change