Skip to content

Latest commit

 

History

History
83 lines (57 loc) · 5.1 KB

CHANGELOG.md

File metadata and controls

83 lines (57 loc) · 5.1 KB

Changelog

All notable to this project starting from v1.2 will be documented in this file.

Changelogs prior to v1.2 has been removed, but are available in the v1.2-release. The project started with a GNU ChangeLog, but it was useless and horrible to maintain. Then I made up my own kind of changelogs for a while, until someone pointed me towards https://keepachangelog.com. The format of this file is more or less based on Keep a Changelog.

This project should more or less adhere to Semantic Versioning.

[unreleased]

Some bugfixes.

Fixes

  • Some parts of the library would throw OverflowError on very weird dates/timestamps. Now those are converted to the minimum or maximum accepted date/timestamp. Credits to github user @tamarinvs19 in python-caldav#327
  • DAVResponse.davclient was always set to None, now it may be set to the DAVClient instance. Credits to github user @sobolevn in python-caldav#323
  • DAVResponse.davclient was always set to None, now it may be set to the DAVClient instance. Credits to github user @sobolevn in python-caldav#323
  • examples/sync_examples.py, the sync token needs to be saved to the database (credits to Savvas Giannoukas)
  • Bugfixes in set_relations, credits to github user @Zocker1999NET in python-caldav#335 and python-caldav#333
  • Dates that are off the scale are converted to min_date and max_date (and logging en error) rather than throwing OverflowError, credits to github user @tamarinvs19 in python-caldav#327
  • Completing a recurring task with a naïve or floating DTSTART would cause a runtime error
  • Tests stopped working on python 3.7 and python 3.8 for a while. This was only an issue with libraries used for the testing, and has been mended.
  • Bugfix that a 500 internal server error could cause an recursion loop, credits to github user @bchardin in python-caldav#344
  • Compatibility-fix for Google calendar, credits to github user @e-katov in python-caldav#344
  • Spelling, grammar and removing a useless regexp, credits to github user @scop in python-caldav#337
  • Faulty icalendar code caused the code for fixing faulty icalendar code to break, credits to github user @yuwash in python-caldav#347

[1.3.6] - 2023-07-20

Very minor test fix

Fixed

One of the tests has been partially disabled, ref python-caldav#300 , python-caldav#320 and python-caldav#321

[1.3.5] - 2023-07-19 [YANKED]

Seems like I've been using the wrong procedure all the time for doing pypi-releases

[1.3.4] - 2023-07-19 [YANKED]

... Github has some features that it will merge pull requests only when all tests passes ... but somehow I can't get it to work, so 1.3.4 broke the style test again ...

[1.3.3] - 2023-07-19

Summary: Some few workarounds to support yet more different calendar servers and cloud providers, some few minor enhancements needed by various contributors, and some minor bugfixes.

Added

  • Support for very big events, credits to github user @aaujon in python-caldav#301
  • Custom HTTP headers was added in v1.2, but documentation and unit test is added in v1.3, credits to github user @JasonSanDiego in python-caldav#306
  • More test code in python-caldav#308
  • Add props parameter to search function, credits to github user @ge-lem in python-caldav#315
  • Set an id field in calendar objects when populated through CalendarSet.calendars(), credits to github user @shikasta-net in python-caldav#314
  • get_relatives-method, python-caldav#294
  • get_dtend-method

Fixed

Changes

  • Refactored relation handling in set_due

[1.3.2] - 2023-07-19 [YANKED]

One extra line in CHANGELOG.md caused style tests to break. Can't have a release with broken tests. Why is it so hard for me to do releases correctly?

[1.3.1] - 2023-07-19 [YANKED]

I forgot bumping the version number from 1.3.0 to 1.3.1 prior to tagging

[1.3.0] - 2023-07-19 [YANKED]

I accidentally tagged the wrong stuff in the git repo