Skip to content

docs(gcal): publish gcal 0.10.0, with its release-notes review - #472

Merged
leemour merged 1 commit into
mainfrom
docs/gcal-0.9.1
Oct 31, 2026
Merged

leemour merged 1 commit into
mainfrom
docs/gcal-0.9.1

Conversation

@leemour

@leemour leemour commented Oct 31, 2026

Copy link
Copy Markdown
Collaborator

Task

Publish gcal 0.10.0 on the docs site and record its release-notes review so the deploy's release-notes step passes.

What

  • tools.json: gcal docsRef v0.9.0 → v0.10.0.
  • RU/ES changelog: section for 0.10.0; translations/sources.json fingerprints accepted with docs:translation accept.
  • docs/release-notes-review.json: gcal v0.10.0; roadmapSha256 from roadmapFingerprint over content/upstream/gcal/roadmap.md (unchanged since 0.7.0); new conclusion first, the old one after "Earlier: ".
  • No EN/RU/ES page mentions the MCP inputs that changed: gcal 0.10.0 only moves to cli-core 0.512.0, whose renamed inputs belong to cli-core's shared calendar MCP tools, which gcal does not serve. gcal's own MCP (gcal_read/gcal_write) already took operation_id and page in 0.9.0, which these pages already describe.

Testing

  • scripts/sync.ts --tool gcal --capture-only at v0.10.0, then docs:translation check on every gcal page: structure ok; only the changelogs were stale, now current.
  • docs:release-notes: no gcal problem (it lists only tools not synced locally).
  • docs:lint, docs:spell, docs:versions pass.

🤖 Generated with Claude Code

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 <noreply@anthropic.com>
@leemour
leemour merged commit 5c39963 into main Oct 31, 2026
2 checks passed
@leemour
leemour deleted the docs/gcal-0.9.1 branch October 31, 2026 23:58
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