Open Bockeman opened 1 year ago
This is maybe a duplicate of #241
@bbx-github thanks for your possible link to #241
Evidence https://github.com/nextcloud/cms_pico/issues/227 https://github.com/newroco/emlviewer/issues/47 shows that there is still a problem here, whether or not related to #241
When updater.phar updates NC it also updates all enabled apps to the latest version. There does not appear to be any check that the latest version of any app is compatible with the latest version of NC.
Technically the updater.phar
doesn't update apps at all, but I understand what you're getting at. It triggers occ upgrade
at the end, which does deploy db and app upgrades.
Your config looks to be the cause of at least part of this:
"updater.release.channel": "beta",
[...]
"app_install_overwrite": [
"cms_pico"
]
app_install_overwrite
have been force enabled. All compatibility checks are inherently bypassed for force enabled apps. You have cms_pico
listed there.updater.release.channel
being set to beta
means you get offered pre-release apps from the store if their info.xml
says they're compatible Also, since cms_pico
is mentioned:
v1.1.0-beta.1
listed (and downloadable) in the app store is definitely not permitted for >v23. And it matches its branch in their repo (and I double-checked the max-version there too). However, their master
branch (which I believe @PhrozenByte warns not to use) has an info.xml
that also reports itself as v1.1.0-beta.1
and has a higher max-version
set. Is it possible you installed that and/or did it from outside the app store?git
installed (i.e. manually deployed outside of the app store) apps IIRC also have special handling. I believe they bypass too, but I'd have to re-look at the code
⚠️ This issue respects the following points: ⚠️
Bug description
I've run into several problems over many NC upgrades. When updater.phar updates NC it also updates all enabled apps to the latest version. There does not appear to be any check that the latest version of any app is compatible with the latest version of NC.
Some examples: https://github.com/nextcloud/cms_pico/issues/227 https://github.com/newroco/emlviewer/issues/47
Steps to reproduce
Expected behavior
updater.phar should not update an app that is incompatible with the NC update version
Installation method
Other Community project
Operating system
Other
PHP engine version
PHP 8.1
Web server
Apache (supported)
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
Updated to a major version (ex. 22.2.3 to 23.0.1)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
No response
Nextcloud Logs
No response
Additional info
CLI Installation and many upgrades OS = Fedora 37