Gravity Forms
Gravity Forms patches reCAPTCHA and Partial Entries after its 3.2 Repeater release.
A side-by-side editorial comparison of Argo CD and pgBackRest — release velocity, themes, recent moves, and the top alternatives to consider.
Argo CD cuts 3.6.0 on the release branch and ships its first patch within a day
Argo CD has moved 3.6 out of candidates: the release branch was bumped to 3.6.0 on 3 November and a 3.6.1 patch followed the next day with a cherry-picked UI sidebar fix. The rc3 and rc4 candidates before it carried fixes for repo-server goroutine leaks, SOCKS5 SSH fetching, sharding and server-side diff, plus one new option for Dex TLS cipher suites.
pgBackRest 2.60 now stops a restore when a page checksum is bad
pgBackRest 2.60.0, released October 18, changes a default: restore now errors and stops if a restored file has an invalid page checksum, leaving the cluster unable to start until the restore is rerun, and expire refuses to proceed if the oldest retained backup would contain checksum errors. Setting checksum-page-error=n returns to warnings. The release also adds GCS Workload Identity Federation and prefetch for object-store reads. Two weeks earlier 2.59.3 fixed a bug that could generate weak encryption subkeys and salts when system random data failed.
Argo CD has moved 3.6 out of candidates: the release branch was bumped to 3.6.0 on 3 November and a 3.6.1 patch followed the next day with a cherry-picked UI sidebar fix. The rc3 and rc4 candidates before it carried fixes for repo-server goroutine leaks, SOCKS5 SSH fetching, sharding and server-side diff, plus one new option for Dex TLS cipher suites.
The 3.6 line is now in stable maintenance, so the next weeks should be small cherry-picked patches rather than features. The 3.5 cycle followed the same shape, with feature work concentrated in rc1 and later candidates limited to fixes.
Expect further 3.6.x patches with backported fixes; the entries do not yet show when a 3.7 candidate will start.
pgBackRest 2.60.0, released October 18, changes a default: restore now errors and stops if a restored file has an invalid page checksum, leaving the cluster unable to start until the restore is rerun, and expire refuses to proceed if the oldest retained backup would contain checksum errors. Setting checksum-page-error=n returns to warnings. The release also adds GCS Workload Identity Federation and prefetch for object-store reads. Two weeks earlier 2.59.3 fixed a bug that could generate weak encryption subkeys and salts when system random data failed.
The project is moving from reporting corruption to refusing to continue past it, a stricter stance that fits the root restriction in 2.59.0. Cloud identity continues too, with GCS joining the Azure and S3 work. Underneath, the code generation, documentation tools and test harness have moved from C and Perl to Python, and a documented release schedule and new website show the project formalizing how it runs.
Patches tracking PostgreSQL 19 should continue, as 2.59.2 did with 19beta4. Now that restore can fail on checksums, expect follow-up fixes or guidance for clusters where existing backups contain them.
Other DevOps 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 Argo CD or pgBackRest.
Gravity Forms patches reCAPTCHA and Partial Entries after its 3.2 Repeater release.
GitHub puts Copilot inside Xcode's own coding assistant, a week after JetBrains Air.
Workato gives MCP proxies per-user OAuth and opens a UK data center with its agent stack.
ServiceDesk Plus brings its Zoho-hosted Zia LLM to the Saudi Arabia data center.
TomEE opens a 10.3 line and a second EE11 milestone on the same day, with no notes
Slurm's newest entry is a test case, not a release; 26.05.5 is still current.
See all Argo CD alternatives → · See all pgBackRest alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Argo CD and pgBackRest 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. Argo CD and pgBackRest 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 DevOps products to evaluate alongside.
Top Argo CD alternatives in DevOps are ranked by recent ship velocity. Browse the "Argo CD alternatives" section above for the current picks, or visit /alternatives/argo-cd for the full list with editorial commentary on each.
Top pgBackRest alternatives in DevOps are ranked by recent ship velocity. Browse the "pgBackRest alternatives" section above for the current picks, or visit /alternatives/pgbackrest for the full list with editorial commentary on each.