No it has always been that way.
Part of the cleanup we did in the new build system and CI (that builds PMS 1.15.0 and newer) was to make the build and distro values more uniform and consistent.
here are some examples of old vs. new
Old Build
Old Distro
New Build
New Distro
linux-ubuntu-i686
ubuntu
linux-x86
debian
linux-ubuntu-x86_64
ubuntu
linux-x86_64
debian
linux-ubuntu-i686
redhat
linux-x86
redhat
linux-ubuntu-x86_64
redhat
linux-x86_64
redhat
linux-ubuntu-i686
fedora
linux-x86
redhat
linux-ubuntu-x86_64
fedora
linux-x86_64
redhat
linux-ubuntu-x86_64
qnap
linux-x86_64
qnap
linux-armada-arm7
readynas6
linux-armv7sf
netgear
2 Likes
kevinm8
February 12, 2019, 4:09am
63
thanks! i know something broke with my old and hacked together update script in the past few months since i last used it. i need to update it.
are all the API docs “unofficial”?
kevinm8
February 12, 2019, 6:14am
64
ok, i got it. Thanks for the info!
1 Like
Excellent plex.tv/downloads is still 1.14 for me but plexupdate is now working, which is what matters.
1 Like
If channel=8 is for PlexPass builds, what do we use for public releases?
You can use channel=16 for public on the , but only once we have a PMS 1.15.0 or newer build inpublic` on the https://plex.tv/downloads/latest/5 and https://plex.tv/updater/products/5/check.xml endpoints. Until then you will need to use https://plex.tv/downloads/latest/1 https://plex.tv/updater/products/5/check.xml for the last public 1.14.1
system
Closed
May 13, 2019, 7:51pm
69
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.