chore: upgrade collabora to 25.04.10.3.1, onlyoffice to 9.4.1.1 #6
Reference in New Issue
Block a user
No description provided.
Delete Branch "upgrade-1935df0"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Recipe upgrade: collabora/code 25.04.9.4.1 → 25.04.10.3.1, onlyoffice/documentserver-de 9.3.1.2 → 9.4.1.1.
Image tag table
Both are in-line bumps within supported upstream lines. No compose/config/env changes required.
collabora 26.04.x was deliberately NOT bumped — 26.04 is the next LibreOffice major (operator-only); this PR stays on the 25.04 LO line.
Upstream release notes
Upstream release notes: collabora 25.04.9.4.1→25.04.10.3.1: https://www.collaboraoffice.com/category/release-notes/
Upstream release notes: onlyoffice 9.3.1.2→9.4.1.1: https://github.com/ONLYOFFICE/DocumentServer/blob/master/CHANGELOG.md
onlyoffice 9.4 backend consolidation (removed internal RabbitMQ/DB deps, single process) does NOT affect this recipe: the
onlyofficeservice has no rabbit/db depends_on and its mountedonlyoffice-config.json.tmplis a WOPI-only block with no rabbit/postgres references.Recommended release
abra recipe release lasuite-drive -y(minor: onlyoffice 9.3→9.4 new features + collabora point release). The version label is intentionally NOT bumped in this PR — operator runs the release to publish.Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review.
cc @trav @notplants
!testme
🌻 cc-ci —
lasuite-drive@1935df02✅ passedfull logs · dashboard
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.