Moving to latest nextcloud 34 release #137

2026-09-28T19:16:20Z

ineiti commented

2026-09-28 19:16:20 +00:00

This release adds the configuration and documentation to use Euro-Office for nextcloud.

As per the MAINTENANCE.md file, it must be installed by at least two maintainers.

@ineiti confirms it's working, specifically including euro-office

#LLM_enabled

I take full responsibility for this code
I understand every line of this code
I tested this code thoroughly on my own computer / servers
None of the commit messages were created using LLMs
I will participate in any discussion on my own and will not use an LLM for the discussion

This release adds the configuration and documentation to use Euro-Office for nextcloud. As per the MAINTENANCE.md file, it must be installed by at least two maintainers. 1. @ineiti confirms it's working, specifically including euro-office #LLM_enabled - [x] I take full responsibility for this code - [x] I understand every line of this code - [x] I tested this code thoroughly on my own computer / servers - [x] None of the commit messages were created using LLMs - [x] I will participate in any discussion on my own and will not use an LLM for the discussion

ineiti requested review from dannygroenewegen 2026-09-28 19:18:22 +00:00

ineiti requested review from moritz 2026-09-28 19:18:23 +00:00

ineiti requested review from javielico 2026-09-28 19:18:43 +00:00

ineiti requested review from carla 2026-09-28 19:18:59 +00:00

ineiti requested review from simon 2026-09-28 19:18:59 +00:00

ineiti changed title from ~~WIP: Moving to latest nextcloud 34 release~~ to WIP: Moving to latest nextcloud 35 release

2026-09-28 19:21:33 +00:00

ineiti changed title from ~~WIP: Moving to latest nextcloud 35 release~~ to WIP: Moving to latest nextcloud 34 release

2026-09-28 19:21:52 +00:00

ineiti referenced this pull request

2026-09-28 19:23:08 +00:00

WIP: pr-15.2.0 - Updating to nextcloud 34.0.2 and EuroOffice #112

ineiti referenced this pull request

2026-09-28 19:23:55 +00:00

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

ineiti referenced this pull request

2026-09-28 19:25:58 +00:00

Updating to the latest nextcloud version #102

ineiti referenced this pull request

2026-09-28 19:26:09 +00:00

Updating to the latest nextcloud version #102

ineiti force-pushed pr-15.0.0+34.0.4 from 2bd5cbaf22 to 41eb0711c5

2026-09-28 19:52:45 +00:00

Compare

ineiti added the help wanted label 2026-10-01 16:43:07 +00:00

ineiti commented

2026-10-01 16:43:25 +00:00

35.0.1 is already out!

ineiti commented

2026-10-05 13:51:01 +00:00

@dannygroenewegen @moritz @javielico @carla @simon if you have some time to test this, so I can go and prepare the PR for version 35!

dannygroenewegen commented

2026-10-06 09:06:49 +00:00

For the next one, it would be better to have separate PRs for something like adding eurooffice and upgrading nextcloud. So they can be reviewed and merged seperatly.

It's on my list to test v34, but currently focusing on other things so might take a bit.

For the next one, it would be better to have separate PRs for something like adding eurooffice and upgrading nextcloud. So they can be reviewed and merged seperatly. It's on my list to test v34, but currently focusing on other things so might take a bit.

ineiti commented

2026-10-06 09:24:59 +00:00

For the next one, it would be better to have separate PRs for something like adding eurooffice and upgrading nextcloud. So they can be reviewed and merged seperatly.

If it is easier for you to test, I can make two PRs. As we're already one major version behind, I didn't want to have to bug people too often :)

> For the next one, it would be better to have separate PRs for something like adding eurooffice and upgrading nextcloud. So they can be reviewed and merged seperatly. If it is easier for you to test, I can make two PRs. As we're already one major version behind, I didn't want to have to bug people too often :)

moritz commented

2026-10-06 11:17:03 +00:00

I started our pipeline on this PR to test v34: https://drone.cicd.local-it.cloud/local-it/kolli-config/1280 but I haven't enabled euro-office yet. I will test this later.

👍 1

moritz approved these changes

2026-10-07 20:59:09 +00:00

moritz left a comment

I tested the nextcloud update to version 34 and it works and nothing breaks so far.
I haven't tested the onlyoffice integration, but I think it's safe enough to merge it. If someone finds any issues with the onlyoffice integration a new fixing PR could be created.

I tested the nextcloud update to version 34 and it works and nothing breaks so far. I haven't tested the onlyoffice integration, but I think it's safe enough to merge it. If someone finds any issues with the onlyoffice integration a new fixing PR could be created.

ineiti marked the pull request as ready for review 2026-10-08 07:39:11 +00:00

ineiti added 1 commit 2026-10-08 07:39:18 +00:00

Moving to latest nextcloud 34 release 9d25f7ee3c

This release adds the configuration and documentation to use
Euro-Office for nextcloud.

ineiti force-pushed pr-15.0.0+34.0.4 from 41eb0711c5 to 9d25f7ee3c

2026-10-08 07:39:18 +00:00

Compare

ineiti merged commit 9d25f7ee3c into main

2026-10-08 07:39:44 +00:00

ineiti deleted branch pr-15.0.0+34.0.4

2026-10-08 07:39:45 +00:00

dannygroenewegen commented

2026-10-08 13:47:24 +00:00

Great that this appears to work!

@ineiti Shouldn't #108 be merged and released first so there is a nextcloud:33-fpm recipe version before the upgrade to 34?

Great that this appears to work! @ineiti Shouldn't #108 be merged and released first so there is a `nextcloud:33-fpm` recipe version before the upgrade to 34?

