v5.0.2

What's Changed

This is a major update of Symfony to the 7.0 version, but including no new features, apart from:

• Use iTIP email when no sender name is present in 231b7ff
• Fix random bytes having null terminators in c4faa17

Important

⚠️ This release drops PHP 8.0 and PHP 8.1 support

How to upgrade

Nothing if you're on v4.4.2+

Full Changelog: v4.4.4...v5.0.2

v5.0.1-rc

Warning

This is a pre-release pending further testing

What's Changed

• Fix a bug when trying to load the profiler in production mode

This is a major update of Symfony to the 7.0 version, but including no new features.

⚠️ This release drops PHP 8.0 and PHP 8.1 support

Full Changelog: v4.4.4...v5.0.1-rc

v5.0.0-rc

⚠️ Yanked — see v5.0.1-rc

v4.4.4

This is a minor fix addressing Docker improvements and other things

What's Changed

This release contains only improvements for Docker image: Switch to PHP 8.3, standalone image package build, as well as fixes in the example compose files.

Note

Note that the standalone version of the image is now generally available in the packages section here. Starting from this release, every new version will trigger both standard and standalone builds. For an example on how to use the standalone image, please refer to the related docker compose file

How to upgrade

Nothing if you're on v4.4.2+

Full Changelog: v4.4.3...v4.4.4

v4.4.3

This is a minor fix addressing Docker improvements and other things

What's Changed

• README: Add new NixOS module by @Ramblurr in #157
• Various Docker improvements: Opcache, image size (5b158af, 37f003c)
• Improve error logging for LDAP

How to upgrade

Nothing if you're on v4.4.2

Full Changelog: v4.4.2...v4.4.3

v4.4.2

What's Changed

• Ability to use Webdav home directories in #143
• Various Docker improvements
• Fix PostgreSQL default encoding in #153
• Allow setting Symfony's dotenv path in #156

How to upgrade

Nothing. There is a new WEBDAV_HOMES_DIR env var (default to an empty string, disabling the home directories), check the README for more information.

Thanks @Ramblurr, @AkselMeola and @de-es for their help

Full Changelog: v4.4.1...v4.4.2

v4.4.1

What's Changed

• Timezone: add the ability to change it easily in #100
• Allow admin auth bypass in #130

How to upgrade

There's nothing much to do, but you can:

1. Add the (optional) APP_TIMEZONE env var if you want to enforce the timezone. By default, timezone is not enforced (which should yield the same behavior as before).

Tip

If you pass the timezone in a Docker env, take care of not including quotes " around the value of the timezone, as they will be passed down to Davis which will result in a bad timezone id. (See the example Docker env file for reference)

2. If you use an external auth provider (such as Authelia) in front of Davis, you can now disable the baked-in auth easily with the ADMIN_AUTH_BYPASS env var (set it to true). By default, nothing changes from the previous release.

💁🏼‍♂️ Also, if you're coming from a release before 4.4.0, please do not forget to run the migration process below

Note

If you encounter the log The parameter "timezone" must be defined. when doing composer install, it means that your cache (from the previous version) is obsolete and Symfony does not manage to clear it. You can do:

rm -rf ./var/cache. # in the Davis application folder

to clean things up. The subsequent composer install will rebuild the cache from scratch and everything should work as expected.

Thanks @MuratovAS for the challenge on auth mechanisms

Full Changelog: v4.4.0...v4.4.1

v4.4.0

What's Changed

• Allow more space for calendar and card data columns (→ MEDIUM TEXT) in #127 and efe4948
• Fix deleting calendar proxies in #126

How to migrate your database

Tip

The added migration will only make changes if you're on MySQL; it's expected, you can ignore if you're using PostgreSQL or SQLite

0. Back up your database

This is a safety precaution in case you end up messing with a migration or the database in general. It's highly recommended, even if you know exactly what you're doing.

1. Update the code and migrate

You can now update the code (either directly or get the up to date container), and then run the remaining migrations with:

bin/console doctrine:migrations:migrate --allow-no-migration

Note

Some migrations are for PostgreSQL, some for MySQL, so it's perfectly normal if you always have a "New" migration that is skipped, and if you're not at the latest one.

---

Full Changelog: v4.3.0...v4.4.0

v4.3.0

What's Changed

• Fix a regression introduced in 4.2.0 about the OPTIONS call (#124)

💁🏼‍♂️ If you're coming from a release before 4.2.0, please do not forget to run the migration process below

How to migrate your database

Warning

While not exactly breaking, you have to update the database schema to have the correct column type. Follow the instructions below.

0. Back up your database

This is a safety precaution in case you end up messing with a migration or the database in general. It's highly recommended, even if you know exactly what you're doing.

1. Update the code and migrate

You can now update the code (either directly or get the up to date container), and then run the remaining migrations with:

bin/console doctrine:migrations:migrate

Note

Some migrations are for PostgreSQL, some for MySQL, so it's perfectly normal if you always have a "New" migration that is skipped, and if you're not at the latest one.

---

Full Changelog: v4.2.1...v4.3.0

v4.2.1 (yanked)

Warning

THIS RELEASE IS YANKED. Please update to 4.3.0 directly, following the migration process of 4.2.0

What's Changed

• Fix a missing import in AddressBook controller

Full Changelog: v4.2.0...v4.2.1