Warning
- Change to database schema so make a backup before updating (Dropped calendar timezone column in favour of timezone_id)
- RustiCal is now very strict with verifying that the
UID
in events matches the id in the database. It's highly unlikely that you are affected by this, but if so you'll see error messages. Feel free to reach out if you need help fixing invalid ids.
Features
- Switched from ical-rs to an own fork
- More validation of uploaded objects like checking that
UID
and object id match - This should help catch invalid calendar objects before having weird or undefined behaviour.
- More validation of uploaded objects like checking that
- Lots of changes around timezones
- Since commonly only timezones from the IANA Timezone Database are used we drop support for other timezones. That means we only need to save the timezone id for a calendar and get well-defined and correct behaviour with low effort.
Full Changelog: v0.7.0...v0.8.0