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 Prometheus and Protocol Buffers — release velocity, themes, recent moves, and the top alternatives to consider.
Prometheus 3.14 ships the release candidate unchanged, duration expressions now on by default
3.14.0 is byte-identical to the 3.14.0-rc.0 body published a week earlier, so the stable cut carries exactly what the candidate previewed: PromQL duration expressions enabled by default with the feature flag retired, first_over_time promoted to stable, Oracle Cloud service discovery added, and a set of start-timestamp experiments still behind flags. The performance work is the substantive half, with regex matchers on literal alternations, native histogram scrape parsing down roughly 49% in allocations, and a recursion-free text parser that closes a stack-overflow path on hostile exposition.
Protobuf is using Edition 2026 to tighten defaults the language spent years leaving loose.
The v36.0 release candidates are the active work, with v35.x still receiving point releases. The through-line is Edition 2026: default symbol visibility becomes STRICT, a naming-style enforcement feature landed to prevent field name collisions, and reserving field number INT_MAX is now disallowed. Alongside that, a new json_options.proto and json_enumvalue_options.proto are being added to release artifacts across C++, Java, and upb, and deprecation warnings are accumulating on older reflection and generic-service APIs.
3.14.0 is byte-identical to the 3.14.0-rc.0 body published a week earlier, so the stable cut carries exactly what the candidate previewed: PromQL duration expressions enabled by default with the feature flag retired, first_over_time promoted to stable, Oracle Cloud service discovery added, and a set of start-timestamp experiments still behind flags. The performance work is the substantive half, with regex matchers on literal alternations, native histogram scrape parsing down roughly 49% in allocations, and a recursion-free text parser that closes a stack-overflow path on hostile exposition.
The project is spending its feature budget on start timestamps, appearing across PromQL, TSDB encoding, and remote write V2 in the same release but held behind use-start-timestamps and histograms-st-encoding. Everything else follows the established rhythm of promoting one experimental function per cycle and adding a cloud discovery source. The API deprecations are being staged carefully, warning now and rejecting at the next major.
Start timestamps are the obvious candidate to lose their feature flags once the encoding and remote-write halves have run together, and the stats parameter values now warned on will be rejected in the next major.
The v36.0 release candidates are the active work, with v35.x still receiving point releases. The through-line is Edition 2026: default symbol visibility becomes STRICT, a naming-style enforcement feature landed to prevent field name collisions, and reserving field number INT_MAX is now disallowed. Alongside that, a new json_options.proto and json_enumvalue_options.proto are being added to release artifacts across C++, Java, and upb, and deprecation warnings are accumulating on older reflection and generic-service APIs.
Editions are being used as the mechanism to change defaults that could never be changed in proto2 or proto3 without breaking the world — visibility, naming, reserved ranges. Each edition becomes a place to make the strict choice the default for new code while old code stays on its declared edition. In parallel the build story is consolidating on Bazel 9, with Bazel 7 support dropped in v35.0 and per-language Bazel 9 test coverage added across csharp, objc, php, python, rust, and upb.
Expect v36.0 to reach general availability from the current rc line, carrying the Edition 2026 defaults and the JSON options gencode with it. The deprecation warnings on generic services and Reflection enum accessors mark the next removals rather than this release's.
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 Prometheus or Protocol Buffers.
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 Prometheus alternatives → · See all Protocol Buffers alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Prometheus and Protocol Buffers 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. Prometheus and Protocol Buffers 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 Prometheus alternatives in DevOps are ranked by recent ship velocity. Browse the "Prometheus alternatives" section above for the current picks, or visit /alternatives/prometheus for the full list with editorial commentary on each.
Top Protocol Buffers alternatives in DevOps are ranked by recent ship velocity. Browse the "Protocol Buffers alternatives" section above for the current picks, or visit /alternatives/protobuf for the full list with editorial commentary on each.