NGINX
nginx returns to feature work with PROXY v2 upstream writes, and quietly adds JSON to core.
A side-by-side editorial comparison of texor and Traefik — release velocity, themes, recent moves, and the top alternatives to consider.
The LaTeX-to-R-Markdown converter that stopped transcribing articles and started making them executable.
texor converts legacy R Journal articles from LaTeX into R Markdown, wrestling with the parts that never translate cleanly: numbering, cross-references, algorithm environments, and macros nobody outside the R Journal uses. Since 1.5.0 it can also emit figures as code chunks and tables as CSV read back through kable(), and target bookdown, litedown or biocstyle. The 2025 releases are repair work — pandoc keeps changing underneath it.
Traefik's 2.11 line spends August fixing the names it generates for Kubernetes resources.
The feed carries only the 2.11 maintenance line, and v2.11.55 is entirely bug fixes. Four of its seven items address generated-name collisions in the Kubernetes CRD provider: scoping Service names to their parent, an opt-in safe-naming mode, a guard against generated-name collisions, and a namespace restriction for default TLS resources. The remainder are a Gateway API router rule fix, a toggle to disable TLS options fallback, and dependency bumps.
texor converts legacy R Journal articles from LaTeX into R Markdown, wrestling with the parts that never translate cleanly: numbering, cross-references, algorithm environments, and macros nobody outside the R Journal uses. Since 1.5.0 it can also emit figures as code chunks and tables as CSV read back through kable(), and target bookdown, litedown or biocstyle. The 2025 releases are repair work — pandoc keeps changing underneath it.
Two expansions define the arc. 1.4.0 took on Sweave as a source format, opening the pre-Rmd back catalogue of literate R documents. 1.5.0 changed what comes out the other end, offering executable code chunks and data files where earlier versions produced flat markup. Both moves point the same way: toward converted articles that still compute rather than merely resemble the original. Everything since has been keeping that machinery working against pandoc's release cadence.
The last two releases were both triggered by upstream pandoc changes breaking numbering or Lua filters, so the next release is most likely more of the same; new output styles remain the plausible feature direction given how recently that list was extended.
The feed carries only the 2.11 maintenance line, and v2.11.55 is entirely bug fixes. Four of its seven items address generated-name collisions in the Kubernetes CRD provider: scoping Service names to their parent, an opt-in safe-naming mode, a guard against generated-name collisions, and a namespace restriction for default TLS resources. The remainder are a Gateway API router rule fix, a toggle to disable TLS options fallback, and dependency bumps.
This branch is in pure maintenance, and the concentration is the signal: name generation in the CRD provider produced enough collisions to justify four separate changes and a new opt-in naming scheme inside a patch release. The two releases before it were CVE responses touching CONNECT tunnel handling and ReplacePathRegex path sanitization. Nothing here indicates feature work on this line.
Expect further 2.11 patches on the same footing, security fixes and Kubernetes provider corrections, with the safe-naming option a candidate to become the default once it has soaked.
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 texor or Traefik.
nginx returns to feature work with PROXY v2 upstream writes, and quietly adds JSON to core.
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.
See all texor alternatives → · See all Traefik alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Traefik is currently shipping more aggressively (velocity 5.0 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. Traefik is currently shipping more aggressively (velocity 5.0 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 texor alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "texor alternatives" section above for the current picks, or visit /alternatives/texor for the full list with editorial commentary on each.
Top Traefik alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Traefik alternatives" section above for the current picks, or visit /alternatives/traefik for the full list with editorial commentary on each.