ineiti commented

2026-10-12 07:04:15 +00:00

Great that this appears to work!

@ineiti Shouldn't #108 be merged and released first so there is a nextcloud:33-fpm recipe version before the upgrade to 34?

I prefer to release first the update to the major version, in case something goes wrong, and it's better to do one more patch/minor upgrade on the previous version.

But the MAINTENANCE.md file tells otherwise: BEFORE major upgrade, do a nextcloud:xx-fpm... Will do that for the 34-35 then...

> Great that this appears to work! > > @ineiti Shouldn't #108 be merged and released first so there is a `nextcloud:33-fpm` recipe version before the upgrade to 34? I prefer to release first the update to the major version, in case something goes wrong, and it's better to do one more patch/minor upgrade on the previous version. But the `MAINTENANCE.md` file tells otherwise: BEFORE major upgrade, do a `nextcloud:xx-fpm`... Will do that for the 34-35 then...

moritz commented

2026-10-12 11:13:36 +00:00

I prefer to release first the update to the major version, in case something goes wrong, and it's better to do one more patch/minor upgrade on the previous version.

Can you elaborate on this in more detail? Our current release 33.0.9 is already the latest nextcloud 33 version.
So you would release version 34 and then do one more patch/minor upgrade on version 33 in an extra branch?

This PR is already merged, but as there is no release yet, it would be simple to revert this PR, merge #108 first, release it and then release this version 34.

> I prefer to release first the update to the major version, in case something goes wrong, and it's better to do one more patch/minor upgrade on the previous version. Can you elaborate on this in more detail? Our current release `33.0.9` is already the latest nextcloud 33 version. So you would release version 34 and then do one more patch/minor upgrade on version 33 in an extra branch? This PR is already merged, but as there is no release yet, it would be simple to revert this PR, merge #108 first, release it and then release this version 34.

ineiti commented

2026-10-13 09:23:33 +00:00

Can you elaborate on this in more detail? Our current release 33.0.9 is already the latest nextcloud 33 version.
So you would release version 34 and then do one more patch/minor upgrade on version 33 in an extra branch?

If somebody doesn't want to move to the next major version, they can use the "floating" version "33" and update easily manually. Once they're ready to do the jump, they'll go to 34.

This PR is already merged, but as there is no release yet, it would be simple to revert this PR, merge #108 first, release it and then release this version 34.

I'm again stuck with abra not being able to create the release - I had the problem already one month ago, something to do with my ssh keys and abra and ssh not agreeing of which key to use. Unfortunately I didn't have the time to look into it.
Your suggestion makes sense. However, #108 is a bit outdated in the meantime, I'll have to update it.

> Can you elaborate on this in more detail? Our current release `33.0.9` is already the latest nextcloud 33 version. > So you would release version 34 and then do one more patch/minor upgrade on version 33 in an extra branch? If somebody doesn't want to move to the next major version, they can use the "floating" version "33" and update easily manually. Once they're ready to do the jump, they'll go to 34. > This PR is already merged, but as there is no release yet, it would be simple to revert this PR, merge #108 first, release it and then release this version 34. I'm again stuck with abra not being able to create the release - I had the problem already one month ago, something to do with my ssh keys and abra and ssh not agreeing of which key to use. Unfortunately I didn't have the time to look into it. Your suggestion makes sense. However, #108 is a bit outdated in the meantime, I'll have to update it.

moritz commented

2026-10-13 11:15:34 +00:00

Ah ok, I think I misunderstood you

I prefer to release first the update to the major version

with this you mean Version nextcloud:33-fpm and not the next major version 34?

If you rebase and merge #108 in the next hours I could do the release. Later I'm on holidays for two weeks. Maybe someone else could do the release then.
Further I would recommend not to update postgres in #108 in the same step. For postgres major updates I recommend extra releases.

Ah ok, I think I misunderstood you > I prefer to release first the update to the major version with this you mean Version `nextcloud:33-fpm` and not the next major version 34? If you rebase and merge #108 in the next hours I could do the release. Later I'm on holidays for two weeks. Maybe someone else could do the release then. Further I would recommend not to update postgres in #108 in the same step. For postgres major updates I recommend extra releases.

ineiti commented

2026-10-13 14:49:40 +00:00

Ah ok, I think I misunderstood you

You understood me correctly, but I changed my mind mid-comment after reading MAINTENANCE.md, sorry...

If you rebase and merge #108 in the next hours I could do the release. Later I'm on holidays for two weeks. Maybe someone else could do the release then.

I should be able to do it, but I have some ssh-key mess I need to sort out. I hope I have time this evening.

Further I would recommend not to update postgres in #108 in the same step. For postgres major updates I recommend extra releases.

Yes, I think we agreed on that. The current postgres update is still waiting because nobody tested it, and I'm not using it. #108 is closed, I'll create a new one.

> Ah ok, I think I misunderstood you You understood me correctly, but I changed my mind mid-comment after reading MAINTENANCE.md, sorry... > If you rebase and merge #108 in the next hours I could do the release. Later I'm on holidays for two weeks. Maybe someone else could do the release then. I should be able to do it, but I have some ssh-key mess I need to sort out. I hope I have time this evening. > Further I would recommend not to update postgres in #108 in the same step. For postgres major updates I recommend extra releases. Yes, I think we agreed on that. The current postgres update is still waiting because nobody tested it, and I'm not using it. #108 is closed, I'll create a new one.

ineiti referenced this pull request

2026-10-13 20:00:04 +00:00

Going from 34 to 35 #140

Sign in to join this conversation.

No Reviewers

dannygroenewegen

javielico

carla

simon

moritz