I’ve processed a batch of major version updates across Big Bear Universal Apps. Rather than doing a straight upgrade on apps where the new version has breaking changes, I’ve introduced separate versioned app entries — so you can stay on the version you know works, and migrate when you’re ready.
What Changed
New App Entries
Three apps had breaking changes significant enough to warrant a new entry alongside the existing one:
-
Vikunja v2 — Vikunja v2 is a full rewrite. Authentication was rebuilt from the ground up (session-based, replacing JWT), API
routes changed, and Typesense search support was removed. The legacy vikunja app stays at v1.1.0. Install vikunja-v2 for
new deployments. -
FarmOS v4 — FarmOS v4 requires PHP 8.4 (Drupal 11) and a minimum of MariaDB 10.6. The legacy app used MariaDB 10, which is
not compatible. The legacy farmos app stays at v3.5.1. Install farmos-v4 for new deployments. -
Password Pusher v2 — v2 drops MySQL/MariaDB support entirely and now requires PostgreSQL. The legacy app was wired to
MariaDB, so a straight upgrade would break the database connection. The legacy passwordpusher app stays at v1.69.3. Install
passwordpusher-v2 for new deployments.
Already Versioned (No Action Needed)
Rocket.Chat and Planka already had versioned app entries (rocket-chat-v8 and planka-v2). The legacy apps have been pinned and will no longer receive auto-updates.
Simple Version Bumps (Already Merged)
These had no breaking changes and were updated directly:
- Zotero — v7 → v9
- Firefox — v1148 → v1149
- Homer — v25 → v26
- Authentik — 2025.12.4 → 2026.2.2
Migration Notes
If you are running any of the legacy apps and want to move to the new version:
- Do not uninstall the legacy app first. Deploy the new versioned app as a separate install, migrate your data, verify
everything works, then remove the old one. - Each new app runs on a different port so both can coexist.
- Migration is one-way — back up before you start.
Links to upstream migration guides are in each app’s install notes.
Pull Request
