Skip to content

chore(deps): cli-base 0.114.0, so a new CLI's family audit does not block on its neighbours' lag - #182

Merged
leemour merged 1 commit into
mainfrom
chore/cli-base-0.114
Nov 17, 2026
Merged

leemour merged 1 commit into
mainfrom
chore/cli-base-0.114

Conversation

@leemour

@leemour leemour commented Nov 17, 2026

Copy link
Copy Markdown
Member

Task

A CRM CLI from new --from-config failed cli-dev ready on the family audit: entity hit.

Why

  • cli-core 0.688.0 added the crm_file hit kind.
  • tg 0.133.0, max 0.118.0, wa 0.45.0, cli-memo 0.143.0 and drive 0.71.0 still print the old schema.
  • cli-base declared that difference, but a CLI's own config/parity-groups.json dropped it.

What

Testing

  • Local checks pass: typecheck, lint and docs:check.
  • The full suite passes (223 tests).
  • pnpm audit:commands: 0 blocking, exit 0.
  • A fresh probe CRM CLI from the kit, with an empty lint/audit-differences.json, passes the family audit row of cli-dev ready. As before, it does not pass two rows:
    • the contracts row is "partially", because of the write exception;
    • the live check is the owner's.

🤖 Generated with Claude Code

…lock on its neighbours' lag

A CRM CLI from new --from-config failed cli-dev ready on entity hit: half the published family prints it from an
older cli-core. cli-base 0.114.0 keeps its accepted entity and reason differences in a CLI's own groups and does not
block a CLI on a schema a published CLI shares. A fresh probe now passes the audit row with no declared difference.

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

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.112.0 ⏵ 0.114.098100100 +19670

View full report

@leemour
leemour merged commit ae0f4a7 into main Nov 17, 2026
16 checks passed
@leemour
leemour deleted the chore/cli-base-0.114 branch November 17, 2026 20:22
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