Skip to content

chore(deps): cli-core 0.651.0, cli-base 0.99.0, family audit through cli-dev - #156

Merged
leemour merged 2 commits into
mainfrom
chore/round-2026-11-13
Nov 13, 2026
Merged

leemour merged 2 commits into
mainfrom
chore/round-2026-11-13

Conversation

@leemour

@leemour leemour commented Nov 13, 2026 •

Copy link
Copy Markdown
Member

Task

Round 2 (2026-11-13): adopt cli-core 0.651.0 and cli-base 0.99.0 in the template, so new CLIs start on them, and
move the family audit onto cli-base's cli-dev audit --family (IDEA-294, IDEA-288 pins). Plan: fix-plan.md of the
round, in cli-private's review reports.

Why

  • New CLIs made from the template must start on cli-core 0.651.0 and cli-base 0.99.0.
  • cli-base 0.99.0 makes same-entity-schema and same-error-reason fail the family audit, and ships
    cli-dev audit --family, which replaces each CLI's copy of scripts/audit.sh.

What

  • Pins: @wirecat/cli-core 0.651.0, @wirecat/cli-base 0.99.0; @wirecat/cli-testing already 0.7.0.
  • contracts/help.snap: the first screen lists pbx (cli-core 0.651.0). mcp-tools.json and the
    mcp-catalogue.json (ownCatalogue) pin need no change.
  • The family audit runs as mail, gcal and beeline run it: CI's checks call
    pnpm exec cli-dev audit --family --cli dist/bin/clidev.js --differences lint/audit-differences.json, and
    audit:commands runs the same inside scripts/sandboxed.ts. scripts/audit.sh and its template.json entry are
    gone. lint/audit-differences.json starts empty, so a new CLI gets a valid file whatever parity groups it joins.
  • config/parity-groups.json: one dated difference, same-error-reason reason meeting-project.stale: code,
    review_after 2026-11-27. cli-core 0.651.0 makes that reason conflict; the published CLIs still give
    configuration_error. None of cli-base 0.99.0's 11 shared rows name clidev (the template's groups have no b24 or
    gcal, and the messenger rows do not reach it), so none is copied. The row lives in config/parity-groups.json, not
    in lint/audit-differences.json, because new CLIs do not get that file and so get no dated row.
  • cli-base reusable workflow pins move to v0.99.0, pinned by its commit 32ebca3. release-checks.yml and release-start.yml were on v0.85.1; their
    workflow_call inputs are the same at both tags. Covers Dependabot build(deps): bump the actions group with 2 updates #154.
  • The cancel setting in main.yml and standards.yml stays as it is (family-wide, WC-CI-7).
  • No contracts/wirecat.json in the template, so no shared host to drop; no schedule run/exec MCP exclusion
    exists (NEED-2604 A holds already).
  • Changelog fragment changes/chore-round-2026-11-13.md.

Testing

Local, in this order: standards:check, lint, typecheck, test:coverage (169 passed), test:matrix:check,
docs:check, generate:check, contracts:check, version:check, security:no-leak, package:check,
peers check, kit:e2e, and audit:commands (audit: 7 CLIs, 248 findings, 0 new that block). Before the parity
row, the family audit failed on the one meeting-project.stale finding.

🤖 Generated with Claude Code

…cli-dev

- Pin @wirecat/cli-core 0.651.0 and @wirecat/cli-base 0.99.0, so a CLI made
  from the template starts on them. cli-testing stays on 0.7.0.
- Refresh contracts/help.snap: cli-core 0.651.0 lists pbx on the first screen.
  mcp-tools.json and mcp-catalogue.json are unchanged.
- audit:commands and CI run `cli-dev audit --family --cli dist/bin/clidev.js`
  inside scripts/sandboxed.ts in place of scripts/audit.sh. template.json no
  longer keeps scripts/audit.sh in step; the file waits in CLEANUP.md.
- config/parity-groups.json: one dated difference (review_after 2026-11-27),
  same-error-reason meeting-project.stale. cli-core 0.651.0 makes it conflict,
  while the published CLIs still give configuration_error. None of cli-base
  0.99.0's 11 shared rows name clidev, so none is copied.
- Move every cli-base reusable workflow pin to v0.99.0 (release-checks and
  release-start were on v0.85.1; their workflow_call inputs are unchanged).
  Covers Dependabot #154.
- Changelog fragment changes/chore-round-2026-11-13.md.

Rules: WC-CI-7 (cancel setting left as is), WC-TEST-14.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@socket-security

socket-security Bot commented Nov 13, 2026 •

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updated@​wirecat/​cli-base@​0.98.0 ⏵ 0.99.099100100 +19670
Updated@​wirecat/​cli-core@​0.650.0 ⏵ 0.651.098 +1100100 +19670

View full report

…e by commit

- CI runs `pnpm exec cli-dev audit --family --cli dist/bin/clidev.js
  --differences lint/audit-differences.json`, the line mail, gcal and beeline
  use, so the next template upgrade in each CLI takes it without asking.
  audit:commands runs the same inside scripts/sandboxed.ts.
- Delete scripts/audit.sh: nothing calls it any more.
- lint/audit-differences.json starts empty, so a new CLI gets a valid file
  whatever parity groups it joins. The template's own meeting-project.stale
  row stays in config/parity-groups.json, which new CLIs do not get, so no
  dated row reaches them.
- The v0.99.0 pins named the annotated tag object (7018773), which Actions
  cannot resolve; they now name its commit (32ebca3).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@leemour
leemour merged commit b831a6d into main Nov 13, 2026
17 of 18 checks passed
@leemour
leemour deleted the chore/round-2026-11-13 branch November 13, 2026 05:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant