ESPHome
ESPHome ships on a calendar, and the August beta train is now four builds deep.
A side-by-side editorial comparison of discretetests and gpkg — release velocity, themes, recent moves, and the top alternatives to consider.
Four years of releases land in four minutes as the changelog gets backfilled to GitHub
DiscreteTests computes exact p-values and their full support for discrete statistical tests, returning results as a class that carries the observations, the test statistic and the null distribution. All four visible releases were tagged within four minutes of each other on a single day in May 2026, in reverse order — 0.4.1 carries the earliest timestamp and 0.4.0 the latest — so this is a historical changelog being pushed to GitHub at once, not four days of work.
An R interface to GeoPackage that keeps sanding down its own API
gpkg gives R users a direct handle on GeoPackage files — the SQLite-based OGC container for vector and raster layers — through lazy table access, OGR/SQLite dialect queries and terra integration. Recent releases center on raster write ergonomics: automatic NoData selection via auto_nodata and an exported gpkg_default_nodata() following GDAL and terra conventions. Release bodies are cumulative, folding two or three versions into one entry.
DiscreteTests computes exact p-values and their full support for discrete statistical tests, returning results as a class that carries the observations, the test statistic and the null distribution. All four visible releases were tagged within four minutes of each other on a single day in May 2026, in reverse order — 0.4.1 carries the earliest timestamp and 0.4.0 the latest — so this is a historical changelog being pushed to GitHub at once, not four days of work.
Read by version rather than by timestamp, the package grew from binomial, Fisher, McNemar and Poisson tests into rank-based and resampling territory: Wilcoxon signed rank and rank sum, Mann-Whitney U, a conditional homogeneity test, then sign tests and a general permutation test with several built-in statistics. Alongside that the result class was extended to hold ragged observation lists and computational detail, the print output was rewritten on cli, and the old dot-separated function names were made defunct.
The permutation test with pluggable statistics is the most open-ended addition here, and adding further built-in statistics to it is the cheapest way to extend the package from where it now stands.
gpkg gives R users a direct handle on GeoPackage files — the SQLite-based OGC container for vector and raster layers — through lazy table access, OGR/SQLite dialect queries and terra integration. Recent releases center on raster write ergonomics: automatic NoData selection via auto_nodata and an exported gpkg_default_nodata() following GDAL and terra conventions. Release bodies are cumulative, folding two or three versions into one entry.
The package is still finding its interface shape, and most releases pair a small capability with a deprecation or signature change — destfile giving way to y, gpkg_create_dummy_features deprecated, vapour swapped out for gdalraster. The consistent direction is deferring to GDAL and terra conventions rather than inventing gpkg-specific behaviour, and pushing connection management out of users' hands. Cadence is roughly one release a year with dependency automation now in CI.
Expect further alignment of write-path defaults with GDAL conventions and continued deprecation-with-replacement of early argument names, with an ogr2ogr-style path for out-of-memory vector data flagged as a possibility rather than a commitment.
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 discretetests or gpkg.
ESPHome ships on a calendar, and the August beta train is now four builds deep.
rapr generalises its Rangeland Analysis Platform API access one endpoint at a time
A small B-Cubed utility for turning R Markdown into publishable docs
R's logging package handed to new maintainers and rebuilt from the inside out
Four dormant years end with a test fix, not a feature
A comorbidity-coding package relicenses to BSD and grows past the American coding systems
See all discretetests alternatives → · See all gpkg alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Infra & APIs. discretetests and gpkg are shipping at a similar cadence (velocity 0.0 vs 0.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. discretetests and gpkg are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top discretetests alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "discretetests alternatives" section above for the current picks, or visit /alternatives/discretetests for the full list with editorial commentary on each.
Top gpkg alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "gpkg alternatives" section above for the current picks, or visit /alternatives/gpkg for the full list with editorial commentary on each.