Updating to the latest nextcloud version #102

New Issue

Open

opened 2026-08-08 09:25:45 +00:00 by ineiti · 3 comments

ineiti commented 2026-08-08 09:25:45 +00:00

Owner

Copy Link

Copy Source

Meta-discussion issue with @dannygroenewegen for the following PRs:

• pr-13.2.0 - Last release for nextcloud-32 (#97)
• pr-14.0.0 - Updating to nextcloud 33.0.7 (#109)
• pr-14.1.0 - Upgrading postgresql to 17 (#110)
• WIP: pr-14.2.0 - Rolling release for nextcloud 33 (#108)
• WIP: pr-15.2.0 - Updating to nextcloud 34.0.2 and EuroOffice (#112)

Let's discuss:

• how to test these PRs
• what needs to be changed

My proposition is:

• we checkout one PR after the other in our ./recipes/nextcloud directory, and then abra app deploy -f <nextcloud> --chaos and check if things are running OK

I propose we also do #96 and add the !test to the PRs.

Meta-discussion issue with @dannygroenewegen for the following PRs: - #97 - #109 - #110 - #108 - #112 Let's discuss: - how to test these PRs - what needs to be changed My proposition is: - we checkout one PR after the other in our `./recipes/nextcloud` directory, and then `abra app deploy -f <nextcloud> --chaos` and check if things are running OK I propose we also do https://git.coopcloud.tech/coop-cloud/nextcloud/issues/96 and add the `!test` to the PRs.

ineiti referenced this issue 2026-08-08 09:28:29 +00:00

chore(deps): update pgautoupgrade/pgautoupgrade docker tag to v18 #85

dannygroenewegen commented 2026-08-08 09:48:11 +00:00

Owner

Copy Link

Copy Source

Yes, either checkout and chaos deploy, or I believe you can also use a commit hash as a version to deploy.

For each PR we should indeed test the deployment. And if we don't find any issues, we can merge the PR and run abra recipe release to publish a correct release. Then move on to the next PR.

Yes, either checkout and chaos deploy, or I believe you can also use a commit hash as a version to deploy. For each PR we should indeed test the deployment. And if we don't find any issues, we can merge the PR and run `abra recipe release` to publish a correct release. Then move on to the next PR.

👍 1

ineiti commented 2026-08-09 13:10:48 +00:00

Author

Owner

Copy Link

Copy Source

if I do abra recipe release for the 13.2.0+32 tag, I get the following:

? select recipe version increment type minor
INFO synced label coop-cloud.${STACK_NAME}.version=13.2.0+32.0.13-fpm to service app
? add release note? (leave empty to skip) Last release for nextcloud-32, pointing to the latest version of nextcloud-32.
ERRO failed to publish new release: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
FATA release failed. any changes made have been reverted

So I git tag -a manually and upgraded.

if I do `abra recipe release` for the `13.2.0+32` tag, I get the following: ``` ? select recipe version increment type minor INFO synced label coop-cloud.${STACK_NAME}.version=13.2.0+32.0.13-fpm to service app ? add release note? (leave empty to skip) Last release for nextcloud-32, pointing to the latest version of nextcloud-32. ERRO failed to publish new release: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain FATA release failed. any changes made have been reverted ``` So I `git tag -a` manually and upgraded.

ineiti commented 2026-08-09 13:20:44 +00:00

Author

Owner

Copy Link

Copy Source

@dannygroenewegen I upgraded my main server to 14.0.0 and then to 14.1.0 and did not have any problems. As per the MAINTENANCE.md, we said we need two maintainers before doing a major step - so if you have time to check this on your own server, too, specifically if you're using the compose.postgresql, this would be great!

Then we can go on with 15.2.0 (see #104 :(

@dannygroenewegen I upgraded my main server to 14.0.0 and then to 14.1.0 and did not have any problems. As per the MAINTENANCE.md, we said we need two maintainers before doing a major step - so if you have time to check this on your own server, too, specifically if you're using the compose.postgresql, this would be great! Then we can go on with 15.2.0 (see #104 :(

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

update_33.0.8

renovate/pgautoupgrade-pgautoupgrade-18.x

renovate/docker.elastic.co-elasticsearch-elasticsearch-9.x

pr-15.2.0+34.0.2-fpm

pr-14.1.0+33.0.7-fpm

pr-14.2.0+33-fpm

pr-15.1.0+34.0.2-fpm

pr-15.0.0+34.0.2-fpm

pr-14.0.1+33.0.7-fpm

feat/check-major-upgrade

pr-14.0.0+33-fpm

temp

fix/nginx-conf-config-name

pr-13.2.0+32-fpm

renovate/redis-8.x

upload-limit

feature/imaginary

kc_stable

nextcloud-v28

add-theming-v28.0.5

add-theming

update-nginx-conf

split-bbb-onlyoffice-compos

split-onlyoffice-bbb-config

authentik_sso

healthchecks

occ_cmds

auto_app_install

embed_nextcloud_in_iframe

auto_configure_sso

add-postgres-db

14.1.1+33.0.8-fpm

14.1.0+33.0.7-fpm

14.0.1+33.0.7-fpm

14.0.0+33.0.7-fpm

13.2.0+32-fpm

13.1.5+32.0.13-fpm

13.1.4+32.0.13-fpm

13.1.3+32.0.13-fpm

13.1.2+32.0.13-fpm

13.1.1+32.0.12-fpm

13.1.0+32.0.11-fpm

13.0.1+32.0.3-fpm

13.0.0+32.0.3-fpm

12.1.0+31.0.6-fpm

12.0.1+31.0.6-fpm

12.0.0+31.0.6-fpm

11.4.0+30.0.6-fpm

11.4.0+30.0.10-fpm

11.3.0+30.0.6-fpm

11.2.0+30.0.6-fpm

11.1.0+30.0.6-fpm

11.0.1+30.0.4-fpm

11.0.0+30.0.4-fpm

10.0.0+30.0.4-fpm

9.2.0+29.0.8-fpm

6.0.11+28.0.10-fpm

6.0.10+28.0.10-fpm

6.0.9+28.0.10-fpm

9.1.2+29.0.5-fpm

6.0.8+28.0.5-fpm

6.0.7+28.0.5-fpm

9.1.0+29.0.5-fpm

9.0.0+29.0.5-fpm

6.0.6+28.0.5-fpm

8.0.1+29.0.3-fpm

8.0.0+29.0.1-fpm

7.0.3+29.0.1-fpm

6.0.5+28.0.5-fpm

7.0.2+29.0.1-fpm

7.0.1+29.0.1-fpm

7.0.0+29.0.0-fpm

6.0.4+28.0.5-fpm

6.0.3+28.0.5-fpm

6.0.2+28.0.5-fpm

5.0.3+27.0.1-fpm

6.0.1+28.0.2-fpm

6.0.0+28.0.1-fpm

5.2.0+27.1.5-fpm

5.1.1+27.1.5-fpm

5.1.0+27.1.3-fpm

5.0.2+27.0.1-fpm

5.0.1+27.0.1-fpm

5.0.0+27.0.0-fpm

4.0.7+26.0.2-fpm

4.0.6+26.0.2-fpm

4.0.5+26.0.2-fpm

4.0.4+26.0.2-fpm

4.0.3+26.0.2-fpm

4.0.2+26.0.2-fpm

4.0.1+26.0.1-fpm

4.0.0+26.0.1-fpm

3.3.2+25.0.6-fpm

3.3.1+25.0.5-fpm

3.3.0+25.0.5-fpm

3.2.0+25.0.4-fpm

3.1.2+25.0.4-fpm

3.1.1+25.0.1-fpm

3.1.0+25.0.1-fpm

3.0.1+25.0.1-fpm

3.0.0+25.0.1-fpm

2.1.4+24.0.6-fpm

2.1.3+24.0.5-fpm

2.1.2+24.0.3-fpm

2.1.1+24.0.2-fpm

2.1.0+24.0.0-fpm

2.0.0+23.0.4-fpm

1.0.0+23.0.1-fpm

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

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/nextcloud#102