/**
 * `telo release` — one release system over the modules of a declared workspace.
 *
 * `add` writes a fragment; `status` explains what would bump and why; `check` is
 * the CI gate; `apply` produces the Version PR; `verify` reconciles the ledger
 * against the registry; `stage` fetches the files `sources:` declares. `telo
 * publish` still keys off version movement.
 *
 * It is the only reader of the marker's `release:` block. `telo run` reads its
 * `env:` block and the editor reads the whole file, but `check`, `publish`,
 * `install`, `upgrade`, `migrate`, `module` and the kernel behave identically
 * with or without one — and every block is optional — which is what keeps a
 * single-manifest repo, a bare `examples/` directory and a third-party module
 * checkout working with nothing added.
 */
import type { Argv } from "yargs";
export declare function releaseCommand(yargs: Argv): Argv;
//# sourceMappingURL=release.d.ts.map