Buttondown
A twenty-item day, and most of it is the import path finally behaving.
A side-by-side editorial comparison of Litmus and Pimcore — 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.
A patch of seven fixes, one of which stops the log tables growing forever.
2026.2.11 is a maintenance patch with no new function. The notable item is an application log archive table that grew on every maintenance run — an unbounded growth bug rather than a cosmetic one. The rest is DataObject and editor correctness: parent query-table data no longer copied into fields that do not support inheritance, empty language permission strings normalised to null in the workspace, UrlSlug edit-mode data accepted in associative form, a workflow note field that threw when not submitted, and an orphaned rel=noopener fragment leaking into WYSIWYG text.
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.
2026.2.11 is a maintenance patch with no new function. The notable item is an application log archive table that grew on every maintenance run — an unbounded growth bug rather than a cosmetic one. The rest is DataObject and editor correctness: parent query-table data no longer copied into fields that do not support inheritance, empty language permission strings normalised to null in the workspace, UrlSlug edit-mode data accepted in associative form, a workflow note field that threw when not submitted, and an orphaned rel=noopener fragment leaking into WYSIWYG text.
The 2026.2 line has been shipping weekly, and the previous three patches all carried some function alongside their fixes. This one does not, which reads as the line settling rather than slowing — the reports it answers are concentrated in DataObject inheritance and workspace permissions, the areas the recent releases touched. Thumbnail clipping failures moving from info to error logging is the same instinct: make the existing behaviour observable before changing it.
Weekly patches on the 2026.2 line have been consistent, so 2026.2.12 within the week is the expectation. Whether it returns to carrying features depends on the DataObject reports, and the notes do not say.
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 Pimcore.
A twenty-item day, and most of it is the import path finally behaving.
n8n's patch stream is now mostly AI-builder work wearing bug-fix labels
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.
See all Litmus alternatives → · See all Pimcore alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Litmus 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. Litmus 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 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 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.