Liquidsoap
Liquidsoap opens its 2.5 line with subtitles as a first-class content type and a streaming server of its own
A side-by-side editorial comparison of Erlang/OTP and Vitest — release velocity, themes, recent moves, and the top alternatives to consider.
Three OTP branches move as one release train, and SSH and epmd carry the security load.
Erlang/OTP is patching three branches in lockstep — 29 as current, 28 and 27 as maintenance — with each fix set published as a trio within minutes of itself. The window is dominated by security work in the network-facing applications: OTP 29.0.4 carried six CVEs including an epmd denial-of-service mitigation, and the 4 August trio brought SSH into line with RFC 4253 by rejecting packets not aligned to the cipher block size, with a timing-safe packet-discard path for CBC ciphers. A regression in the previous patch that stopped epmd binding to localhost was fixed in the same trio.
Vitest 5 is in bug-fix mode: the second RC is almost entirely hardening
rc.2 carries one feature — a custom title for the GitHub Actions summary — and otherwise fixes the failure modes the RC period surfaced. The browser mode gets most of it: failing instead of hanging when the browser stops responding, exiting cleanly on disconnect during cancellation, and triggering Chromium GC when disk runs low. Snapshot evaluation moved server-side to work under a no-unsafe-eval CSP, and the UI now requires auth for coverage reports and every subtree request.
Erlang/OTP is patching three branches in lockstep — 29 as current, 28 and 27 as maintenance — with each fix set published as a trio within minutes of itself. The window is dominated by security work in the network-facing applications: OTP 29.0.4 carried six CVEs including an epmd denial-of-service mitigation, and the 4 August trio brought SSH into line with RFC 4253 by rejecting packets not aligned to the cipher block size, with a timing-safe packet-discard path for CBC ciphers. A regression in the previous patch that stopped epmd binding to localhost was fixed in the same trio.
The maintenance pattern is unusually strict: 27, 28 and 29 receive the same trouble reports on the same day, so the effective support window is wide and sites on older majors are not being pushed forward by security pressure. Where the fixes land is consistent — ssh, ssl, crypto, public_key and erts account for nearly every changed application across these releases, which is the distribution epmd and the TLS/SSH stack impose on a distributed runtime. The CBC timing mitigation in particular is an old class of attack being closed properly rather than papered over.
Expect the next patch trio to follow the same shape — a small set of trouble reports applied to all three branches simultaneously — with ssh and ssl the most likely applications to change. Nothing in these entries indicates feature work landing on the patch branches; that stays on the next major.
rc.2 carries one feature — a custom title for the GitHub Actions summary — and otherwise fixes the failure modes the RC period surfaced. The browser mode gets most of it: failing instead of hanging when the browser stops responding, exiting cleanly on disconnect during cancellation, and triggering Chromium GC when disk runs low. Snapshot evaluation moved server-side to work under a no-unsafe-eval CSP, and the UI now requires auth for coverage reports and every subtree request.
The v5 line has spent four betas and two candidates reshaping config resolution, projects, mocking defaults, and the benchmark API; this candidate adds nothing to that surface and only stabilizes it. The concentration of browser-mode and pool fixes says that is where the remaining risk sits, and where real-world RC adoption is finding edges.
On this trajectory the next tag is either a final 5.0.0 or one more candidate, with browser mode the deciding factor rather than any remaining API work.
Other DevOps 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 Erlang/OTP or Vitest.
Liquidsoap opens its 2.5 line with subtitles as a first-class content type and a streaming server of its own
Appwrite keeps reworking its own plumbing — Go CLI, SquashFS mounts, and an MCP layer that refreshes itself
FusionAuth's feed publishes version numbers; whether they carry news is a coin flip.
Sanity ships across every package at once, and the agent-facing surface moves fastest.
The 6.1 candidate arrives carrying the same notes the beta already shipped in June.
Auth0 hands tenants a throttle on their own noisy apps
See all Erlang/OTP alternatives → · See all Vitest alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Erlang/OTP and Vitest 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. Erlang/OTP and Vitest 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 DevOps products to evaluate alongside.
Top Erlang/OTP alternatives in DevOps are ranked by recent ship velocity. Browse the "Erlang/OTP alternatives" section above for the current picks, or visit /alternatives/erlang-otp for the full list with editorial commentary on each.
Top Vitest alternatives in DevOps are ranked by recent ship velocity. Browse the "Vitest alternatives" section above for the current picks, or visit /alternatives/vitest for the full list with editorial commentary on each.