Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -119,6 +119,7 @@ Tests must be hermetic: CI has no `cmduse` binary and no homebrew prefix, so any

- **Versions are independent:** `cmduse-core` runs its own major line, the CLI is 0.7.x. Never read one from the other. Core's semver stays loose on purpose (an internal breaking change rides a MINOR); **core's major always leads the CLI's** so the two never look like a pair. crates.io slots are permanent — 0.2–0.4 and 0.6.x are burned; each release takes one patch above the published version, never a reuse.
- **Publish order:** core first when it changed (`cargo package -p cmd-usage` verifies against the _published_ core), then the CLI. Clean tree (Cargo.lock committed).
- **The `cmduse-v*` tag does NOT publish the crate** — `release.yml` builds the six assets and stops, so `cargo publish -p cmd-usage` is a separate step and `verify-crate.ts` reports `absent from the index` until it runs; measured 2026-11-05, where a green release run read as a finished release.
- **Releases ship prebuilt binaries** (tag `cmduse-vX.Y.Z`, workflow `release.yml`): six targets, `cmduse-<ver>-<target>.tar.gz` with binaries at the archive root + `cmduse.1` + licence, plus `SHA256SUMS`. **The staged binary list is defined once** (a job-level `BINS` env the artifact `cp` loop and the `install -m` line both read) — a new bin needs one edit, not two.
- **Homebrew after every release:** `scripts/bump-tap.sh cmduse-vX.Y.Z` matches pins by target triple off the release's own `SHA256SUMS` and aborts without writing when a pin has no sha. The tag carries a `v`, asset names do not. Formula installs all six binaries (`bin.install "cmduse", "ocuse", "arkuse", "cmdusedev", "ocusedev", "arkusedev"`).
- **Verify with the scripts, never by eye:** `opencode-plugin/scripts/verify-crate.ts <version>` (crate ⇄ release assets ⇄ tap pins) and `verify-release.ts <version>` for npm (`--source` for a CI-published package, `--dir <path>` for another package). Running them from the repo root fails — the scripts live in `opencode-plugin/scripts/`.
Expand Down
Loading