Is it safe to update Vikunja?
Tracking go-vikunja/vikunja
Update with care.
No explicit breaking changes or required migration steps are called out in the notes, but the introduction of a plugin system and OAuth 2.0 provider mode are significant architectural additions that may affect existing integrations or configuration. The 11 security fixes make upgrading urgent, so reviewing the full changelog at the linked URL before deploying is prudent.
What changed
v2.3.0 ships 11 security fixes, making prompt upgrading strongly advisable. It introduces a new plugin system, adds Vikunja itself as an OAuth 2.0 provider, and brings WeKan and CSV import options. Desktop users gain a quick-entry window for faster task capture. The release spans 277 commits, reflecting a substantial cycle of improvements alongside the security work.
Source
Every verdict on Bumplog traces back to a GitHub release. No invented details.
