james.maesandClaude Fable 5.1
ac86860422
The repository had no contributor or security guidance and no .github directory, so a 1.0.0 public release would give reporters no private channel and contributors no statement of the checks, the signed-commit rule on main or the license their work falls under. Modeled on QRun-IO/qqq but adapted: npm workspaces plus Bun for the TUI, the qqq-orb cli profile, Apache-2.0 (no AGPL text copied), conventional signed commits. CODEOWNERS requests @KofTwentyTwo on every change. Dependabot groups weekly minor and patch updates for the npm workspaces and, through its bun ecosystem, for packages/tui's bun.lock; the throwaway tui-spike is left out on purpose. Issue templates ask for the qqq doctor build line, and route server and security problems elsewhere. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
1.1 KiB
1.1 KiB
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 withnpm run generate?)@qrun-io/qqq-ui-api-conformancepackages/tui(qqq ui)
Checks
npm ci && npm run build && npm test && npm run lintpassnpm run test:tuipasses (whenpackages/tuior the kernel changed)- Tried against a server (the QQQ sample server, or say which), with the commands used below
CHANGELOG.mdhas an entry under the next version for user-visible changes- README,
TRY-IT.mdor 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