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

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

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

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