rsconnect
The deployment client is being rebuilt around credentials it never has to store.
A side-by-side editorial comparison of git2r and vdiffr — release velocity, themes, recent moves, and the top alternatives to consider.
git2r stopped vendoring libgit2 and now expects it on the system
git2r is the R binding to libgit2. The defining recent change is packaging, not API: 0.35.0 removed the bundled libgit2 source entirely and made a system install of libgit2 1.0 or newer a hard requirement, with a macOS fallback that downloads a checksum-verified static build. 0.36.2 follows up with proxy support and clearer build-time error messages.
vdiffr finished its job in 2021 and has been tracking compilers ever since.
vdiffr generates deterministic SVG snapshots so plot changes show up as test failures. Its recent history is almost entirely toolchain: UCRT Windows compatibility twice, a revert to C++11 to work around a GCC issue, and renaming the internal SVG device so it stops colliding with svglite. The only functional additions in view are snapshot variants in 1.0.8 and a testthat fix so snapshots are no longer auto-deleted when a test errors or skips. The last release was October 2024.
git2r is the R binding to libgit2. The defining recent change is packaging, not API: 0.35.0 removed the bundled libgit2 source entirely and made a system install of libgit2 1.0 or newer a hard requirement, with a macOS fallback that downloads a checksum-verified static build. 0.36.2 follows up with proxy support and clearer build-time error messages.
The package is trading install convenience for a maintainable build, and the releases since are about softening that edge — better diagnostics when the requirement is unmet, documented system dependencies, platform-specific build configuration. The API itself grows slowly and only where the underlying libgit2 exposes something new.
Expect further build-configuration and diagnostics work on the unbundled setup, with API additions arriving only as thin wrappers over libgit2 features.
vdiffr generates deterministic SVG snapshots so plot changes show up as test failures. Its recent history is almost entirely toolchain: UCRT Windows compatibility twice, a revert to C++11 to work around a GCC issue, and renaming the internal SVG device so it stops colliding with svglite. The only functional additions in view are snapshot variants in 1.0.8 and a testthat fix so snapshots are no longer auto-deleted when a test errors or skips. The last release was October 2024.
The package reached its intended shape at 1.0.0, when snapshot management moved to testthat and vdiffr shed most of its own R and JavaScript code to become a reproducible SVG engine and nothing more. There is not much left to add to that, and the release stream since reads accordingly: it moves when a compiler, an R version, or testthat moves. For a testing dependency this is a healthy end state, though it does mean the package inherits whatever the graphics engine does to snapshot stability.
The entries do not support predicting a feature release. The likely next change is a compatibility fix prompted by a compiler or a testthat change, as every release since 1.0.2 has been.
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 git2r or vdiffr.
The deployment client is being rebuilt around credentials it never has to store.
A package whose release calendar is written by whoever ships the next Rtools.
DNSControl v5 is feature complete and counting down to an August ship date
highr is finished software: one-line releases every year or two
casdoor ships several times a day, mostly tightening organization boundaries.
downlit's HTML contract was set in 0.4.0; every release since tracks R itself.
See all git2r alternatives → · See all vdiffr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. git2r and vdiffr 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. git2r and vdiffr 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 git2r alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "git2r alternatives" section above for the current picks, or visit /alternatives/git2r for the full list with editorial commentary on each.
Top vdiffr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "vdiffr alternatives" section above for the current picks, or visit /alternatives/vdiffr for the full list with editorial commentary on each.