* feat(baikal): update to Baikal 0.12.1 and track sabre-io releases ckulka/baikal-docker, and the archived fork the addon was based on, stopped publishing images at Baikal 0.10.1, so the addon could not follow upstream and its updater tracked a repository that no longer moves. The base image is now used for its runtime only (nginx, php-fpm, msmtp) and the application comes from the release published by sabre-io, which the updater can follow. The Home Assistant timezone fix the fork carried as a whole patched Plugin.php is applied as the single hunk it actually is, and the build fails if sabre/dav ever moves that code. The addon data folder holds the application as well as the user data, and it was seeded with no-clobber, so a rebuilt image never replaced the code being served. Application folders are now refreshed on every start ; Specific and config are still only seeded when missing. Closes #3038 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * docs(baikal): satisfy markdownlint on the new changelog and readme lines Bare URLs (MD034) and a heading with no blank line before its list (MD022 / MD032). The blank line matches the older hand-written entries in the same file. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
2.9 KiB
0.12.1 (2026-09-03)
-
Update to Baikal 0.12.1 from 0.10.1 (changelog : https://github.com/sabre-io/Baikal/releases). This includes the 0.12.1 fix for an XSS vulnerability that let an authenticated user take over the admin interface by renaming a calendar
-
⚠ After the update, open the Baikal web admin once : Baikal asks to confirm the upgrade before it serves calendars again
-
The application is now taken from the release published by sabre-io instead of from the ckulka/baikal-docker image, which stopped at 0.10.1. The base image still provides nginx, php-fpm and msmtp. Automatic version tracking is enabled again, following sabre-io/Baikal
-
The Baikal application files in the addon data folder are now replaced on every start instead of being kept. Calendars, contacts, users and the Baikal configuration are untouched ; any manual edit made inside the application folders themselves is lost
-
The Home Assistant project has deprecated support for the armv7, armhf and i386 architectures. Support wil be fully dropped in the upcoming Home Assistant 2025.12 release
0.10.1-hafix4 (2025-11-18)
- Minor bugs fixed
0.10.1-hafix3 (2025-11-18)
- Added support for configuring extra environment variables via the
env_varsoption alongside config.yaml.
0.10.1-hafix2 (2025-08-01)
- Minor bugs fixed
0.10.1+hafix (2025-04-26)
- Update to latest version from ckulka/baikal-docker (changelog : https://github.com/ckulka/baikal-docker/releases)
0.10.1-2 (2024-11-23)
- Minor bugs fixed
0.10.1 (2024-11-23)
- Update to latest version from ckulka/baikal-docker (changelog : https://github.com/ckulka/baikal-docker/releases)
0.9.5_updated (2024-08-06)
- Minor bugs fixed
0.9.5 (2024-04-27)
- Update to latest version from ckulka/baikal-docker (changelog : https://github.com/ckulka/baikal-docker/releases)
0.9.4-3 (2024-04-26)
- ⚠ MAJOR CHANGE : switch to the new config logic from homeassistant. Your configuration files will have migrated from /config/hassio_addons/baikal to a folder only accessible from my Filebrowser addon called /addon_configs/something-baikal. This avoids the addon to mess with your homeassistant configuration folder, and allows to backup the options. Migration of data, custom configs, and custom scripts should be automatic. Please be sure to update all your links however ! For more information, see here : https://developers.home-assistant.io/blog/2023/11/06/public-addon-config/
0.9.4-2 (2024-01-14)
- Minor bugs fixed
0.9.4+msmtpfix (2023-12-30)
- Update to latest version from ckulka/baikal-docker
0.9.4 (2023-12-23)
- Update to latest version from ckulka/baikal-docker
0.9.3+msmtp (2023-11-04)
- Update to latest version from ckulka/baikal-docker
- Implemented healthcheck
0.9.3 (2022-12-13)
- Update to latest version from ckulka/baikal-docker
- WARNING : update to supervisor 2022.11 before installing
0.9.2
- First version