coop-cloud/nextcloud
10
7
Fork 11
Code Issues 13 Pull Requests 9 Releases Wiki Activity

WIP: pr-14.2.0 - Rolling release for nextcloud 33 #108

Closed
ineiti wants to merge 2 commits from pr-14.2.0+33-fpm into main
pull from: pr-14.2.0+33-fpm
merge into: :main
Conversation 7 Commits 2 Files Changed 4
+5 -4
ineiti commented 2026-08-11 04:52:55 +00:00
Owner
Copy Link
Copy Source

As discussed, started with a fixed version in 14.0 and 14.1, and only now going to rolling release.

As discussed, started with a fixed version in 14.0 and 14.1, and only now going to rolling release.
ineiti changed title from Rolling release for nextcloud 33 to pr-14.2.0 - Rolling release for nextcloud 33 2026-08-11 05:00:16 +00:00
ineiti changed target branch from pr-14.1.0+33-fpm to main 2026-08-11 05:01:58 +00:00
ineiti changed target branch from main to pr-14.1.0+33.0.7-fpm 2026-08-11 05:03:49 +00:00
ineiti marked the pull request as work in progress 2026-08-11 20:42:25 +00:00
dannygroenewegen changed target branch from pr-14.1.0+33.0.7-fpm to main 2026-08-13 10:18:50 +00:00
dannygroenewegen added 2 commits 2026-08-13 10:18:50 +00:00
chore: publish 14.0.1+33.0.7-fpm release e17a1aa057
Releasing rolling version of nextcloud 4a3a426de8
moritz commented 2026-09-21 11:16:36 +00:00
Owner
Copy Link
Copy Source

if people want this, this could be enabled using an image env. Else I think it's not a good idea because it makes the recipe nondeterministic and unstable. You don't know which exact version you are deploying, A redeployment would trigger an unwanted update. This would make debugging and testing difficult and lead to unexpected behavior.

if people want this, this could be enabled using an image env. Else I think it's not a good idea because it makes the recipe nondeterministic and unstable. You don't know which exact version you are deploying, A redeployment would trigger an unwanted update. This would make debugging and testing difficult and lead to unexpected behavior.
ineiti commented 2026-09-22 06:41:08 +00:00
Author
Owner
Copy Link
Copy Source

if people want this, this could be enabled using an image env. Else I think it's not a good idea because it makes the recipe nondeterministic and unstable. You don't know which exact version you are deploying, A redeployment would trigger an unwanted update. This would make debugging and testing difficult and lead to unexpected behavior.

Can you please open an PR with a change to MAINTENANCE.md? Because currently we have this in our workflow:

the previous release gets a last update pointing to the docker image versions nextcloud:xx-fpm, so that users can auto-update if they wish so

Then we can discuss it there. The idea is that this is a minor update to the coop-cloud recipe, which people can choose, or not to, but which let's them follow the patches of nextcloud without us having to do anything...

> if people want this, this could be enabled using an image env. Else I think it's not a good idea because it makes the recipe nondeterministic and unstable. You don't know which exact version you are deploying, A redeployment would trigger an unwanted update. This would make debugging and testing difficult and lead to unexpected behavior. Can you please open an PR with a change to MAINTENANCE.md? Because currently we have this in our workflow: > the previous release gets a last update pointing to the docker image versions nextcloud:xx-fpm, so that users can auto-update if they wish so Then we can discuss it there. The idea is that this is a minor update to the coop-cloud recipe, which people can choose, or not to, but which let's them follow the patches of nextcloud without us having to do anything...
moritz commented 2026-09-22 09:08:12 +00:00
Owner
Copy Link
Copy Source

the previous release gets a last update pointing to the docker image versions nextcloud:xx-fpm, so that users can auto-update if they wish so

Then we can discuss it there. The idea is that this is a minor update to the coop-cloud recipe, which people can choose, or not to, but which let's them follow the patches of nextcloud without us having to do anything...

Thank you for clarification. This was a misunderstanding on my side. If this only affects the last release directly in front of the next major release, it's a different story. I thought it should affect every release 😅.

> > the previous release gets a last update pointing to the docker image versions nextcloud:xx-fpm, so that users can auto-update if they wish so > > Then we can discuss it there. The idea is that this is a minor update to the coop-cloud recipe, which people can choose, or not to, but which let's them follow the patches of nextcloud without us having to do anything... Thank you for clarification. This was a misunderstanding on my side. If this only affects the last release directly in front of the next major release, it's a different story. I thought it should affect every release 😅.
👍 1
ineiti commented 2026-09-28 19:23:55 +00:00
Author
Owner
Copy Link
Copy Source

Closing this and waiting for #137 to be merged - perhaps we get another patch version in between :)

Closing this and waiting for #137 to be merged - perhaps we get another patch version in between :)
ineiti closed this pull request 2026-09-28 19:24:04 +00:00
moritz reopened this pull request 2026-10-13 11:17:43 +00:00
compose.postgres.yml
@@ -11,3 +11,3 @@
db:
image: "pgautoupgrade/pgautoupgrade:14-debian"
image: "pgautoupgrade/pgautoupgrade:17-debian"
moritz commented 2026-10-13 11:19:02 +00:00
Owner
Copy Link
Copy Source

It's better to update postgres in a separate release.

It's better to update postgres in a separate release.
ineiti commented 2026-10-13 14:48:17 +00:00
Author
Owner
Copy Link
Copy Source

Sorry for the mess - this PR dates from a time when I hoped that I could merge all updates and then update to the 34 version in one hour. Two months later, postgres-17 has been merged to version 33, and many other things happened. So this PR is definitely out of date. I'll create a proper one.

Sorry for the mess - this PR dates from a time when I hoped that I could merge all updates and then update to the 34 version in one hour. Two months later, postgres-17 has been merged to version 33, and many other things happened. So this PR is definitely out of date. I'll create a proper one.
ineiti commented 2026-10-13 14:49:08 +00:00
Author
Owner
Copy Link
Copy Source

I'll create a proper last release for version 33.

I'll create a proper last release for version 33.
ineiti closed this pull request 2026-10-13 14:49:08 +00:00
ineiti commented 2026-10-13 20:01:01 +00:00
Author
Owner
Copy Link
Copy Source

It's probably too difficult to create a rolling release for 33 - I propose we do #140

It's probably too difficult to create a rolling release for 33 - I propose we do #140

Pull request closed

Please reopen this pull request to perform a merge.
This pull request is marked as a work in progress.
Sign in to join this conversation.
Reviewers
No Reviewers
moritz
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 (Born Deleuze) Brooke carla cas (Cassowary) coopcloud dannygroenewegen (Danny Groenewegen) decentral1se (d1) fauno (fauno) ineiti (Linus Gasser) javielico (Javielico) jjsfunhouse kawaiipunk (KawaiiPunk) knoflook moosemower moritz notplants oxaliq (sorrel) p4u1 (p4u1) renovate-bot (Comrade Renovate Bot) simon stevensting (stevensting) trav (Trav Fryer) yksflip
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coop-cloud/nextcloud#108