This release includes breaking changes for platform teams planning a safe upgrade.
✓ No known CVEs patched in this version
Topics
+4 more
ReleasePort's take
Light signalContacts now sync automatically every 15 minutes and deleted CardDAV contacts are removed from Yuvomi with new safeguards.
Why it matters: Automatic sync on the SYNC_INTERVAL_MINUTES schedule (default 15 minutes) streamlines contact consistency, while deletion handling eliminates stale entries; the v89 migration adds a `contacts.carddav_origin` field and backfills existing linked contacts to "merged".
Summary
AI summaryContacts now sync automatically on the same interval as calendars and deleted server contacts are removed from Yuvomi.
Changes in this release
| Type | Severity | Summary | CVE |
|---|---|---|---|
| Feature | Medium |
Contacts now sync automatically on the SYNC_INTERVAL_MINUTES schedule (default 15 minutes). Contacts now sync automatically on the SYNC_INTERVAL_MINUTES schedule (default 15 minutes). Source: llm_adapter@2026-07-15 Confidence: high |
— |
| Feature | Medium |
Deleted CardDAV contacts are now removed from Yuvomi, with safeguards for parsing failures. Deleted CardDAV contacts are now removed from Yuvomi, with safeguards for parsing failures. Source: llm_adapter@2026-07-15 Confidence: high |
— |
| Feature | Low |
Migration v89 adds `contacts.carddav_origin` field ("remote" or "merged") and backfills existing linked contacts to "merged". Migration v89 adds `contacts.carddav_origin` field ("remote" or "merged") and backfills existing linked contacts to "merged". Source: llm_adapter@2026-07-15 Confidence: low |
— |
Full changelog
Added
- Contacts now sync automatically. CardDAV addressbooks only ever synced when "Sync now" was pressed in Settings → Synchronization; they now run on the same
SYNC_INTERVAL_MINUTESschedule (default 15) as calendars, with the manual trigger still available. This was documented behaviour rather than a bug, but it meant a contact added on the phone did not appear in Yuvomi until someone remembered to press a button. - Contacts deleted on the CardDAV server are now removed from Yuvomi as well, instead of lingering forever. Contacts that Yuvomi imported purely from CardDAV are deleted. A contact that already existed locally and was only adopted by the smart-merge logic (matched via email or phone) is kept: it carries locally maintained data that never existed on the server, so only its CardDAV link is dropped and it stays as a plain local contact. Contacts from before this release are treated as adopted, since their origin cannot be reconstructed — they are never deleted automatically, only unlinked. Deletion is suspended entirely, with a warning, whenever the addressbook returns nothing, its fetch fails, or a single vCard cannot be parsed: an incomplete list of contacts must never be read as "everything else was deleted".
Changed
- Migration v89 adds
contacts.carddav_origin(remote/merged) to record how a contact's CardDAV link came about. Existing linked contacts are backfilled tomerged. No data is removed.
Full Changelog: https://github.com/ulsklyc/yuvomi/compare/v1.23.2...v1.24.0
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
Related context
Related tools
Earlier breaking changes
- v0.71.3 Changes WebDAV backup default path from "/oikos/backups/" to "/yuvomi/backups/".
- v0.66.0 Repository URL changed to `https://github.com/ulsklyc/yuvomi`.
- v0.66.0 Docker image moved to `ghcr.io/ulsklyc/yuvomi`.
- v0.66.0 Project renamed from Oikos to Yuvomi.
- v0.62.0 Changes event dialog to unified sync target picker across Google and CalDAV calendars.
Beta — feedback welcome: [email protected]