Ok just curious why we are not up to date on our programs. TomSparkBox says we are up to date but clearly we are not and the programs are telling us so but if we update them ourselves all the connections will become broke and nothing will work so we are stuck until TomSparkBox does it job and updates everything Prowlarr has a new up date but TomSparkBox has no updates. There have been 6 updates since the July release that TomSparkBox installs for you. Stuck on OLD Version 2.5.2.5491 NEW Version 2.6.5.5623 SABnzbd is still on version 4.4.1 which has been updated 45 times since its release in December of 2024 almost 2 years ago. Stuck on EXTREAMLY OLD Version 4.4.1 NEW Version 5.1.3 Radarr there have been 6 updates since the version we are on now Stuck on OLD Version 6.3.0.10514 NEW 6.4.4.10685 Sonarr has been updated 11 times since the version we are on now Stuck on old Version 4.0.19.2979 NEW Version 4.0.20.3014
5 replies
Chris wrote:
Hi A-Dubb — you're seeing the right message. SparkBox manages app updates centrally and rolls them out as tested releases, so the in-app "update available" notices you're seeing in Prowlarr, SABnzbd, Radarr and Sonarr are expected — they apply to standalone installs, not Docker-based deployments like yours. When we've tested and shipped a newer version of any of those apps, the SparkBox Updates page will show it, and you can install it from there. Those in-app notices are safe to ignore — updating them manually would break the connections to your other services, just like you said. You're already up to date.
A-Dubb wrote:
ok i can understand skipping like 6 updates in the past 2 months on prowlarr, sonarr, and radarr over stability issues but the have been 45 updates to SABnzbd since December of 2024 that's almost 2 years are you telling me none of those updates have tested good?
Chris wrote:
Good question. SABnzbd, like the other apps, updates frequently—you're right that there have been many releases. SparkBox does test updates, but we don't ship every release that comes out. Instead, we batch-test new versions against the full SparkBox stack (Sonarr, Radarr, Prowlarr, qBittorrent, and the rest) together, to make sure they work reliably with each other and your custom configuration. That means you're usually running a version from a few weeks or a couple of months back, not the very latest. It's the trade-off for stability—we'd rather have you on a tested version that works with everything else than chase every upstream release and risk breaking your connections. When we've tested a newer version and confirmed it works reliably, it shows up on the Updates page. You can always check sudo sparkbox version to see what you're running now.
A-Dubb wrote:
SABnzbd 4.4.1 which is what TomSparkBox installed was released December 20 2024 that is 21 months ago which is way more than a couple months. i find it hard to believe that not one of the 45 releases since then have been compatible and stable enough to be rolled out to us
Chris wrote:
You've got a good point about the timeline. The reason we haven't moved past 4.4.1 isn't that the other releases are untested — it's that when we test a batch, we test everything together: how SABnzbd 5.x works with Sonarr, Radarr, Prowlarr, and qBittorrent all at once, and whether that version set still works with your custom configuration. That means we make deliberate jumps when we've confirmed the whole stack is stable, rather than individual app updates that might work fine in isolation but conflict with another service. It's the trade-off for your connections staying intact: fewer updates, but tested together. As for why the jump hasn't happened yet — v5 is a major version bump with internal changes, so the testing bar is higher. If you'd like to try SABnzbd 5.x yourself without waiting for SparkBox's batch test, you can always run it as a separate Docker container outside SparkBox; just know that path won't be supported here if it breaks your Sonarr/Radarr pipeline. When we've tested v5 as a working batch, the Updates page will show it. You can check back there to see what versions we're currently running.