All four packages go final together, with the exact workspace pins, so the orb publishes them as latest. The CHANGELOG's rc.1 entry becomes "## [1.0.0] - YYYY-MM-DD" (date to fill in on release day), docs/release-notes/1.0.0.md is the release body with the final sequence (tags v1.8.0 and cli-v1.0.0, gh release --latest, dist-tag latest), the README, the CLI README and TRY-IT drop the rc version and @rc, and the runbook says this branch is fast-forwarded onto main the day rc.1 feedback is accepted. node scripts/release.mjs --check is READY for 1.0.0. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@qrun-io/qqq-cli
qqq, the command-line client for QQQ applications. It talks to a
QQQ server only through the UI API (/qqq/v1), the same API the web UI uses, so every app, table,
field and process comes from the server's metadata.
echo "@qrun-io:registry=https://npm.pkg.github.com" >> ~/.npmrc
npm install -g @qrun-io/qqq-cli
qqq login --server https://admin.example.com
qqq table query person -w "lastName STARTS_WITH S" -o -id -l 5
Requires Node.js 20 or later, or use a single-file binary from the
releases (no Node needed). Servers: UI API 1.6.0 up to
2.0 (qqq --version prints the range).
Grammar, sign-in, profiles, output formats and exit codes: see the repository README and TRY-IT.md.
Apache-2.0