Emby 4.9.1.0 Beta in TrueNas Community Edition 25.04

[Luke 42505]

2 hours ago, Shiroyama said:

What is the numbering logic going because the beta is now on 4.10.0.10? The stable version goes backwards...?

The stable version number will always be a little lower than beta.

[sskwhiteshadow 6]

Is this every going to be fixed where we can use beta and stable to do upgrades as this is a little wild to have 8 months now of what seems 0 progress for your users on TrueNas platform... 

Why are we not following standardization . Stable release line/Beta (with the correct tags and flags)
- Allowing the user to pick the Stable release line or the Beta release line

- Its been way to long for this fix its been 8 months, it feels you are killing y you user base on TrueNas for something as simple as labeling. 

Because Emby never used explicit -beta tags on their Docker images, the TrueNAS bot was forced to rely on an unofficial "math trick" (a Regex script) to tell them apart. The bot was programmed to assume that any version ending in .0 (like 4.9.3.0) was Stable, and anything else was a Beta.

When Emby's version numbering deviated from this assumed rule, the bot accidentally pulled a Beta into the Stable train. To prevent further damage and stop more users from getting unwanted beta software, the fetching script was essentially halted.

Right now, there is a standoff:

• The TrueNAS maintainers cannot turn the update bot back on or fix their script because Emby won't guarantee what the numbering scheme will be moving forward. If they guess wrong, they break thousands of stable TrueNAS installs again.

• The Emby developers feel they are tagging things correctly on GitHub (using the "pre-release" checkbox) and don't want to change their internal workflow to accommodate the TrueNAS Docker bot.

Because neither side has aligned, the bot is stuck waiting for a "safe" version, and you are stuck getting nothing.

How This Can Be Fixed (Based on the Forum Standoff)

