Traefik
Traefik's 2.11 line spends August fixing the names it generates for Kubernetes resources.
A side-by-side editorial comparison of ggh4x and NGINX — release velocity, themes, recent moves, and the top alternatives to consider.
Handed its axis and legend guides to ggplot2 and legendry, and kept the facets
ggh4x is a set of ggplot2 extensions — nested and manual facets, per-facet scales, forced panel sizes, and statistics such as stat_difference() and stat_rle(). Its guide functions, once a substantial part of the package, are deprecated: 0.3.0 redirected users to ggplot2's own guide arguments and to the legendry package, and 0.3.1 made the deprecated functions return plain equivalents. What remains as this package's own territory is facetting and panel layout.
nginx returns to feature work with PROXY v2 upstream writes, and quietly adds JSON to core.
1.31.4 is the first mainline release in months that is not primarily a CVE response. It adds PROXY protocol version 2 write support for stream upstreams, special-cases the Host header for HTTP and gRPC upstreams, and tightens QUIC flow control on RESET_STREAM final sizes. Underneath those, core gained data model and JSON serialization libraries that nothing in this release consumes.
ggh4x is a set of ggplot2 extensions — nested and manual facets, per-facet scales, forced panel sizes, and statistics such as stat_difference() and stat_rle(). Its guide functions, once a substantial part of the package, are deprecated: 0.3.0 redirected users to ggplot2's own guide arguments and to the legendry package, and 0.3.1 made the deprecated functions return plain equivalents. What remains as this package's own territory is facetting and panel layout.
The handover was signalled well in advance. Version 0.2.5 set the guides' lifecycle to 'questioning' and said outright they might migrate to a new package once ggplot2 overhauled its guide system, and 0.3.0 executed that eighteen months later. Much of the rest of the changelog is anticipatory compatibility work for upcoming ggplot2 releases, the standing cost of being an extension package. Releases carry playful codenames that say nothing about their contents.
The deprecated guide functions are scheduled for removal in the next non-hotfix release, so expect that next; continued work should concentrate on facets and panel sizing, the areas neither ggplot2 nor legendry has absorbed.
1.31.4 is the first mainline release in months that is not primarily a CVE response. It adds PROXY protocol version 2 write support for stream upstreams, special-cases the Host header for HTTP and gRPC upstreams, and tightens QUIC flow control on RESET_STREAM final sizes. Underneath those, core gained data model and JSON serialization libraries that nothing in this release consumes.
The five preceding releases were security releases: three CVEs in July across both branches, an HTTP/2 and gRPC buffer overflow and an HTTP/3 use-after-free in June. Against that run, 1.31.4 reads as the project returning to feature work, with F5 contributors visible across the stream and upstream changes and four first-time contributors landing fixes. The JSON and data-model libraries are the item worth watching, since general serialization is not something a proxy needs for proxying.
Those libraries have no consumer in this release, so the plausible next move is a feature that uses them, such as structured status output or configuration, rather than another round of parser hardening.
Other Infra & APIs 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 ggh4x or NGINX.
Traefik's 2.11 line spends August fixing the names it generates for Kubernetes resources.
ESPHome closes the 2026.8 cycle, but the release body is a bare link to the real notes.
A genomics workhorse whose visible release feed stops dead in mid-2020.
The R phone-number package stopped only parsing numbers and started asking them where they are.
A Venn diagram package whose public release notes say almost nothing — including about its copyright cleanup.
A Shiny app for choosing the right ordinal test reached CRAN in a single 90-minute burst of tags.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. NGINX is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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. NGINX is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top ggh4x alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ggh4x alternatives" section above for the current picks, or visit /alternatives/ggh4x for the full list with editorial commentary on each.
Top NGINX alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "NGINX alternatives" section above for the current picks, or visit /alternatives/nginx for the full list with editorial commentary on each.