@stavros-k I’m curious where do you pull the images for EMBY from? It looks like their github does lack the “beta” and “latest” tags. Tags · MediaBrowser/Emby.Releases · GitHub
But it looks like the docker releases do have correct tags. “latest” appears to be latest stable.
Or if there is somewhere else you need the “latest” or “stable” tag I could make a final effort to ask the Emby dev for it.
Dockerhub is used. But versioned tags dont have the stable suffix/prefix.
Latest is not an option. It’s a mutable tag. What happens if it updates for you to a breaking changed version and we didn’t updated the template to correctly handle that?
Right now they have been back to the previous scheme. The current stable version is 4.9.3.0 and the next one will be 4.9.5.0. while the current beta version for 4.9 is 4.9.4.1.
It should be able to conclude that stable version is 4.9.x.0, x is odd; beta version is 4.9.x.!0, x is even. Or you can even consider all the 4.9.x.0 as stable.
Could you please update your regex for fetching and see how it works? As the current fetching strategy doesn’t work, nothing can be hurt anymore.
Any link to the source of this change?
Previous scheme was that if the 3rd digit was 0, it was beta.
Hey, been following this thread and others for awhile now on the topic and figured i would repeat what’s been said on the Emby forum back so it isn’t forgotten.
About the number naming scheme one of the devs said this
So i think it’s safe to say they don’t have such a scheme and it’s just someone who came up with it in an attempt to make sense of it.
As for the 4.9.5 update that’s coming next being stable, that’s something he spoke about the other day.
I would like to point out that he’s simply naming the 4.9.5 update that’s coming as stable. He’s NOT saying that this is a new naming scheme. So for the future, there still needs to be a solution to differentiate between stable and beta.
@stavros-k The new naming scheme has 4 group numbers like this for beta x.x.x.x-beta
and the stable goes like x.x.x.0
will that help you ?
Thanks
Link Source please.
Emby just need to also tag the docker images as well with the -beta suffix. That would solve it.
Hmm dunno about suffix yet when i see the filenames in github
I feel like we are going in circles 
Github releases are not the same thing as container/image/docker tags.
We need suffix/prefix on the tags listed here.
Latest is not an option. It’s a mutable tag. What happens if it updates for you to a breaking changed version and we didn’t updated the template to correctly handle that?
The process now pulls Beta, though, which is arguably worse, right? They say the :latest tag is for stable releases only.
I am going to try and get some Emby people into this thread. I am sure this is just a nomenclature issue - surely it can be solved.
When i go to emby/embyserver - Docker Image i see that there is a tag for beta on the most recent update. Is this not how it’s always been @stavros-k ? Because if it’s not always been like this then there might have been a change the devs didn’t tell us.
As you can see in the screenshot, it clearly says beta there right below tag on the most recent update they pushed. The one before that has the same digest number but didn’t have the beta tag for some reason. So i’m not sure if it matters or not, i’ll leave it to you and other maintainers to make sense of it. And again, it would be cool if you guys could just join that thread on the Emby forums to talk to the devs directly, just do @ and luke and you’ll have a dev that sees your ping. Emby 4.9.1.0 Beta in TrueNas Community Edition 25.04 - Page 2 - Linux - Emby Community
What @stavros-k said above about :latest also applies here:
He can correct me if I’m wrong but it feels like a lot of people are talking past each other here, so this is my understanding of the issue. :latest and :beta are both mutable. This doesn’t work for the TrueNAS apps catalog because the actual version being pulled by that tag can change without warning and the app maintainer does not get a chance to test or troubleshoot issues before rolling it out.
If you look at the screenshot someone posted in that thread:
three years ago emby apparently pushed an immutable beta tag for 4.8.0.30-beta, but since then has used the mutable beta.
On github, I see that emby does use the -beta suffix in the titles of their releases, but even there the actual tag is just the numbers
https://github.com/MediaBrowser/Emby.Releases/releases/tag/4.10.0.2
If emby tagged their versions with that suffix 4.10.0.2-beta, the bot could ignore those, but since they tag both the beta 4.10.0.2 and stable 4.9.3.0 with the same format, the bot can’t tell the difference.
And that is exactly why i linked the forumpost on the Emby forums where we have also been discussing this very thing.
I”m not a dev. I’m someone who uses the Truenas Emby app. All i know is that on this forum, Stavros (and maybe others i don’t know) maintains the app and knows how to adjust things to it. He responds here.
On the Emby forum when someone brings this issue up, it’s Luke who responds. One of the devs for Emby.
That’s why multiple people have linked either post on either forum in hopes that one of the people who can actually do something about the situation goes to that other forumpost and TALKS to that person.
I mean thank you for the app obviously but it’s just ridiculous that basic users have to play telephone for this. I’ll link the post on the Embyforum again, in case someone here who knows what they are talking about wants to go there and @ luke so he can communicate with that person and help get this sorted out. Emby 4.9.1.0 Beta in TrueNas Community Edition 25.04 - Page 2 - Linux - Emby Community
TBH it’s Emby who’s re-inventing the wheel here with their Dockerhub naming of the tags (which btw isn’t standard practice at all). They’ll have to change it if they want, that’s their call, TrueNAS devs shouldn’t have to go to their forums to get them to follow their tagging system in the titles and releases
I feel like you missed part of what i said there.
I said i’m a basic user that just wants to get this resolved and is forced into a role of telephone with other users as we have 2 sides who both think that the other should come to them or adhere to their standards (you can say that Emby’s not doing it right, i don’t know. )
I also said that on either forum (Emby or Truenas) either post has been linked (so here we linked Emby forum’s post, over there we linked Truenas forum’s post)
I didn’t say a truenas dev should go there. I said that us users are hoping that someone from either side goes to the other forum to talk to someone who actually knows these things. Perhaps someone who knows if what you said about the normal system for docker is true? All we want is a solution.
At the moment to put it in a different context. To me it looks like this. I have a car from 2 garages. Garage 1 says that garage 2 needs to change and Garage 2 says it’s garage 1 not doing it right. Me, the person in between doesn’t know who’s right and who’s wrong. That’s why i present contact info to either side in hopes that someone sees it, sends a response and a dialog is opened and it get’s fixed.
I mean it’s been months of this back and forth now. It’s annoying.
