Pimcore
A patch of seven fixes, one of which stops the log tables growing forever.
A side-by-side editorial comparison of Litmus and n8n — release velocity, themes, recent moves, and the top alternatives to consider.
The blog feed says nothing; Litmus's real changelog sits undated in a separate scrape.
Two sources sit under this product and they do not agree. The dated feed is a deliverability and lifecycle education blog — footers, rebrands, preference centres, birthday sends, holiday prep — and announces no product change; one entry even carries the rebrand article's excerpt instead of its own, a scrape defect. The undated rows are the actual Litmus release archive: Email Guardian, Integrated Insights, Litmus Personalize, Litmus Assistant, and two dozen smaller Builder, Proof, and testing releases.
n8n's patch stream is now mostly AI-builder work wearing bug-fix labels
n8n releases patch versions every few days across several concurrent lines, with generated notes that are almost entirely a Bug Fixes list. The 2.36 and 2.37 lines have been infrastructure and credential work — proxy environment variables applied across processes, domain-restricted credentials fixed and backported, execution ids threaded through dynamic-credential storage, glibc staged into the distroless runner image. The current 2.38.1 release is far larger, and its body hits the 8,000-character storage ceiling.
Two sources sit under this product and they do not agree. The dated feed is a deliverability and lifecycle education blog — footers, rebrands, preference centres, birthday sends, holiday prep — and announces no product change; one entry even carries the rebrand article's excerpt instead of its own, a scrape defect. The undated rows are the actual Litmus release archive: Email Guardian, Integrated Insights, Litmus Personalize, Litmus Assistant, and two dozen smaller Builder, Proof, and testing releases.
Read from the release archive rather than the blog, Litmus has moved outward from pre-send rendering QA in three directions: analytics that join ESP performance data to its own engagement data, open-time personalization acquired with Kickdynamic, and generative drafting inside the editor. The in-ESP testing integrations — Klaviyo, Adobe Journey Optimizer, Intilery — are the same capability extended market by market. Apple's Mail Privacy Protection forced a run of measurement-integrity work that the later reporting features depend on.
Because the archive carries no dates, ordering and recency are unreadable and no confident call on the next release is available from this feed. What can be said is that the analytics and personalization lines each accumulated follow-on releases after their originating launch, so further work on those two surfaces is the pattern the entries support.
n8n releases patch versions every few days across several concurrent lines, with generated notes that are almost entirely a Bug Fixes list. The 2.36 and 2.37 lines have been infrastructure and credential work — proxy environment variables applied across processes, domain-restricted credentials fixed and backported, execution ids threaded through dynamic-credential storage, glibc staged into the distroless runner image. The current 2.38.1 release is far larger, and its body hits the 8,000-character storage ceiling.
Read past the Bug Fixes heading and the centre of gravity has moved to the AI builder: tool call events emitted for Workflow, HTTP Request and Code tools, several tools from one provider addable through the UI, agent artifacts in the preview tab bar, managed credits preserved while building, and a requirement that a model be configured before the assistant accepts a prompt. Alongside it, trigger reliability keeps being hardened — Gmail no longer loses queued messages mid-poll or misses email when more than a hundred arrive between polls.
The credits and model-configuration items point at metering and guardrails around the AI builder rather than at its capabilities, so expect the next releases to keep filling in how agent usage is accounted for before new agent features land.
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 Litmus or n8n.
A patch of seven fixes, one of which stops the log tables growing forever.
A twenty-item day, and most of it is the import path finally behaving.
SalesBlink is making agents first-class clients, and just broke API-key MCP connections to do it
Postscript is handing SMS marketing to an agent that decides each subscriber's next message
Systeme.io's feed sells the consolidation story, one customer at a time.
Mailtrap pulls cross-client render testing into the sandbox that already holds the mail.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Litmus and n8n 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. Litmus and n8n 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 Litmus alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "Litmus alternatives" section above for the current picks, or visit /alternatives/litmus for the full list with editorial commentary on each.
Top n8n alternatives in Mkt Auto are ranked by recent ship velocity. Browse the "n8n alternatives" section above for the current picks, or visit /alternatives/n8n for the full list with editorial commentary on each.