Skipping a major release ends in data corruption, warning/prevention doesn't work

[AlexCloudDev]

Steps to reproduce

1. Upgrade to a newer major version by skipping a major release (e.g.: from 21 --> 23)

Expected behaviour

The update process is being stopped, you stay at your current version and your data is not corrupted

Actual behaviour

The update process is being stopped, you stay at an undefined version and your data is corrupted

Now nextcloud is in maintenance mode. You can't go back to your former release, because you get the error "version of the data is higher than the docker image version".

Server configuration

Operating system:
docker/alpine
Web server:
nginx
Database:
mariadb
PHP version:
7
Nextcloud version: (see Nextcloud admin page)
21

[linucksrox]

This absolutely makes sense to me. I would imagine it's not super complicated to make this work but I haven't looked at the code so maybe there are some other caveats involved.

[J0WI]

see nextcloud/server#2270

[J0WI]

duplicate of #1129