Since a while appeared a new versioning for desktop app, similar to server versioning.
This could makes sense to make desktop version following server version. For example, as long as I use a Nextcloud server version 34, users are advised to follow desktop version 34. But what if I connect to multiple servers with different versions?
Regarding milestones we can notice that multiple versions are updated regularly (v33, v34, v35 and now the new v36).
But Download and install Nextcloud does not propose to download any except latest. Furthermore, autoupdate of installed versions only propose latest. So why keep updating oldest versions? What is the goal behind that?
And more generally, is there an interest to follow oldest branch of desktop version? If so, how make desktop installations to follow a specific branch?
In general, you should just use the latest desktop version available.
There is no hard dependency, in general the clients are compatible with all older versions of Nextcloud (they might cut support at some point, but that should be long before the server versions fall out of support).
One day there might be the new Nextcloud server version 36 with a fancy new feature, this new feature then probably requires a Nextcloud desktop client 36 or newer. But even in this case, I’d expect the older clients still running and just ignoring the new feature.
Older version are not of great interest, there are some legacy versions for older macOS versions:
(but they should then also work with newer server versions).
What some do with new version, if there is the very first release of a new version, e.g. the 35.0.0, they still stay on the 34-branch and just switch to the 35 branch after the first point release. Or if this is due to a specific bug they wait for it to be fixed.
And for 34 branch, there are still releases: Releases · nextcloud/desktop · GitHub
(I suppose, if you wanted to stay on the 34-branch, you probably have to ignore the updates to the 35 versions, and then yourself check when new versions on the 34 branch appear). I’d do that just if I have a specific problem with a new version.
As a company, you have more support to know how it works in your environment, have your own deployment, branding, …