From 073772a63229b6542fee1d885696cd2905f2cd59 Mon Sep 17 00:00:00 2001 From: leemour Date: Sun, 1 Nov 2026 00:57:14 +0100 Subject: [PATCH] docs(gcal): publish gcal 0.10.0, with its release-notes review gcal 0.10.0 only moves to cli-core 0.512.0; nothing changes for its commands or MCP inputs (gcal does not serve cli-core's shared calendar MCP tools, whose id became operation_id). docsRef v0.9.0 -> v0.10.0, RU/ES changelog sections, fingerprints accepted, review recorded. Co-Authored-By: Claude Opus 5.5 --- docs/release-notes-review.json | 6 +++--- tools.json | 2 +- translations/gcal/changelog.es.md | 7 +++++++ translations/gcal/changelog.ru.md | 7 +++++++ translations/sources.json | 4 ++-- 5 files changed, 20 insertions(+), 6 deletions(-) diff --git a/docs/release-notes-review.json b/docs/release-notes-review.json index af512226..b2906be6 100644 --- a/docs/release-notes-review.json +++ b/docs/release-notes-review.json @@ -36,9 +36,9 @@ "conclusion": "Reviewed released WhatsApp 0.21.0 (Core 0.506.0/Base 0.67.0), covering 0.18.0 to 0.20.0. 0.18.0 transcribes an audio file someone sent, not only a voice note (AAC/M4A need ffmpeg, over an hour is refused). 0.19.0 makes tags list name: ignore case in any alphabet (store v38) and lists gcal under Works with. 0.20.0 finds notes, documents and contact notes by any part of a word in any case, refuses searches under three characters and moves the store to v40. 0.21.0 records each engine request and Graph call as a wire line in events.jsonl (message id only, never a chat id or phone number), adds page.total to search messages, makes --discover search by meaning for explicit syntax and rank a narrow chat:/date: filter's own messages, answers meta.complete: false for a chat held only in part, and refuses an unknown transcribeWith. RU/ES changelog, attachments, commands, diagnostics, remote and search reviewed. The roadmap is unchanged since 0.17.0: reactions you send are still not kept in the local store, and channel files, business labels, the guide command, more files per message and communities stay planned. Earlier: Reviewed WhatsApp v0.11.0 to v0.17.0 with the published changelog and command contract: `reactions list ` (newest first, `reaction:`, --limit and --cursor) lists who reacted from what the local store received (history push, serve and watch), because WhatsApp has no request for older reactions; a reaction sent with `reactions add` or one that arrived while nothing listened is missing, and a channel refuses it with `reactions.broadcast`. `contacts info` is now `contacts show` (--offline), `--show-phone` is gone and `--hide-phone` is the opt-in; a shared contact card shows name and phone. RU/ES changelog, commands, cli-contract, archive, bot, configuration-reference, diagnostics, limits, mcp, people, query-language, recipes, remote, sessions and usage reviewed. The roadmap plans are unchanged: reactions you send are still not kept in the local store, so that item stays planned, as do channel files, business labels, the guide command, more files per message and communities." }, "gcal": { - "version": "v0.9.0", + "version": "v0.10.0", "roadmapSha256": "ccd4d1aaafb881029514e78336072fc7239d2766967957dc81e8581446970a76", - "reviewedAt": "2026-10-31", - "conclusion": "Reviewed released Google Calendar 0.9.0 (Core 0.510.0/Base 0.68.1), covering 0.8.0. 0.8.0 takes the keyring's file fallback from cli-base 0.68.0 with no workaround of gcal's own: a sign-in in the private file stays there until a session start reaches the keyring again. 0.9.0 renames events create --id and events update --following --id to --operation-id (may break callers), adds events list --page with a page.next step that keeps the query, makes search events --backend both answer (store hits first, those Google also found marked server, then Google-only hits, one page with no cursor), fixes the --cursor help, and the MCP agent log now names the calling agent instead of gcal-mcp. EN/RU/ES changelog, usage and commands reviewed. Roadmap unchanged since 0.7.0: sign-in through WireCat's shared Google app is still planned. Earlier: Reviewed released Google Calendar 0.7.0 (Core 0.502.0/Base 0.67.0), covering 0.5.0 and 0.6.0. 0.5.0 renames search to search events and status to store status, makes events list take only field query terms (today, week, from: and overlapping removed; changed: becomes changed_at>=), lists people with event:, and denies deleting or transferring a whole calendar by default. 0.6.0 adds starts_at bounds to events list, makes calendars busy take start>=/end<= with repeatable calendar: and person:, and falls back to a file when the keyring fails (--credential-storage file chooses it). 0.7.0 lets raw api writes that do not delete or share run without a question, and moves the upgrade check to 0.6.0. EN/RU/ES commands, usage, configuration, security, changelog and the comparison reviewed in cli-docs #465, #466 and #467. Roadmap matches the release: the current summary names search events and changed_at>=, the overlapping filter left it; sign-in through WireCat's shared Google app is still planned. Earlier: Reviewed released Google Calendar 0.4.0 (Core 0.491.0/Base 0.65.5). 0.4.0 moves the shared store to version 40 (the trigram index notes and documents search uses), so an older gcal no longer leaves a newer tool's store without its index entries; no command, setting or guide changes. EN/RU/ES changelog reviewed, and the comparison re-dated to 0.4.0 with every competitor mark linked to its source. Roadmap unchanged since 0.3.0: sign-in through WireCat's shared Google app is still planned. Earlier: Reviewed released Google Calendar 0.3.0 (Core 0.489.0/Base 0.65.5), covering 0.2.0. 0.2.0 only publishes the skill on ClawHub as wirecat-gcal. 0.3.0 adds events move --to-calendar, events update|delete --following, events list changed: and events list overlapping, and models list|download; create/update/move/respond are now allowed by default while delete asks, a series update that ends a series sooner needs events.delete.series, a failed sync prints nothing and fails with sync.partial carrying details.calendars, search and links review answer items, search --backend server refuses --newest, and a moved-folder run signs in to its own keyring entry. EN/RU/ES overview, usage, commands, settings, security, changelog, roadmap and the comparison reviewed. Roadmap matches the release: moving an event to another calendar and changing this-and-following occurrences shipped and left Next; sign-in through WireCat's shared Google app is still planned." + "reviewedAt": "2026-11-01", + "conclusion": "Reviewed released Google Calendar 0.10.0 (Core 0.512.0/Base 0.68.1). 0.10.0 only moves gcal to cli-core 0.512.0: no command, option, setting or MCP input changes for gcal. cli-core 0.512.0 renamed id to operation_id in its shared calendar MCP tools and gave events_list a page, but gcal does not serve those tools; its agents use gcal_write and gcal_read, which already take operation_id and events list --page since 0.9.0. RU/ES changelog reviewed; the other gcal pages are unchanged at v0.10.0. Roadmap unchanged since 0.7.0: sign-in through WireCat's shared Google app is still planned. Earlier: Reviewed released Google Calendar 0.9.0 (Core 0.510.0/Base 0.68.1), covering 0.8.0. 0.8.0 takes the keyring's file fallback from cli-base 0.68.0 with no workaround of gcal's own: a sign-in in the private file stays there until a session start reaches the keyring again. 0.9.0 renames events create --id and events update --following --id to --operation-id (may break callers), adds events list --page with a page.next step that keeps the query, makes search events --backend both answer (store hits first, those Google also found marked server, then Google-only hits, one page with no cursor), fixes the --cursor help, and the MCP agent log now names the calling agent instead of gcal-mcp. EN/RU/ES changelog, usage and commands reviewed. Roadmap unchanged since 0.7.0: sign-in through WireCat's shared Google app is still planned. Earlier: Reviewed released Google Calendar 0.7.0 (Core 0.502.0/Base 0.67.0), covering 0.5.0 and 0.6.0. 0.5.0 renames search to search events and status to store status, makes events list take only field query terms (today, week, from: and overlapping removed; changed: becomes changed_at>=), lists people with event:, and denies deleting or transferring a whole calendar by default. 0.6.0 adds starts_at bounds to events list, makes calendars busy take start>=/end<= with repeatable calendar: and person:, and falls back to a file when the keyring fails (--credential-storage file chooses it). 0.7.0 lets raw api writes that do not delete or share run without a question, and moves the upgrade check to 0.6.0. EN/RU/ES commands, usage, configuration, security, changelog and the comparison reviewed in cli-docs #465, #466 and #467. Roadmap matches the release: the current summary names search events and changed_at>=, the overlapping filter left it; sign-in through WireCat's shared Google app is still planned. Earlier: Reviewed released Google Calendar 0.4.0 (Core 0.491.0/Base 0.65.5). 0.4.0 moves the shared store to version 40 (the trigram index notes and documents search uses), so an older gcal no longer leaves a newer tool's store without its index entries; no command, setting or guide changes. EN/RU/ES changelog reviewed, and the comparison re-dated to 0.4.0 with every competitor mark linked to its source. Roadmap unchanged since 0.3.0: sign-in through WireCat's shared Google app is still planned. Earlier: Reviewed released Google Calendar 0.3.0 (Core 0.489.0/Base 0.65.5), covering 0.2.0. 0.2.0 only publishes the skill on ClawHub as wirecat-gcal. 0.3.0 adds events move --to-calendar, events update|delete --following, events list changed: and events list overlapping, and models list|download; create/update/move/respond are now allowed by default while delete asks, a series update that ends a series sooner needs events.delete.series, a failed sync prints nothing and fails with sync.partial carrying details.calendars, search and links review answer items, search --backend server refuses --newest, and a moved-folder run signs in to its own keyring entry. EN/RU/ES overview, usage, commands, settings, security, changelog, roadmap and the comparison reviewed. Roadmap matches the release: moving an event to another calendar and changing this-and-following occurrences shipped and left Next; sign-in through WireCat's shared Google app is still planned." } } diff --git a/tools.json b/tools.json index 7108ef36..ecf22e18 100644 --- a/tools.json +++ b/tools.json @@ -55,7 +55,7 @@ "repo": "WireCatLabs/gcal-cli", "package": "@wirecat/gcal-cli", "lang": "en", - "docsRef": "v0.9.0", + "docsRef": "v0.10.0", "summary": { "en": "Keep your Google Calendar on your computer, search meetings offline and know who the attendees are in your other chats.", "ru": "Храните Google Календарь на своём компьютере, ищите встречи без интернета и узнавайте участников из других ваших чатов.", diff --git a/translations/gcal/changelog.es.md b/translations/gcal/changelog.es.md index 84ec7871..c4af38dd 100644 --- a/translations/gcal/changelog.es.md +++ b/translations/gcal/changelog.es.md @@ -4,6 +4,13 @@ title: "Historial de cambios" Cambios destacados de `@wirecat/gcal-cli`. Una sección por versión, de la más reciente a la más antigua. +## 0.10.0 — 01.11.2026 + +- gcal funciona ahora sobre cli-core 0.512.0. Nada cambia en los comandos de gcal ni en su servidor MCP: cli-core + 0.512.0 renombró `id` a `operation_id` en sus propias herramientas MCP de calendario, que gcal no ofrece. Los + agentes de gcal escriben con `gcal_write`, donde `events create` y `events update` ya aceptan `operation_id` desde la + 0.9.0, y paginan `events list` con `gcal_read` y `page`. + ## 0.9.0 — 31.10.2026 ### Cambios — pueden romper scripts diff --git a/translations/gcal/changelog.ru.md b/translations/gcal/changelog.ru.md index 176ae1d4..92c21828 100644 --- a/translations/gcal/changelog.ru.md +++ b/translations/gcal/changelog.ru.md @@ -4,6 +4,13 @@ title: "История изменений" Заметные изменения в `@wirecat/gcal-cli`. По одному разделу на версию, новые сверху. +## 0.10.0 — 01.11.2026 + +- gcal теперь работает на cli-core 0.512.0. Для команд gcal и его MCP-сервера ничего не меняется: cli-core 0.512.0 + переименовал `id` в `operation_id` в своих общих MCP-инструментах календаря, которые gcal не предоставляет. Агенты + gcal пишут через `gcal_write`, где `events create` и `events update` принимают `operation_id` с версии 0.9.0, и + листают `events list` через `gcal_read` с `page`. + ## 0.9.0 — 31.10.2026 ### Изменено — может сломать скрипты diff --git a/translations/sources.json b/translations/sources.json index 87aa2677..91304ccf 100644 --- a/translations/sources.json +++ b/translations/sources.json @@ -286,7 +286,7 @@ "gcal/configuration.ru": "e7e4abe92f5daa79dc21f1c6e42029e035e2ef4512d898c000bc42deae4e2f6b", "gcal/troubleshooting.ru": "b6a09403c6c616ff308bc988f3b324399052be65ea30d8973094ef59dbd930df", "gcal/security.ru": "73dba01a0eb58c7645451e29e9c5ed30830cc323e2d54b7e6ce18dcc6effeed3", - "gcal/changelog.ru": "51905e348b72c9be6039f50e3409a48957d458d05f4980c5d13865305c436a58", + "gcal/changelog.ru": "0e9538a449a959a06a587318ff2d8b3dfd61bd4dc4b68aa3491d4da8668b1773", "gcal/roadmap.ru": "3a0799752f3548f19329c359eff70882bb1f3b0f941eb385da3d12cd380505c7", "gcal/index.es": "542c70e7db4546c2ebd8ca10994a4104f8f94644956328c541605bb4926558ae", "gcal/installation.es": "6c8e2a7d2d42dba552f491ca940ecd7d888549295bebcb8c331770ad6e20f303", @@ -296,6 +296,6 @@ "gcal/configuration.es": "e7e4abe92f5daa79dc21f1c6e42029e035e2ef4512d898c000bc42deae4e2f6b", "gcal/troubleshooting.es": "b6a09403c6c616ff308bc988f3b324399052be65ea30d8973094ef59dbd930df", "gcal/security.es": "73dba01a0eb58c7645451e29e9c5ed30830cc323e2d54b7e6ce18dcc6effeed3", - "gcal/changelog.es": "51905e348b72c9be6039f50e3409a48957d458d05f4980c5d13865305c436a58", + "gcal/changelog.es": "0e9538a449a959a06a587318ff2d8b3dfd61bd4dc4b68aa3491d4da8668b1773", "gcal/roadmap.es": "3a0799752f3548f19329c359eff70882bb1f3b0f941eb385da3d12cd380505c7" }