Gravity Forms
Gravity Forms patches reCAPTCHA and Partial Entries after its 3.2 Repeater release.
A side-by-side editorial comparison of pgBackRest and Slurm — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Slurm's newest entry is a test case, not a release; 26.05.5 is still current.
Slurm maintains three branches (25.05, 25.11, 26.05). On September 2 it shipped coordinated security releases on all three fixing seven CVEs, including an operator-to-administrator privilege escalation and SQL injection via cluster names. 26.05.5 on October 13 returned to ordinary fixes. The newest feed item is a testsuite commit checking that step cancels in --stepmgr jobs record the job owner rather than root.
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.
Slurm maintains three branches (25.05, 25.11, 26.05). On September 2 it shipped coordinated security releases on all three fixing seven CVEs, including an operator-to-administrator privilege escalation and SQL injection via cluster names. 26.05.5 on October 13 returned to ordinary fixes. The newest feed item is a testsuite commit checking that step cancels in --stepmgr jobs record the job owner rather than root.
Slurm's cadence is monthly point releases on the 26.05 line with occasional coordinated security drops across all supported branches. The test commit points at accounting accuracy for step-manager jobs as current work.
A 26.05.6 point release in November is likely, possibly including the --stepmgr cancel accounting fix the new test covers.
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 pgBackRest or Slurm.
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.
Argo CD cuts 3.6.0 on the release branch and ships its first patch within a day
TomEE opens a 10.3 line and a second EE11 milestone on the same day, with no notes
See all pgBackRest alternatives → · See all Slurm alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. pgBackRest and Slurm 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. pgBackRest and Slurm 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 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.
Top Slurm alternatives in DevOps are ranked by recent ship velocity. Browse the "Slurm alternatives" section above for the current picks, or visit /alternatives/slurm for the full list with editorial commentary on each.