Conversation
Publishes the CLI as `aube` instead of `aube-cli` on crates.io now that the `aube` name is available. The binary name was already `aube`, so this is purely a package-rename; no user-facing command changes. - Rename crates/aube-cli/ -> crates/aube/ - Flip package name in Cargo.toml + workspace dep - Update release-plz.toml ([[package]] name) and release-plz.yml jq selectors so the release flow tags/drafts off the aube crate - Update hk.pkl msrv path, .gitattributes and docs/installation.md - Refresh source-comment references across the other 9 crates - Rename .aube-cli-* CSS classes (landing-page terminal chrome) - user-agent hostname fallback in login.rs aube-cli 1.0.0-beta.1 stays on crates.io; yank once you're satisfied with the replacement.
Greptile SummaryThis PR renames the Confidence Score: 5/5Safe to merge — purely a rename with no logic changes and no remaining stale references. The rename is thorough and mechanically consistent across all configuration, source, and documentation files. A grep for No files require special attention. Important Files Changed
Reviews (2): Last reviewed commit: "rename: aube-cli crate -> aube" | Re-trigger Greptile |
## Summary - Document `cargo install aube --locked` as an install method on the installation page, between the recommended mise path and the from-source build. - README already defers to the docs page for "other install methods", so no README change. ## Dependency The crates.io page for `aube` doesn't exist yet — it'll be published on the first release-plz cycle after [#7](#7). **Don't merge this PR until that release has landed**, otherwise the docs page will link users to a 404. ## Test plan - [ ] CI green (docs build + link check, if any). - [ ] After merge, verify `cargo install aube --locked` actually pulls from crates.io on a clean machine. <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Low Risk** > Low risk documentation-only change; the main concern is user confusion if the crates.io package is not yet published when this ships. > > **Overview** > Adds a new *From crates.io* section to `docs/installation.md` documenting installation via `cargo install aube --locked`, including a brief explanation of `--locked` and where the binary is installed. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 1faf187. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY -->
Summary
aube-clicrate toaubeon crates.io now that the short name is available. The binary name was alreadyaube, so no user-facing command changes.crates/aube-cli/→crates/aube/(git mv; PR shows as renames).[[package]]name, and the release-plz.yml jq selectors so the tag/draft flow pivots to theaubecrate.hk.pklmsrv path,.gitattributes,docs/installation.md, CLAUDE.md, settings docs, and doc-comment refs across the other 9 crates..aube-cli-*landing-page CSS classes to.aube-*(cosmetic; matches the new crate name).login.rshostname fallback string.Verified locally:
cargo build --bin aube,cargo clippy --all-targets -D warnings, and theusage_kdl_matches_committed_golden_filetest all pass.aube.usage.kdlis byte-for-byte unchanged (binary name stayed the same).Context (resolved)
aube-clihas been deleted from crates.io (404 on the package page), so no yank-and-leave-behind.AUBE_GH_TOKENPAT scope has been fixed, so the release-plz release job can now create git tags — unblocks the full release cycle on merge.Heads-up on first release after merge
First publish of
aubeas a new crates.io package will hit the new-crate rate limit once (~10 min). Expected; just a single retry.Test plan
chore: releasePR on merge withaubelisted as the binary-owning crate.