Skip to content

chore(release): 0.2.0 on cli-core 0.671.0 and cli-base 0.103.0 - #32

Merged
leemour merged 3 commits into
mainfrom
chore/cli-core-latest
Nov 16, 2026
Merged

leemour merged 3 commits into
mainfrom
chore/cli-core-latest

Conversation

@leemour

@leemour leemour commented Nov 16, 2026

Copy link
Copy Markdown
Member

Why

beeline 0.1.0 was built on cli-core 0.663.0 and cli-base 0.100.0. The owner asked to move it to the latest cli-core and release it.

What

  • cli-core 0.671.0 (was 0.663.0) and cli-base 0.103.0 (was 0.100.0; cli-core 0.671.0 needs >=0.102.1).
  • The breaking meetings changes of cli-core 0.667.0 and 0.668.0 need no code here. They touch meetings create|update|cancel, createMeetingManagement and custom MeetingStores without participantCandidates. beeline mounts none of the write commands and reads cli-core's own store.
  • What callers see: meetings transcript and meetings export answer an untrusted list, and a search meetings hit may carry by, score and passage. The generated docs/commands.md follows.
  • lint/audit-differences.json: the temporary meeting_hit entry is removed, because beeline now builds on 0.664.0+. The family audit still reports 0 new blocking differences.
  • lint/baseline/option-role.json: the stale search meetings --tag entry is removed. The command lint no longer finds it.
  • The fresh audit found that the meetings transcribe help example duration_ms>=60000 was not quoted, so a shell redirected it to a file. It is quoted now.
  • Version 0.2.0: before 1.0.0, Added raises the minor. The fragment is collected into the dated section.

Conformance

  • pnpm release:check passed on 2ca139d, the released code: 12 test files, 127 tests, lines 96.5%, branches 82%. Command lint ok. Family audit: 10 CLIs, 0 new findings that block. Test matrix: 75 tested, 0 missing. The no-leak, docs, generate, version and package checks pass.
  • Live check (read-only, with the owner's yes, bin/beeline-live nbzb): 0.2.0 2ca139df848db1862a2638e8dc8ebf7f48974bf8 2026-11-16 bin/beeline-live v2:01b5cb21edd481af660362e286ef321399e8704e175b1c1178971b6bb6418134. session status --check ok. meetings sync saved 245 meetings, 0 warnings. meetings list returned 3. meetings transcribe transcribed 1 call, 0 failed. The first run, at 11:07, got HTTP 503 from Beeline's API. A probe without a token also got 503, so the outage was Beeline's. The rerun after the API recovered passed.
  • Comparison page (WC-CMP-11): none. Neither cli-docs translations/pages/beeline/ nor docs/compare.md exists.
  • Fresh audit (a new subagent, prompt from docs/dev/skills/release/fresh-audit.md): every package check passed. It found 39 gaps: 28 in this repository, 5 in the handbook and 6 in other repositories. None is new in this change. Gap 1 (no live line for 0.2.0) and gap 14 (the unquoted help example) are fixed here. The other repository gaps are follow-ups:
    • WC-CMD-17: meetings list with an unknown profile saves an account. search meetings opens the store for writing.
    • WC-OUT-15: the meeting and provider_error error details are not registered.
    • WC-ARCH-22: meetingsMount keeps per-call state in the command tree, which mcp serve shares between calls.
    • WC-LIFE-16: the next step of sync.continue drops --timeout and --max-pages.
    • WC-OUT-13: audio_seconds instead of _ms. Without --check, session status answers verified: false.
    • WC-TEST-5, 8 and 9: a timer wait in the beeline-api tests, a phone-like fixture, a shared work store between tests, and no test that run events leave out PII.
    • WC-STYLE-5 (as casts), WC-DOC-2 (README.ru.md is not in USER_PAGES), WC-CI-14 (the pinned node-ci.yml v0.85.1 is older than cli-base), WC-CI-4 (ci:quick builds twice), WC-TEST-14 (the reason for the contracts:upgrade skip is stale), WC-TEST-19, WC-SECR-17.
    • Repository settings: squash-only merges (WC-STYLE-10), the npm environment limited to main (WC-REL-11), the social preview (WC-DOC-21).
    • Handbook: WC-LIFE-15, 16 and 17, and WC-STORE-1 do not list beeline, or keep a stale note about it. WC-DOC-13 versus the Russian README. The MCP catalogue snapshot rule.
  • Slice reviews: none. This change is a dependency bump and has no new feature slice.

🤖 Generated with Claude Code

leemour and others added 3 commits November 16, 2026 10:53
cli-core 0.671.0 (was 0.663.0) and cli-base 0.103.0 (was 0.100.0). The
breaking meetings changes of 0.667.0 and 0.668.0 touch create, update and
cancel and custom meeting stores; beeline mounts none of them and reads
cli-core's own store, so no code changes. The shared answers now mark
other people's text untrusted, and a meeting search hit may carry by,
score and passage, which the generated command reference follows.

With beeline on 0.664.0+, the temporary meeting_hit audit difference
goes; the family audit still reports 0 new blocking differences. The
command lint no longer finds search meetings --tag's option role, so its
stale baseline entry goes too.

Added raises the minor before 1.0.0: 0.2.0, with the fragment collected.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…cribe

Unquoted, a shell reads > as a redirect to a file named =60000. Found by
the release's fresh audit.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.100.0 ⏵ 0.103.099100100 +196 +170
Updated@​wirecat/​cli-core@​0.663.0 ⏵ 0.671.098100100 +19670

View full report

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