Repository navigation
feat(meetings)!: read Zoom through cli-core's find/get, manage meetings under meetings, drop remote-meetings - #373
Merged
Conversation
…gs under `meetings`, drop remote-meetings - cli-core 0.667.0 (was 0.663.0) and cli-base 0.102.1 (was 0.100.0). - ZoomApiSource implements find/get: `meetings list` finds meetings that ran and are not stored, and `meetings show` reads one again from Zoom by its instance uuid or its meeting number (then its latest instance). Sync, find and get name a run by the same instance uuid. get needs the optional meeting:read:past_meeting scope, refuses with permission_error without it, and writes no series, since a past meeting's answer has no join link or recurrence. finds.upcoming is false: Zoom gives each run its own uuid. - meetings create|update|cancel|invitation come from cli-core's createMeetingManagement; a create needs --start-time, there is no instant meeting. They open no store and need no login for a preview. - remote-meetings is removed, with no alias. Its permission default is gone; cli-core asks first for meetings.create|update|cancel. - The stored-event link moves from `meetings update --event-id` to `meetings link --event-id`, so `meetings update` means the same as in every other CLI on cli-core. - docs/remote-meetings.md becomes docs/meeting-management.md; the other pages, the skill and the generated references follow. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…onth at a time `meetings list` sent one previous-meetings page of up to 100 series and one instance request per series, with no dates: up to ~600 requests per list. - find asks List meetings with from/to (whole UTC days, timezone=UTC) and page_size=300, one 30-day stretch of the started_at window per call, newest first; past instances get the same from/to. - At most 20 series' instances per call; the cursor carries on in the same page, then the stretch before. One list sends at most 3 calls x 2 pages x 21 = 126 requests. - Without started_at it starts at today and walks back to Zoom's 6-month limit; when cli-core's page cap stops it first, the answer is complete: false with meetings.server-capped. - Tests use a strict fake that refuses from without to, a non-day date, no timezone or a page over 300. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…Info Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ew paths The ci check failed its 97% statement floor (96.52%): the removed remote-meetings tests had covered code that is now unused or untested. - ZoomRemoteMeetings.list/show and the management list/get ports are gone: no command calls them. - checkPermission no longer asks: no zm command takes its own --yes now; cli-core's management asks through askBeforeWrite. - The configured source declares find/get without stand-in functions, and calls the built source's method on it. - Tests: link's mixed event and person forms, a bad find cursor, an invalid list, a repeated token, an empty id, a meeting that never started, a transcript refusal, a folder source and reset, and a malformed provider answer. Statements 97.03% locally. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- meetings update, cancel and invitation get examples that name the meeting. - meetings link's summary fits 80 characters. - "meetings invitation" is cli-core's word, so it joins the unknown-verb baseline; the stale "search meetings --tag" option-role entry is gone. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Merged
leemour
added a commit
that referenced
this pull request
Nov 15, 2026
## Task Release #373 (cli-core 0.667.0, find/get, management under `meetings`, `remote-meetings` removed, the event link moved to `meetings link --event-id`). ## What `changes/feat-meetings-find-get-management.md` is collected into `## 0.77.0 — 15.11.2026`, and the version is raised to 0.77.0 in `package.json` and `src/version.ts`. ## Testing `pnpm version:check` and `pnpm docs:check` pass locally. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
leemour
added a commit
that referenced
this pull request
Nov 15, 2026
…ts with meetings link (#376) ## Task The 0.77.0 release ([run 43757122355](https://github.com/WireCatLabs/zoom-cli/actions/runs/43757122355)) failed `installed-platforms` on all six jobs with "network, browser or keyring accessed". Nothing was published. ## What - `scripts/installed-platform.mjs`: `meetings list` and `meetings show` now also ask Zoom (#373), so they read the keyring, which the proof forbids. The proof's store reads now pass `--backend archive`, both from the CLI and in the MCP `zm_read` calls. - `scripts/installed-meeting-integration.mjs`: event links use `meetings link --event-id`, which #373 missed. ## Testing The installed-platform proof passes locally on Linux (Node 24.19.0) against the packed 0.77.0 tarball. Typecheck and biome pass. The platform jobs run only on a release, so the release run checks Windows and macOS. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Task
gcal's cross-CLI parity check fails on zoom. zm's
meetings updatelinked a stored meeting to an event, while cli-core's sharedmeetings updatechanges a meeting on the service. zoom was also still on cli-core 0.663.0. The owner ruled: move zoom to cli-core 0.667.0, move the event link offmeetings updatewith no alias, and adopt cli-core's meeting reads and management.What
--json <fields>keeps theuntrustedlist.ZoomApiSourceimplementsfind,getandfinds.meetings listfinds meetings that ran and are not stored yet.meetings showreads one again by its instance uuid or its meeting number (then its latest instance).finds.upcomingis false, because Zoom gives each run its own uuid.getneeds the optionalmeeting:read:past_meetingscope (added to the app guide), and refuses withpermission_errorwithout it.getwrites no series, because a past meeting's answer has no join link or recurrence.findasks List meetings withfrom/to(whole UTC days,timezone=UTC),type=previous_meetingsandpage_size=300, one 30-day stretch of thestarted_atwindow per call, newest first. Past instances get the samefrom/to. A call reads the runs of at most 20 series, and its cursor carries on in the same page, then in the stretch before. One list sends at most 3 calls × 2 pages × 21 = 126 requests; a plain list sends at most 42.started_at, the list starts at today and walks back to Zoom's 6-month limit. When cli-core's page cap stops it first, the answer iscomplete: falsewithmeetings.server-capped.finds.upcoming: false): one that has not run has no instance uuid to store. cli-core says so inmissing, andmeetings scheduledlists them.from,to,timezoneandpage_sizeparameters follow Zoom's List meetings docs. The tests use a strict fake: it refusesfromwithoutto, a date that is not a day, notimezone, and a page over 300.meetings create|update|cancel|invitationcome from cli-core'screateMeetingManagement.--start-time. There is no instant meeting.remote-meetings, with no alias.meetings update <ref> --event-id→meetings link <ref> --event-id.linkalready carried the person link.docs/remote-meetings.md→docs/meeting-management.md. The other pages, the skill and the generated references are updated. The changelog note ischanges/feat-meetings-find-get-management.md.A fresh review agent found three bugs, all fixed here, each with a regression test:
find/getwithout binding them to their object, so live reads never ran.getblanked the stored series.--dry-runchange.Testing
docs:check,contracts:checkandpnpm generate. The test matrix shows 344 tested, 21 untested with a reason, 0 missing.remote-meetingskey;--json=<field>in a locked run.🤖 Generated with Claude Code