1. The Immediate "Band-Aid" Fix (Emby's Move) The fastest way to unblock everyone right now is for the Emby team to release their next stable update using the exact numbering scheme the TrueNAS bot is currently looking for—specifically, a version ending in .0 (such as 4.9.5.0). If Emby pushes a release with this exact format, the TrueNAS bot's existing script will recognize it as "safe," wake up, and push the update to all TrueNAS users.

2. The Long-Term Fix (Emby Tagging Docker Images) The Emby team argues that they already mark betas using GitHub's "pre-release" flag. The problem is that Docker catalog bots don't look at GitHub checkboxes; they look at the raw Docker Image tags. Emby needs to bridge this gap by explicitly adding -beta and -stable directly to their image tags. If they publish an image tagged 4.10.0.2-beta, the TrueNAS maintainer can simply tell the bot, "Ignore all tags with the word beta." This permanently ends the numbering-scheme guessing game.

3. The Compromise Fix (A Published, Hard Rule) If Emby refuses to add -beta to their tags, they must officially and publicly commit to a rigid mathematical rule (e.g., "The 3rd digit will ALWAYS be even for stable and odd for beta"). If Emby officially documents this rule and promises not to break it, the TrueNAS maintainer can safely rewrite the update script to match that logic and turn the updates back on.


PLEASE FIX THIS

Edited May 13 by sskwhiteshadow

[hjason7812 35]

On 10/16/2025 at 1:54 PM, richt said:

Having read several of the threads on this issue and noting that Luke has already provided the general framework, it seems to me the best course of action is for the maintainer of the FreeNAS Emby App to get on this forum and PM Luke.  Playing man in the middle on this is inefficient and must be frustrating.

What Luke has stated several times over is that the one in charge of the app on truenas asked to do it and emby team said ok go ahead. Bur seeing as though they've obviously dropped the ball to say it mildly I think the emby team should take back control of this since it's their baby and should be taken care of the right way. Which we all can admit it's not being taken care of at all since tbei hasn't been a new app update on truenas since scale became release candidate. 

[hjason7812 35]

3 hours ago, sskwhiteshadow said:

Is this every going to be fixed where we can use beta and stable to do upgrades as this is a little wild to have 8 months now of what seems 0 progress for your users on TrueNas platform... 

Why are we not following standardization . Stable release line/Beta (with the correct tags and flags)
- Allowing the user to pick the Stable release line or the Beta release line

- Its been way to long for this fix its been 8 months, it feels you are killing y you user base on TrueNas for something as simple as labeling. 

Because Emby never used explicit -beta tags on their Docker images, the TrueNAS bot was forced to rely on an unofficial "math trick" (a Regex script) to tell them apart. The bot was programmed to assume that any version ending in .0 (like 4.9.3.0) was Stable, and anything else was a Beta.

When Emby's version numbering deviated from this assumed rule, the bot accidentally pulled a Beta into the Stable train. To prevent further damage and stop more users from getting unwanted beta software, the fetching script was essentially halted.

Right now, there is a standoff:

• The TrueNAS maintainers cannot turn the update bot back on or fix their script because Emby won't guarantee what the numbering scheme will be moving forward. If they guess wrong, they break thousands of stable TrueNAS installs again.

• The Emby developers feel they are tagging things correctly on GitHub (using the "pre-release" checkbox) and don't want to change their internal workflow to accommodate the TrueNAS Docker bot.

Because neither side has aligned, the bot is stuck waiting for a "safe" version, and you are stuck getting nothing.

How This Can Be Fixed (Based on the Forum Standoff)

1. The Immediate "Band-Aid" Fix (Emby's Move) The fastest way to unblock everyone right now is for the Emby team to release their next stable update using the exact numbering scheme the TrueNAS bot is currently looking for—specifically, a version ending in .0 (such as 4.9.5.0). If Emby pushes a release with this exact format, the TrueNAS bot's existing script will recognize it as "safe," wake up, and push the update to all TrueNAS users.

2. The Long-Term Fix (Emby Tagging Docker Images) The Emby team argues that they already mark betas using GitHub's "pre-release" flag. The problem is that Docker catalog bots don't look at GitHub checkboxes; they look at the raw Docker Image tags. Emby needs to bridge this gap by explicitly adding -beta and -stable directly to their image tags. If they publish an image tagged 4.10.0.2-beta, the TrueNAS maintainer can simply tell the bot, "Ignore all tags with the word beta." This permanently ends the numbering-scheme guessing game.

3. The Compromise Fix (A Published, Hard Rule) If Emby refuses to add -beta to their tags, they must officially and publicly commit to a rigid mathematical rule (e.g., "The 3rd digit will ALWAYS be even for stable and odd for beta"). If Emby officially documents this rule and promises not to break it, the TrueNAS maintainer can safely rewrite the update script to match that logic and turn the updates back on.


PLEASE FIX THIS

This will never be fixed I'm afraid. It does seem like either the emby team can't fix it won't fix it or doesn't want to fix it. Or they need help lots of help. Maybe emby higher ups should reach out to the community to get the best of the best coders so they can have more help than they have now inside so the customers can get the program they deserve and expect to get. But what do I know I'm a lifetime license holder have been for years and I'm just a user bot a coder at all wish I did coding so I could fix all their mistakes. I am tired of thinking I'm getting a stable release and getting a beta I was under the impression that wheb I installed scale fresh install and installed emby I was getting a stable release of emby nope got a beta and it's been that way since then too. Irs a real shame whoever is in charge if the enby truenas scale app roll out seems to be purposely doing this to hurt emby and I dint know of emby sees it or recognizes this happening. I really hope this gets fixed soon but I'm not holding my breath like I aaid I don't think emby has enough employees right now and need lots of help.  Have a good one

[sskwhiteshadow 6]

I feel the same way. Lifetime license but omg talk about not getting something like this straight is crazy and for 8 months now. 

sad and disappointing

[Shiroyama 1]

On 14/04/2026 at 20:33, Luke said:

The stable version number will always be a little lower than beta.

Ok, So stable 4.9.5.0 is out and it includes all the updates up to 4.10.0.11-beta? And if so, "Add new spotlight home screen section option (requires Emby Server 4.10+)" is also working on the new stable release?

[psxlover 37]

2 hours ago, Shiroyama said:

And if so, "Add new spotlight home screen section option (requires Emby Server 4.10+)" is also working on the new stable release?

Based on Luke's comments in the announcement post it is not part of the 4.9.5.0 release

 

[Tom1241 0]

The latest app version on TrueNAS is still showing 4.9.4.1. Docker shows the latest as 4.9.5.0. Relying on the TrueNAS catalog really is painful.

https://hub.docker.com/r/emby/embyserver

https://apps.truenas.com/catalog/emby_stable/

[psxlover 37]

@Tom1241since Emby release a new stable version, and it is using the discussed naming scheme (last digit is "0"), I believe that it is now on Truenas / Stavros' responsibility to update the Truenas app.

[psxlover 37]

Truenas app catalog seems to have been updated and 4.9.5.0 is now available