noVNC
noVNC ships about once a year, and its betas and finals carry identical notes.
A side-by-side editorial comparison of Radarr and Lidarr — release velocity, themes, recent moves, and the top alternatives to consider.
Radarr is in steady maintenance, with one new download client the only visible addition
Radarr ships small builds on parallel develop and master branches, typically a handful of commits each. The recent stream is almost entirely correctness work — HTTP request disposal, deferred JSON deserialisation, malformed cookie handling, qBittorrent basic auth, an SQLite busy timeout raised to 1000ms — plus translation updates. The single functional addition is an RQBit download client.
Lidarr's release notes still tell you not to update Radarr — the fork's seams are showing.
Lidarr publishes auto-generated pre-release builds every few weeks, each carrying a handful of commits. The recent ones add rate limiting to Spotify lookup endpoints, fix basic auth and cookie reuse for qBittorrent, pull in Weblate translation updates and bump ImageSharp and MailKit. The boilerplate at the top of every entry warns against updating Radarr inside an existing container — text inherited from the upstream project and never changed.
Radarr ships small builds on parallel develop and master branches, typically a handful of commits each. The recent stream is almost entirely correctness work — HTTP request disposal, deferred JSON deserialisation, malformed cookie handling, qBittorrent basic auth, an SQLite busy timeout raised to 1000ms — plus translation updates. The single functional addition is an RQBit download client.
Version numbers are moving quickly through 6.1 to 6.4, but the changes behind them are patch-sized; the major.minor increments track branch mechanics rather than feature milestones. The work that is happening targets reliability under load and with third-party clients, which is where a long-running background service accumulates problems.
Expect the develop-branch build cadence to continue with further download client and indexer compatibility fixes; nothing here signals a larger release in preparation.
Lidarr publishes auto-generated pre-release builds every few weeks, each carrying a handful of commits. The recent ones add rate limiting to Spotify lookup endpoints, fix basic auth and cookie reuse for qBittorrent, pull in Weblate translation updates and bump ImageSharp and MailKit. The boilerplate at the top of every entry warns against updating Radarr inside an existing container — text inherited from the upstream project and never changed.
This is a project maintained rather than developed. Version numbers advance through build counts more than features, one release in this window contains nothing but a version bump, and the substantive work is defensive: staying within third-party rate limits, keeping torrent client authentication working, absorbing dependency updates. The metadata providers it depends on are where the pressure shows.
Expect continued small builds driven by external breakage — torrent client authentication changes and metadata provider limits are the two recurring sources here. The rate limiting added for Spotify suggests provider throttling is an active problem, so more of the same is the likeliest next move.
Other Collab products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Radarr or Lidarr.
noVNC ships about once a year, and its betas and finals carry identical notes.
Typst keeps widening past PDF — first accessibility, now HTML, MathML and multi-file output
Kodi's v22 'Piers' cycle is a long rebuild of playback, Blu-ray and PVR
pCloud's feed sells lifetime storage and Swiss privacy; the product changes stay off it.
SiYuan's 3.8 branch turns a local-first notebook into an agent-readable knowledge store.
Hive deepens its proofing stack for creative teams while teaching Buzz restraint
See all Radarr alternatives → · See all Lidarr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — maintenance — within Collab. Radarr and Lidarr are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Radarr and Lidarr are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Collab products to evaluate alongside.
Top Radarr alternatives in Collab are ranked by recent ship velocity. Browse the "Radarr alternatives" section above for the current picks, or visit /alternatives/radarr for the full list with editorial commentary on each.
Top Lidarr alternatives in Collab are ranked by recent ship velocity. Browse the "Lidarr alternatives" section above for the current picks, or visit /alternatives/lidarr for the full list with editorial commentary on each.