From be78a5ad271a5e6c03a08581ab4b9b560c23e358 Mon Sep 17 00:00:00 2001 From: Michiel de Jong Date: Tue, 22 Sep 2026 10:49:39 +0200 Subject: [PATCH] Point Calendar README's write-back PR links at the OAD migration localthought/overlays#166 and integration-proxy#75, previously linked here, are now superseded by overlays#168 and integration-proxy#76: the underlying google-calendar base document moved out from under #166 when ontola/openapi-directory removed the hand-written subset it was built against in favor of a regenerated, full calendar/v3 document. See localthought/atomic-plugins#5 for the full history. Co-Authored-By: Claude Sonnet 5 --- integrations/localthought/README.md | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/integrations/localthought/README.md b/integrations/localthought/README.md index acfb1024..7465dc05 100644 --- a/integrations/localthought/README.md +++ b/integrations/localthought/README.md @@ -189,12 +189,17 @@ in this repo. What was still missing was narrower: the composed `localthought/overlays`) only ever declared `GET` operations, so a `PATCH` never reached Google no matter what the proxy or scope allowed. That catalog gap is closed by -[overlays#166](https://github.com/localthought/overlays/pull/166) (adds the +[overlays#168](https://github.com/localthought/overlays/pull/168) (adds the one write operation this lens sends — a partial event update, matching `applyCalendarEdit`'s `summary`/`description`/`location`/`start`/`end` fields and `If-Match`) and -[integration-proxy#75](https://github.com/localthought/integration-proxy/pull/75) -(bumps the deployed `DEFAULT_CATALOG_PATH` pin to it). Both need merging and +[integration-proxy#76](https://github.com/localthought/integration-proxy/pull/76) +(bumps the deployed `DEFAULT_CATALOG_PATH` pin to it). overlays#168 also +migrates the underlying base document: `ontola/openapi-directory` removed the +hand-written, read-only `google-calendar/v3` subset the earlier +[overlays#166](https://github.com/localthought/overlays/pull/166) was built +against, replacing it with a regenerated, full `calendar/v3` document +converted from Google's own Discovery document. Both PRs need merging and the service needs restarting to pick up the new pin before any write reaches Google. Reconnect existing Google accounts if the wider `calendar.events` scope wasn't already exercised in this deployment; Calendar reconnection