QRun-IO/qqq-cli
2
0 Fork 0
Code Issues 1 Pull Requests 1 Actions Packages Projects Releases 1 Wiki Activity
Files
main
qqq-cli/.github/pull_request_template.md
T
james.maesandClaude Fable 5.1 1bc4ddd0be release: qqq 1.0.0 (#11) 
qqq 1.0.0: the command-line client and the full-screen terminal UI (qqq ui) for QQQ applications over the UI API (/qqq/v1), with @qrun-io/qqq-cli 1.0.0, @qrun-io/qqq-core 1.0.0, @qrun-io/qqq-ui-api-client 1.8.0 and @qrun-io/qqq-ui-api-conformance 1.6.0 going final together. Squash of the release/1.0.0 branch at 79ba68e (the branch is kept with the full signed history; the tags v1.8.0 and cli-v1.0.0 point at that commit, which is what the released binaries were built from). See CHANGELOG.md [1.0.0] and docs/release-notes/1.0.0.md.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-11-01 12:49:06 -06:00

1.1 KiB
Raw Permalink Blame History

What and why

Type of change

  • Bug fix
  • New feature or command
  • Breaking change (CLI grammar, output shape, exit code, or a package's exported API)
  • Documentation
  • Refactoring, tests or build

Packages touched

  • @qrun-io/qqq-cli
  • @qrun-io/qqq-core
  • @qrun-io/qqq-ui-api-client (regenerated with npm run generate?)
  • @qrun-io/qqq-ui-api-conformance
  • packages/tui (qqq ui)

Checks

  • npm ci && npm run build && npm test && npm run lint pass
  • npm run test:tui passes (when packages/tui or the kernel changed)
  • Tried against a server (the QQQ sample server, or say which), with the commands used below
  • CHANGELOG.md has an entry under the next version for user-visible changes
  • README, TRY-IT.md or the package README updated for new or changed commands
  • Commits are signed and use conventional-commit subjects

How it was tested

# commands run, and against which server
Reference in new issue View Git Blame Copy Permalink