Repository navigation
docs(gcal): publish gcal 0.4.0 and link every competitor mark on its comparison - #464
Merged
Merged
Conversation
…comparison - tools.json: gcal docsRef v0.3.0 -> v0.4.0 (npm latest). The only reader-facing change between the tags is the 0.4.0 changelog entry; RU/ES changelog translations carry it and their source fingerprints are accepted. - Comparison page (EN/RU/ES): intro now names release 0.4.0. The five competitor marks that had no source (WC-CMP-9) now link to what was checked: offline search for Workspace MCP and google-calendar-mcp (both query Google's events.list live) and Claude's connector article; claude.ai on the web for gcalcli (a terminal CLI, no MCP server) and gog (its MCP server is stdio only). Co-Authored-By: Claude Opus 5.5 <[email protected]>
The release-notes gate needs a review entry for every pinned version. 0.4.0 changes only the shared store version; the roadmap fingerprint is unchanged from 0.3.0. Co-Authored-By: Claude Opus 5.5 <[email protected]>
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.
Why
A standards audit of gcal found its comparison page still dated to release 0.3.0 while npm serves 0.4.0, and five competitor ❌ marks with no source (WC-CMP-9: a mark the reader cannot check).
What
tools.json: gcaldocsRefv0.3.0 → v0.4.0. Between the tags only the changelog changed for readers (one 0.4.0 entry about the shared store version); RU/ES changelog translations add it and their fingerprints are accepted (pnpm docs:translation accept).translations/pages/gcal/compare.{en,ru,es}.md: intro names release 0.4.0; the unlinked ❌ marks now link to what was checked:gcalendar/calendar_tools.pycallsevents().listlive), google-calendar-mcp (SearchEventsHandler.tscallscalendar.events.list), Claude's connector (its support article).docs/mcp.md: its MCP server runs over stdio only).Not in this PR: the drive/memo/tg RU/ES comparison files under
translations/<tool>/compare.*.mdare translations of the older upstream pages (half the length, different sections from the current site-owned EN pages), so they were not moved to the published path.Testing
pnpm sync --tool gcalat v0.4.0 passes the translation gate;pnpm docs:localizereports complete.pnpm ci:quick: 363 tests pass.🤖 Generated with Claude Code