Repository navigation
Point Calendar README at the google-calendar OAD migration - #24
Merged
michielbdejong merged 3 commits intoSep 22, 2026
Merged
Conversation
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 #5 for the full history. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Closed
…r-oad-migration-646b6f
michielbdejong
enabled auto-merge
September 22, 2026 09:09
…r-oad-migration-646b6f
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
1 participant
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.
Summary
Part of #5 (Phase 1: close the calendar write-back gap). The Google Calendar OAD (OpenAPI directory source) this platform's catalog depends on moved:
ontola/openapi-directoryremovedAPIs/googleapis.com/google-calendar/v3/openapi.yaml— a hand-written, read-only "Reflector subset" of Calendar v3 that had drifted from Google's real API — and replaced it with a regeneratedAPIs/googleapis.com/calendar/v3/openapi.yaml, converted straight from Google's own Discovery document.The actual catalog/overlay/proxy work lives in the other two repos in this integration's stack (as established by the previous Phase 1 session — see #5's history):
google-calendarcatalog document to the new base spec, replaces the previous PR's hand-writtenPATCHoperation with a security override on the operation the full spec now defines natively, and widens security narrowing to the ~30 other operations the full spec brings along (superseding Pin atomic-server to 69602364b (#1755 re-publisher read, #1756 well-known 404) #166 and its interim, incorrectly-based Host API requirements to complete the server protocol plugins #167).DEFAULT_CATALOG_PATHpin to the migrated catalog and regenerates the checked-in composed-document test fixtures (supersedes the deployment concern the now-merged Bump atomic-server to b875d4a31 and lift the plugin-system e2e quarantine #75 addressed for the old base).This repo's only change is pointing the Calendar README's deployment-requirement note at the new PRs instead of the now-superseded ones.
Test plan
localthought/overlays: composed and validated the migrated document (openapi_spec_validator),python3 tests/test_identity_overlays.py(3/3 pass against the live pinned branch).localthought/integration-proxy:cargo test --bin auth-proxy(100 passed, 0 failed), plus the three network-gated catalog-pin tests run explicitly against the live new pin (all pass, including confirming the previous base document's removal doesn't break anything).🤖 Generated with Claude Code