Calendula 0.2.0 drops pimalaya-toolbox and the inline CalDAV implementation in favour of the new Pimalaya stack:
pimalaya-clifor clap scaffolding, prompts, spinners, and tables.pimalaya-configfor TOML config loading and secret resolution.pimalaya-streamfor TCP/TLS streams.io-vdir 0.0.3for the filesystem-backed backend.io-webdav 0.0.1for CalDAV (RFC 4791) over WebDAV (RFC 4918).io-calendar 0.0.3for the sharedCalendarClientStddispatch layer.
- The top-level command tree was reorganised. Shared commands live under
calendar,event, anditem(the pluralcalendars/events/itemsforms remain as hidden aliases); protocol-specific commands live undervdirandcaldav. - A new global
-b/--backendflag selects the backend used by shared commands. The default isauto(first configured backend wins; vdir wins over caldav). account list,account check, andaccount configurewere added under the newaccountsubcommand.completionsandmanualswere renamed from the previouscompletion/manshapes.
- The
[accounts.<name>.caldav]section keeps its name; locate the calendar home-set with one ofcaldav.discover,caldav.server, orcaldav.home. caldav.auth = "plain"was dropped. Authentication now acceptsnone,basic { username, password }, orbearer { token }.- The new global sections
[table],[calendar],[event],[item]carry per-list rendering options. - The legacy
serde(deny_unknown_fields)behaviour was relaxed so future TUI fields can coexist in the same TOML file.
- Running
calendulawithout a config file proposes to bootstrap one at the default platform path (~/.config/calendula/config.tomlon Linux). calendula account configure --account <name>runs the same wizard against an explicit account, creating it when missing.