coop-cloud/nextcloud
9
6
Fork 12
Code Issues 22 Pull Requests 7 Releases Wiki Activity

pr-14.0.0 - Updating to nextcloud 33 - directly as rolling version #98

Closed
ineiti wants to merge 0 commits from pr-14.0.0+33-fpm into main
pull from: pr-14.0.0+33-fpm
merge into: :main
Conversation 2 Commits - Files Changed -
+217 -7
ineiti commented 2026-08-08 08:58:35 +00:00
Owner
Copy Link
Copy Source

This points directly to the latest nextcloud-33, as it is merely a stepping stone for nextcloud-34.

This points directly to the latest nextcloud-33, as it is merely a stepping stone for nextcloud-34.
ineiti changed title from Updating to nextcloud 33 - directly as rolling version to pr-14.0.0 - Updating to nextcloud 33 - directly as rolling version 2026-08-08 09:21:30 +00:00
ineiti changed target branch from pr-13.2.0+32-fpm to main 2026-08-09 13:07:54 +00:00
ineiti force-pushed pr-14.0.0+33-fpm from 8d2c1c7e88 to 00d8c07480 2026-08-09 13:08:57 +00:00 Compare
ineiti force-pushed pr-14.0.0+33-fpm from 00d8c07480 to 5cb22388ed 2026-08-09 19:21:44 +00:00 Compare
dannygroenewegen requested changes 2026-08-10 12:22:11 +00:00
compose.yml Outdated
@@ -49,3 +49,3 @@
app:
image: nextcloud:32-fpm
image: nextcloud:33-fpm
dannygroenewegen commented 2026-08-10 12:18:46 +00:00
Owner
Copy Link
Copy Source

Upgrade works for me. But I think we should also release a pinned version first, 33.0.7, so there is also a predictable version deployment for v33.

Upgrade works for me. But I think we should also release a pinned version first, 33.0.7, so there is also a predictable version deployment for v33.
👍 1
ineiti commented 2026-08-10 12:28:38 +00:00
Author
Owner
Copy Link
Copy Source

so 14.0.0+33.0.7-fpm and 14.1.0+33-fpm?

so `14.0.0+33.0.7-fpm` and `14.1.0+33-fpm`?
👍 1
release/14.0.0+33-fpm Outdated
@@ -0,0 +2,4 @@
IMPORTANT:
- Nextcloud does NOT support downgrades. Take a backup before deploying.
- Do not skip major versions: your instance must be on the latest 32.x before
dannygroenewegen commented 2026-08-10 12:22:04 +00:00
Owner
Copy Link
Copy Source

Refer to check_major_upgrade function (assuming we also merge that for this release)
And if you name this file as release/next, then abra recipe release will automatically rename the file to the released version. Then any PR can add to release/next until we release.

Refer to check_major_upgrade function (assuming we also merge that for this release) And if you name this file as `release/next`, then `abra recipe release` will automatically rename the file to the released version. Then any PR can add to `release/next` until we release.
👍 1
ineiti commented 2026-08-10 12:28:05 +00:00
Author
Owner
Copy Link
Copy Source

But every PR has to override the previous PR's release/next file, correct?

wrt check_major_upgrade - do you want that for 13.2.1? Or should we only start adding it here?

But every PR has to override the previous PR's `release/next` file, correct? wrt `check_major_upgrade` - do you want that for 13.2.1? Or should we only start adding it here?
dannygroenewegen commented 2026-08-10 13:34:41 +00:00
Owner
Copy Link
Copy Source

But every PR has to override the previous PR's release/next file, correct?

Any PR can add some lines to the release/next file if its commit(s) add anything that should be in the next release notes.

> But every PR has to override the previous PR's `release/next` file, correct? Any PR can add some lines to the `release/next` file if its commit(s) add anything that should be in the next release notes.
ineiti added 2 commits 2026-08-11 04:46:42 +00:00
feat: add check_major_upgrade abra.sh function to check readiness for the next major 2fb279d96a 
Checks version skip, pending DB upgrade, occ update:check status, and
non-shipped app compatibility (with an apps.nextcloud.com fallback
lookup) to verify if it looks safe to upgrade to the next Nextcloud major
version.
Updating to nextcloud 33.0.7 0998a98df5
ineiti force-pushed pr-14.0.0+33-fpm from 5cb22388ed to 0998a98df5 2026-08-11 04:46:42 +00:00 Compare
ineiti commented 2026-08-11 05:01:30 +00:00
Author
Owner
Copy Link
Copy Source

Closing in favour of #109 as gitea doesn't want to change my branch names!?!

Closing in favour of #109 as gitea doesn't want to change my branch names!?!
ineiti closed this pull request 2026-08-11 05:01:30 +00:00

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No Reviewers
dannygroenewegen
Labels
Clear labels
bug
Something is not working
 documentation
For issues that are calling out documentation gap
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No labels
Milestone
No items
No Milestone
Assignees
Clear assignees
3wordchant aadil (Aadil Ayub) abra-bot (Abra Bot) ammaratef45 amras (Sarma) BornDeleuze Brooke cas (Cassowary) coopcloud dannygroenewegen (Danny Groenewegen) decentral1se (d1) fauno (fauno) ineiti (Linus Gasser) javielico (Javielico) jjsfunhouse kawaiipunk (KawaiiPunk) knoflook moosemower notplants oxaliq (sorrel) p4u1 renovate-bot (Comrade Renovate Bot) stevensting trav (Trav Fryer) yksflip
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coop-cloud/nextcloud#98