n8n
n8n ships 2.40.0 with AI builder hardening while laying v3 storage migration groundwork
A side-by-side editorial comparison of Craft CMS and Pimcore — release velocity, themes, recent moves, and the top alternatives to consider.
Craft CMS 6.0 is a full Laravel rewrite — alpha releases are shipping breaking API changes every week.
Craft CMS 6.0 is mid-alpha, with a complete architectural shift from Yii to Laravel as its foundation. The alpha cadence has been weekly or better, each release removing legacy event-based APIs and replacing them with modern Laravel patterns — service containers, Artisan commands, Inertia/Vue CP pages. Image handling was overhauled to intervention/image with libvips support and new format coverage (HEIC, JPEG XL). The 5.x line continues receiving security and bug patches in parallel.
Pimcore's 2026.2 branch is in steady bug-fix mode, targeting storage races, workflow correctness, and image processing.
Pimcore is in a maintenance-focused release cycle for the 2026.2 branch, shipping weekly patch releases that address edge-case failures across three recurring areas: storage and file system race conditions, workflow state inconsistencies, and image processing (Imagick colorspace, thumbnail format aliases, missing binary detection). There are no new features in this window — it is purely stabilization work. A parallel legacy branch (12.3.12.x) received one bug fix targeting deserialization and dateRange assertion correctness.
Craft CMS 6.0 is mid-alpha, with a complete architectural shift from Yii to Laravel as its foundation. The alpha cadence has been weekly or better, each release removing legacy event-based APIs and replacing them with modern Laravel patterns — service containers, Artisan commands, Inertia/Vue CP pages. Image handling was overhauled to intervention/image with libvips support and new format coverage (HEIC, JPEG XL). The 5.x line continues receiving security and bug patches in parallel.
Every alpha release trades backward compatibility for a cleaner platform foundation. Plugin authors are absorbing breaking changes in batches, with a compatibility shim (yii2-adapter) as the bridge. The CP frontend is moving steadily to Inertia/Vue, and the fluent component APIs suggest a design system consolidation. Once the alpha phase closes, Craft 6 will require full plugin rewrites — the ecosystem disruption is the price of the architectural cleanup.
The next alpha releases will focus on stabilizing the plugin API surface and filling gaps in the Inertia/Vue CP migration. A beta tag is plausible within 2-3 months if the breaking-change cadence slows. Expect the yii2-adapter compatibility layer to become a first-party migration guide rather than a long-term support path.
Pimcore is in a maintenance-focused release cycle for the 2026.2 branch, shipping weekly patch releases that address edge-case failures across three recurring areas: storage and file system race conditions, workflow state inconsistencies, and image processing (Imagick colorspace, thumbnail format aliases, missing binary detection). There are no new features in this window — it is purely stabilization work. A parallel legacy branch (12.3.12.x) received one bug fix targeting deserialization and dateRange assertion correctness.
The 2026.2 patch cadence is defensive: fixing subtle failures that would cause data corruption or unexpected behavior in production environments. The storage-race and workflow-rollback fixes suggest hardening for multi-process environments — containerized deployments and distributed storage backends. The quality and specificity of the bugs being addressed (circular reference guards, colorspace compositing edge cases, file system contention) indicate mature platform maintenance rather than new capability development.
The patch cadence will continue through 2026.2.x as remaining edge cases surface in production. Based on the recurring DAM-related fixes, the next releases will continue addressing asset metadata handling and thumbnail generation reliability — these are the themes appearing most frequently across the patch series.
Other Mkt Auto 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 Craft CMS or Pimcore.
n8n ships 2.40.0 with AI builder hardening while laying v3 storage migration groundwork
Buttondown gives publishers granular AI-crawler controls as daily fixes continue
Gumloop ships Gumball, background subagents, and a model router in two weeks—each one changes how agents work.
Formidable Forms adds form abandonment analytics and deepens its multilingual and add-on ecosystem.
Moosend's only visible signal is blog content—no public product changelog available
Lemlist ships domain purchasing, real-time lead scoring, and phone enrichment — the cold-email tool is becoming infrastructure.
See all Craft CMS alternatives → · See all Pimcore alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — cms — within Mkt Auto. Craft CMS and Pimcore 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. Craft CMS and Pimcore 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 Mkt Auto products to evaluate alongside.
Top Craft CMS alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Craft CMS alternatives" section above for the current picks, or visit /alternatives/craft-cms for the full list with editorial commentary on each.
Top Pimcore alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Pimcore alternatives" section above for the current picks, or visit /alternatives/pimcore for the full list with editorial commentary on each.