Verdaccio
Verdaccio's v9 pre-release counter reaches 41, and the notes still say nothing
A side-by-side editorial comparison of Lima and Terragrunt — release velocity, themes, recent moves, and the top alternatives to consider.
Lima 2.3 nears release, with a Windows path that drops QEMU and a new TUI
Lima v2.3.0-rc.0 is out with an experimental HCS driver that removes the QEMU dependency on Windows hosts, block device attachment for VZ guests on macOS, and experimental shared, host and bridged networks on Linux hosts. limactl menu adds a menu-based interface, which now opens when limactl runs on a terminal without arguments. The default Ubuntu template moves to 26.10.
Terragrunt 1.2's last candidate finishes eleven experiments and locks down state buckets.
Terragrunt v1.2.0-rc3, dated mid-October, is declared the final candidate: unless a blocker appears, v1.2.0 ships with its contents. The cycle completes eleven experiments, among them OCI, block-iteration, azure-backend and optional-hooks. Two changes need attention: base64gzip() now returns the Go 1.27 encoder's output, which can trigger resource replacements, and S3 bootstrapping no longer adds the RootAccess bucket policy statement.
Lima v2.3.0-rc.0 is out with an experimental HCS driver that removes the QEMU dependency on Windows hosts, block device attachment for VZ guests on macOS, and experimental shared, host and bridged networks on Linux hosts. limactl menu adds a menu-based interface, which now opens when limactl runs on a terminal without arguments. The default Ubuntu template moves to 26.10.
The any-guest, any-host direction now reaches all three desktop platforms in one release, and each host gets a feature suited to its own virtualization stack. The menu interface is a different kind of addition: it aims at people who do not want to memorize the CLI. LFX mentees and outside contributors continue to carry much of this work, and the project's experimental-first labeling still applies to the biggest items.
A 2.3.0 final is the next step after rc.0. The HCS driver and Linux network modes should stay experimental there, following the pattern earlier platform additions took.
Terragrunt v1.2.0-rc3, dated mid-October, is declared the final candidate: unless a blocker appears, v1.2.0 ships with its contents. The cycle completes eleven experiments, among them OCI, block-iteration, azure-backend and optional-hooks. Two changes need attention: base64gzip() now returns the Go 1.27 encoder's output, which can trigger resource replacements, and S3 bootstrapping no longer adds the RootAccess bucket policy statement.
The graduation model has repeated at a larger scale: six experiments in v1.1, eleven in v1.2. The candidates ran as stabilization, with fixes concentrated in the CAS, the catalog and the Provider Cache Server. Each breaking change also ships with an escape hatch, base64gzip_compat() or enable_bucket_root_access, which shows how seriously the project treats its 1.0 guarantees.
v1.2.0 final is the next release, since rc3 says only regression or urgent fixes will land first. It has not appeared in this feed in the 18 days since rc3.
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 Lima or Terragrunt.
Verdaccio's v9 pre-release counter reaches 41, and the notes still say nothing
Snort 3.12.4 pairs a long memory-safety pass with detection speed work
Nineteen patches into 3.2, HAProxy's ingress controller is mostly bumping dependencies
Honeycomb is working on the first ten minutes, not just the incident
Talos 1.15's alpha keeps moving: a silent containerd config trap and declarative CPU control
Pinot 1.6 adds SQL DDL and vector backends, and now needs Java 25 to run its services.
See all Lima alternatives → · See all Terragrunt alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Lima and Terragrunt 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. Lima and Terragrunt 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 Infra & APIs products to evaluate alongside.
Top Lima alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Lima alternatives" section above for the current picks, or visit /alternatives/lima for the full list with editorial commentary on each.
Top Terragrunt alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Terragrunt alternatives" section above for the current picks, or visit /alternatives/terragrunt for the full list with editorial commentary on each.