github nextcloud master version

does anyone know when the github latest branch get updated to the newest version?

my Problem is that i have wrote a script to check if my nextclouds are uptodate and to do so i compare my installed version with the “tag_name“ from https://api.github.com/repos/nextcloud/server/releases/latest

but know i have installed version 32.0.3 and on github its still 31.0.12 …

thanks and bests ungoliant

Hi @ungoliant

There’s no latest ‘branch’, and master is already on 33: server/version.php at master · nextcloud/server · GitHub

For some reason, however, the ‘latest release label’ doesn’t reflect the latest stable release. But, I’m neither a developer nor a GitHub expert, so I can’t offer any insight into the ‘why’ or ‘when’.

Why not just use occ update:check ?

ok thank u!

occ update:check only gives me the next available version.. i need the latest possible version..

I googled around a bit, and found this: GitHub - nextcloud-releases/updater_server: 🔂 The updater server keeps you informed about new Nextcloud updates

And then I found that curl -fsSL https://updates.nextcloud.com/updater_server/latest | jq will give me this:

{
  "version": "32.0.3",
  "url": "https://download.nextcloud.com/server/releases/nextcloud-32.0.3.zip",
  "downloads": {
    "zip": [
      "https://github.com/nextcloud-releases/server/releases/download/v32.0.3/nextcloud-32.0.3.zip",
      "https://download.nextcloud.com/server/releases/nextcloud-32.0.3.zip"
    ],
    "bz2": [
      "https://github.com/nextcloud-releases/server/releases/download/v32.0.3/nextcloud-32.0.3.tar.bz2",
      "https://download.nextcloud.com/server/releases/nextcloud-32.0.3.tar.bz2"
    ]
  }
}

And with the following command…

curl -fsSL https://updates.nextcloud.com/updater_server/latest | jq -r '.version'

…I got:

32.0.3

Hope that helps.

1 Like

Often GitHub latest points at the latest stable release, but unfortunately it’s not always accurate due to timing of the artifact releases. i.e. if a v31 maintenance release goes up after a v32 maintenance release it’ll get tagged latest by default unless a human manually fixes it.

If you want to use the GitHub API you’d have to do something like LSIO does here in their Nextcloud image build process.

But the approach suggested by @bb77 is probably the most reliable, IMO. It’s literally pulling the data from Nextcloud’s updater infrastructure so it’s authoritative.

1 Like

yes, i think thats a good option!

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.