Skipper
Skipper patches its second filter advisory in a week, this one in the OPA request-body filter.
A side-by-side editorial comparison of Payload CMS and Woodpecker CI — release velocity, themes, recent moves, and the top alternatives to consider.
Payload v4 beta 3 adds Next.js cache components and moves TanStack Start to React Flight.
Payload 4.0 is on its fourth beta. beta.3 adds support for Next.js cache components, with the admin rendered at request time, and switches the TanStack Start adapter to React Flight for RSC responses, a breaking change for that adapter. The rest is fixes: per-locale validation when writing all locales, live-preview and bulk-upload UI bugs, and a Drizzle locale index tweak. The beta.0 bundle of admin redesign, TanStack Start support and the rewritten MCP server remains the release's core.
Woodpecker CI hardens agent security and forge handling through its 3.14 release candidates
Woodpecker is iterating through 3.14.0 release candidates focused on security and agent/forge robustness: sanitizing agent-introduced state changes and log streaming, blocking registration as arbitrary agents, restricting log access, and cleaning up the Forge interface. Dependency security bumps (axios, otel, follow-redirects) and a lodash removal run throughout.
Payload 4.0 is on its fourth beta. beta.3 adds support for Next.js cache components, with the admin rendered at request time, and switches the TanStack Start adapter to React Flight for RSC responses, a breaking change for that adapter. The rest is fixes: per-locale validation when writing all locales, live-preview and bulk-upload UI bugs, and a Drizzle locale index tweak. The beta.0 bundle of admin redesign, TanStack Start support and the rewritten MCP server remains the release's core.
The betas are converging on two framework adapters with comparable rendering models: Next.js gains cache-components support while TanStack Start moves onto React Flight. Breaking changes are now confined to the newer adapter, and most of each beta is fixes and repo tooling, which points toward a stable 4.0.
Expect further weekly betas with adapter fixes and migration docs before 4.0 stable. The entries still give no stable date, and further TanStack Start breaking changes remain possible.
Woodpecker is iterating through 3.14.0 release candidates focused on security and agent/forge robustness: sanitizing agent-introduced state changes and log streaming, blocking registration as arbitrary agents, restricting log access, and cleaning up the Forge interface. Dependency security bumps (axios, otel, follow-redirects) and a lodash removal run throughout.
The 3.14 line reads as a security-and-internals hardening cycle, tightening the agent trust boundary and forge integration rather than pushing features. The earlier 3.11 line shows the more typical mix of per-repo config features and fixes.
Expect 3.14.0 to converge to a stable release after the RC series, continuing the agent-security and forge-handling focus.
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 Payload CMS or Woodpecker CI.
Skipper patches its second filter advisory in a week, this one in the OPA request-body filter.
Aviator moves from merging code to judging it: Verify checks PRs against their stated intent.
Infisical stores PAM session recordings in S3 and backs internal CAs with AWS KMS keys.
Airflow 3.4.0 reaches its second beta a day after the common-ai provider hit 1.0.
ESPHome adds a sixth 2026.10 beta, one more than 2026.9 needed before its .0.
Semgrep adds Objective-C as an alpha target, its first new language since Dart went GA.
See all Payload CMS alternatives → · See all Woodpecker CI alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Payload CMS is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. 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. Payload CMS is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top Payload CMS alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Payload CMS alternatives" section above for the current picks, or visit /alternatives/payload-cms for the full list with editorial commentary on each.
Top Woodpecker CI alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Woodpecker CI alternatives" section above for the current picks, or visit /alternatives/woodpecker-ci for the full list with editorial commentary on each.