Publish comline to crates.io

Rescoped 2026-10-18. The CLI command set, UX, completions, man pages and guide all shipped (#2, see the comment below). The only item left was publishing, so this issue now tracks just that. The original checklist is in this issue's edit history.

Publish `comline` to crates.io

So that cargo install comline works.

Blocked: every Comline dependency is a git-rev pin, which crates.io doesn't allow. Publishing needs each dependency released to crates.io first, in dependency order:

comline-core (ComlineProject/core)
comline-codegen (ComlineProject/generation)
comline-codegen-rust (ComlineProject/comline-rust) and comline-codegen-typescript (ComlineProject/comline-typescript)
comline itself

Releasing those also replaces the manual git-rev pin cascade across repos with ordinary version requirements.

feature: expand the CLI's commands, UX and packaging (#1)

Merge pull request #2 from ComlineProject/feature/issue-1-cli

#2 is merged (552127c). What landed:

Commands — diff, clean, a real validate-only check (via the merged ComlineProject/core#21), generate --target, richer new scaffold + --git, completions.
UX — -q/--quiet, --watch for build/generate, progress spinner, colored stderr output decoupled from tracing, stable exit codes (0/1/2), a long_about with examples on every subcommand.
Packaging & docs — Cargo.toml metadata fixed, tokio dropped; man pages + 5-shell completions generated at build time; README.md rewritten; docs/cli.md added as the full guide; CI gains a fmt + clippy -D warnings job.
Tests: 6 → 17.

Left open for the one remaining checkbox: publish to crates.io, blocked on comline-core being released (it is currently a git dependency). A dedicated docs site is wanted eventually but is tracked separately.

Heads-up on an upcoming comline generate rework (design doc: docs/.../planning/code-generation/output-configuration.md):

output location moves to a committed, consumer-owned comline.toml [generate] section (targets, out, layout template, mode); config.idp stays the manifest and never carries output paths.
generate stops calling build() — it uses compile_package() (no CAS write / no version bump) for the latest, freezing only when a historical version is explicitly requested.
new flags --out / --layout / --mode; with >1 configured target they require --target and override only that one.
clean / --watch / new all read the same config.
core side (drop the frozen generation_path + core-side codegen scaffolding) is done on branch feature/drop-frozen-generation-path.

Navigation Menu

Repository navigation

Publish comline to crates.io #1