You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reopening — the "completed/verified in codebase" close was based on a mis-mapping to records/changes, which is a different Apple endpoint.
Per Apple's CloudKit Web Services Reference, Fetching Database Changes is POST .../changes/database — it returns which zones have changed. Apple explicitly marks the older zones/changes ("Fetching Zone Changes") as deprecated and says to use changes/database instead.
What openapi.yaml actually declares today:
records/changes → fetchRecordChanges — this is Apple's "Fetching Record Changes" (a different endpoint, not database changes).
zones/changes → fetchZoneChanges — this is the deprecated "Fetching Zone Changes" endpoint.
The canonical changes/database path is not in the spec and has no CloudKitService wrapper. So this remains unimplemented; the spec should add changes/database (and fetchZoneChanges/zones/changes should be reconsidered as deprecated).
Resolved on v1.0.0-beta.4 via #429 (commit 0b6bea9) — changes/database as fetchDatabaseChanges / fetchAllDatabaseChanges. (Was still filed under the v1.0.0-alpha.5 milestone; it landed in beta.4.)
Activity
leogdion commentedon Jan 8, 2026
Status: NOT IMPLEMENTED
The database changes endpoint is defined in the OpenAPI specification but has not been wrapped with convenience methods in MistKit.
Current State
What Exists:
openapi.yaml:226:/database/{version}/{container}/{environment}/{database}/records/changesSources/MistKit/Generated/Types.swiftWhat's Missing:
What Remains
Create CloudKitService extension:
Sources/MistKit/Service/CloudKitService+DatabaseChanges.swiftAdd documentation:
Write tests:
Update README.md:
Files to Create/Modify
Sources/MistKit/Service/CloudKitService+DatabaseChanges.swift(new)Tests/MistKitTests/CloudKitServiceDatabaseChangesTests.swift(new)README.md(update roadmap)leogdion commentedon Jan 9, 2026
This issue is now tracked as part of parent issue #199 - Complete CloudKit API Coverage
Add lookupZones, fetchRecordChanges, and uploadAssets operations (#44, …
Add lookupZones, fetchRecordChanges, and uploadAssets operations (#44, …
feat: implement uploadAssets, lookupZones, and fetchRecordChanges ope…
leogdion commentedon Apr 29, 2026
Completed and verified in codebase.
leogdion commentedon May 27, 2026
Reopening — the "completed/verified in codebase" close was based on a mis-mapping to
records/changes, which is a different Apple endpoint.Per Apple's CloudKit Web Services Reference, Fetching Database Changes is
POST .../changes/database— it returns which zones have changed. Apple explicitly marks the olderzones/changes("Fetching Zone Changes") as deprecated and says to usechanges/databaseinstead.What
openapi.yamlactually declares today:records/changes→fetchRecordChanges— this is Apple's "Fetching Record Changes" (a different endpoint, not database changes).zones/changes→fetchZoneChanges— this is the deprecated "Fetching Zone Changes" endpoint.The canonical
changes/databasepath is not in the spec and has noCloudKitServicewrapper. So this remains unimplemented; the spec should addchanges/database(andfetchZoneChanges/zones/changesshould be reconsidered as deprecated).Refs:
Generated by Claude Code
Add changes/database and changes/zone endpoints; deprecate zones/chan…
Add changes/database and changes/zone endpoints; deprecate zones/chan…
leogdion commentedon Aug 28, 2026
Resolved on
v1.0.0-beta.4via #429 (commit 0b6bea9) —changes/databaseasfetchDatabaseChanges/fetchAllDatabaseChanges. (Was still filed under the v1.0.0-alpha.5 milestone; it landed in beta.4.)Add changes/database and changes/zone endpoints; deprecate zones/chan…
v1.0.0 beta.4 (#439)