Meilisearch
A week of walking back v1.52.0 while the sharding work ships on a parallel tag
A side-by-side editorial comparison of Heroku and Sanity — release velocity, themes, recent moves, and the top alternatives to consider.
Runtime bumps fill the changelog; the managed Postgres line is where Heroku actually moves.
Day to day, Heroku's changelog is language-runtime upkeep: Python, Node, Ruby, Go, PHP, JRuby and .NET point releases, buildpack refreshes for Pipenv and uv, and periodic rebuilds of the Heroku-22, Heroku-24 and Heroku-26 stacks now maintained in parallel. The exception is the managed database. Postgres 18 entered beta on 14 July and reached general availability on 4 August, and Heroku deprecated Postgres 15 on the same day.
Sanity is making the fastest path into its platform an agent typing a CLI command.
Sanity releases across many independently versioned packages at once — Studio, @sanity/ui, the MCP server, the React App SDK and Media Library — often several in the same week. Early August carried two directional moves within a day of each other: @sanity/ui v4.0.0 went ESM-only behind subpath imports, and Studio v6.9.2 shipped Sanity New, account-less project creation explicitly aimed at AI agents. The rest of the cadence is steady corrective work on Studio and Media Library.
Day to day, Heroku's changelog is language-runtime upkeep: Python, Node, Ruby, Go, PHP, JRuby and .NET point releases, buildpack refreshes for Pipenv and uv, and periodic rebuilds of the Heroku-22, Heroku-24 and Heroku-26 stacks now maintained in parallel. The exception is the managed database. Postgres 18 entered beta on 14 July and reached general availability on 4 August, and Heroku deprecated Postgres 15 on the same day.
The platform is running two clocks at once. One is a near-daily maintenance cadence that keeps supported runtimes current and rarely changes behaviour. The other is a deliberate, publicly staged lifecycle for the data services, where a major version is walked from beta to GA and the version three releases behind is retired in the same announcement. Kafka is on the same track, with 2.8 and 3.7 deprecations and a revised version-support policy posted in late July.
Given that Postgres 15's deprecation was announced alongside 18's general availability, the next concrete step is a published end-of-life date and forced-upgrade window for Postgres 15. The runtime bumps will continue at their current weekly rhythm.
Sanity releases across many independently versioned packages at once — Studio, @sanity/ui, the MCP server, the React App SDK and Media Library — often several in the same week. Early August carried two directional moves within a day of each other: @sanity/ui v4.0.0 went ESM-only behind subpath imports, and Studio v6.9.2 shipped Sanity New, account-less project creation explicitly aimed at AI agents. The rest of the cadence is steady corrective work on Studio and Media Library.
Two currents run in parallel. The platform is being made agent-addressable: the MCP server can now run Sanity CLI commands without a shell, patches documents transactionally, and refuses to write to Studio-managed schemas, while project creation itself no longer requires an account. At the same time the front-end stack is being modernized without much regard for laggards — ESM-only, Node.js 22.12, React 19.2, styles as an imported stylesheet, deprecated APIs removed outright. Sanity is optimizing for teams and agents starting fresh rather than for consumers pinned to old toolchains.
Sanity New issues temporary credentials with a 72-hour window before a project must be claimed, and the MCP server is iterating weekly; the observable pattern points to the claim-and-expiry flow and the MCP schema guardrails being the next pieces to firm up. Whether agent-created projects convert into paid ones is not something these entries show.
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 Heroku or Sanity.
A week of walking back v1.52.0 while the sharding work ships on a parallel tag
Two branches running in parallel: 3.13 LTS on security patches, 3.14 promoting experiments to stable.
The blog has become a teaching channel, with the real releases arriving as Gateway API and deprecation notices.
Vitest 5 reaches RC after a beta line that reworked config, mocking defaults, and the browser runner.
A dependency-bump treadmill interrupted by the first real accessibility push in months.
Jenkins is shrinking its own war file and rebuilding its UI, one weekly release at a time
See all Heroku alternatives → · See all Sanity alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Sanity is currently shipping more aggressively (velocity 7.5 vs 5.0), with 2 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. Sanity is currently shipping more aggressively (velocity 7.5 vs 5.0), with 2 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.
Top Heroku alternatives in DevOps are ranked by recent ship velocity. Browse the "Heroku alternatives" section above for the current picks, or visit /alternatives/heroku for the full list with editorial commentary on each.
Top Sanity alternatives in DevOps are ranked by recent ship velocity. Browse the "Sanity alternatives" section above for the current picks, or visit /alternatives/sanity for the full list with editorial commentary on each.