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 FusionAuth and pyjanitor — release velocity, themes, recent moves, and the top alternatives to consider.
FusionAuth's feed publishes version numbers; whether they carry news is a coin flip.
FusionAuth releases every four to eight weeks, but the changelog entries are inconsistent: three of the last six carry nothing but an upgrade-guide link, while the ones that do have notes describe substantial standards and security work. The last documented release, 1.67.0, added RFC 8707 resource scoping so tokens issued by OAuth endpoints can be bound to specific resources. Before it, two consecutive releases tightened API key requirements — 1.65.0 for installation-wide endpoints, 1.66.0 extending the same rule to webhooks it had missed.
pyjanitor breaks its pandas 2.x floor and returns from a four-month quiet spell.
After a stretch of dependency-only releases through spring, v0.32.24 is the first substantive release since March. It carries a 5.9x speedup in find_replace by swapping .apply() for .map(), two new options on the cleaning verbs (strip_whitespace on clean_names, drop_first on expand_column), a cheaper polars expand path, and a hard requirement of pandas 3.0 and Python 3.11. The releases before it were the groupby migration arc — by methods moved onto groupby objects, an assign method added there, and pd.col column references supported.
FusionAuth releases every four to eight weeks, but the changelog entries are inconsistent: three of the last six carry nothing but an upgrade-guide link, while the ones that do have notes describe substantial standards and security work. The last documented release, 1.67.0, added RFC 8707 resource scoping so tokens issued by OAuth endpoints can be bound to specific resources. Before it, two consecutive releases tightened API key requirements — 1.65.0 for installation-wide endpoints, 1.66.0 extending the same rule to webhooks it had missed.
Where the notes are readable, the direction is standards conformance and closing security defaults that were too permissive, accepting breaking changes to do it. FusionAuth has been willing to make an enabled identity provider's linking strategy immutable and to require global API keys where tenant keys used to work — changes that break running deployments in exchange for a tighter default. What cannot be read from this feed is where the last two releases fit, because they shipped without notes.
The pattern of hardening endpoint-by-endpoint suggests further scope narrowing wherever tenant-level keys still reach installation-level effects. Any read on 1.68.0 and 1.69.0 would be guesswork — the entries carry no content.
After a stretch of dependency-only releases through spring, v0.32.24 is the first substantive release since March. It carries a 5.9x speedup in find_replace by swapping .apply() for .map(), two new options on the cleaning verbs (strip_whitespace on clean_names, drop_first on expand_column), a cheaper polars expand path, and a hard requirement of pandas 3.0 and Python 3.11. The releases before it were the groupby migration arc — by methods moved onto groupby objects, an assign method added there, and pd.col column references supported.
Two arcs are converging. The API arc keeps folding pyjanitor's verbs into pandas' own grouping and column-reference idioms rather than maintaining a parallel vocabulary, with mutate formally deprecated along the way. The maintenance arc has now committed to pandas 3.0 as the floor, which closes off the 2.x user base but frees the library to use the new implementation instead of working around two majors at once. The polars work continues quietly beside both.
With pandas 3.0 established as the baseline, expect the next releases to lean on it directly — retiring compatibility shims and continuing the deprecation of the older standalone verbs in favor of the groupby-attached forms.
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 FusionAuth or pyjanitor.
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
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
Vitest 5 is in bug-fix mode: the second RC is almost entirely hardening
See all FusionAuth alternatives → · See all pyjanitor alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. FusionAuth and pyjanitor are shipping at a similar cadence (velocity 2.5 vs 2.5, 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. FusionAuth and pyjanitor are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.
Top FusionAuth alternatives in DevOps are ranked by recent ship velocity. Browse the "FusionAuth alternatives" section above for the current picks, or visit /alternatives/fusionauth for the full list with editorial commentary on each.
Top pyjanitor alternatives in DevOps are ranked by recent ship velocity. Browse the "pyjanitor alternatives" section above for the current picks, or visit /alternatives/pyjanitor for the full list with editorial commentary on each.