Emby not upgrading to new 4.10.0.x

Noticed in the last 3 months EMBY catalog is no longer being updated
it still shows “4.9.4.1 beta” while latest is 4.10.0.4

I look at github and docker it shows latest:4.10.0.4

Curious why the Truenas catalog for this entry is no longer being updated?
all my other apps update no issue and have updates every few days to acouple weeks.
But only Emby hasn’t updated and if i deply a new on same 4.9 version…

Anyone else having this issue?

Propably because of the discussion in this post and the issue with emby version numbers…

I have used EMBY for a very long time utlising TN apps which were originally the stable train and more recently the beta. I have not seen any performance issues or bugs.

Obviously the catalog app has not been updated in a while so….. what are peoples opinions about custom app as stable or beta? Which do people recommend?

‎I believe the 4.10 branch is still in beta. I don’t think it is full release until it hits 4.10.1.0 from the others versioning thread topic with TrueNAS app versioning.

This feels like a dead lock of never getting emby updates

Yea seems like Emby will never be updated on this platform again

4.10 series is showing as Beta. 4.9.5 is current.

@stavros-k , It looks like Emby 4.10.0.40 is the latest stable branch as of yesterday. Do you know what the timeline looks like for it to show up in the TrueNAS repository after the work you did with 4.9.5.0?

yeah the catalog train for emby has been stuck for a while because of the beta/stable numbering mess.

while you wait on the official chart, the usual workaround is a custom app pointing at the official emby/embyserver image and keep your config + media paths the same. that gets you onto 4.10 without fighting the train.

if you stay on the catalog app, youre basically waiting for the maintainer to bump the tag after 4.10.0.40 landed stable.

FYI Response on Emby Forum:

TrueNas Scale - Page 7 - Linux - Emby Community

Yeah if they randomly declare a version stable with a different versioning scheme, then our regex is going to miss it. After the last debacle with Emby going to a beta version, Stavros modified the renovate bot to watch for stable version numbers ending in .0:

    customVersioning(
      // 1.2.3.0, but not 1.2.3.4 (4th digit != 0 equals beta)
      "^(?<major>\\d+)\\.(?<minor>\\d+)\\.(?<patch>\\d+)\\.0$",
      ["emby/embyserver"],
    ),

This was more or less agreed to by an Emby maintainer (Luke) in this thread Emby 4.9.1.0 Beta in TrueNas Community Edition 25.04 - Page 3 - Linux - Emby Community. If they’re not going to use immutable -beta tags or even a standardized version string for stable releases, then there’s not much we can do about it.

4.10.1.0 has been uploaded to Docker Hub.

while the catalog regex is stuck, custom app can pull the hub tag

Apps → Discover Apps → Custom App:
-image emby/embyserver:4.10.1.0
-reuse the same config + media host paths
-stop the old catalog app first so they dont fight the config dir

or convert the ix-app to a custom app and just change the image tag… if you want to always pull the latest image you could then use the “latest” image tag instead a fixed version number and the truenas gui notifies you if an update got pushed to docker hub and you can update the app as you see fit

Looks like the 4.10.1.0 update got pushed. Thank you @stavros-k for maintaining it.