GitHub
At Universe, GitHub folds Copilot into Enterprise seats and lets Copilot Fusion pick the model.
A side-by-side editorial comparison of GeoServer and Sanity — release velocity, themes, recent moves, and the top alternatives to consider.
GeoServer patches three branches at once, with the new work reserved for the 3.0 line
Three releases landed within about an hour of each other — 2.27.6, 2.28.5 and 3.0.1 — the coordinated multi-branch pattern this project uses for maintenance. The shared payload is a set of security-adjacent fixes: a GeoFence SQL query missing its spatial filter when only CLIP applies, wrong CRS axis order when clipping WFS 2.0.0 features, and the XXE vulnerability in features-templating backported to the oldest branch. Only 3.0.1 carries new capability: a Keycloak role service and security-aware GeoWebCache tile caching.
Sanity's MCP server now advertises itself to agents through a server card and llms.txt.
Sanity shipped three MCP server releases in two days. 2.44.0 makes the server discoverable through a /.well-known server card, an HTML or markdown landing page, robots.txt and llms.txt, and cuts CPU per request. 2.43.0 adds an undeploy_schema tool and deprecates workspaceName for schema selection. 2.42.2 fixes validation against deployed schemas and refuses patches that would change a document's _type.
Three releases landed within about an hour of each other — 2.27.6, 2.28.5 and 3.0.1 — the coordinated multi-branch pattern this project uses for maintenance. The shared payload is a set of security-adjacent fixes: a GeoFence SQL query missing its spatial filter when only CLIP applies, wrong CRS axis order when clipping WFS 2.0.0 features, and the XXE vulnerability in features-templating backported to the oldest branch. Only 3.0.1 carries new capability: a Keycloak role service and security-aware GeoWebCache tile caching.
The branch split is doing what it is supposed to. The 2.x lines get fixes and nothing else, while the 3.0 line — which broke the monolith into extensions — is where authentication and cache-security work now lands. The recurring theme across all three is access control at the data layer: GeoFence filtering, secured feature sources, and now tile caching that respects security rather than serving from an unaware cache.
Expect the next coordinated round to follow the same shape, with 3.0.2 taking further security-aware caching and identity-provider work while the 2.x branches receive only the shared fixes.
Sanity shipped three MCP server releases in two days. 2.44.0 makes the server discoverable through a /.well-known server card, an HTML or markdown landing page, robots.txt and llms.txt, and cuts CPU per request. 2.43.0 adds an undeploy_schema tool and deprecates workspaceName for schema selection. 2.42.2 fixes validation against deployed schemas and refuses patches that would change a document's _type.
The MCP server is becoming the main way agents read and write Sanity content, and the work has shifted from adding tools to making it safe and findable: guarded patches, accurate safety annotations, full schema lifecycle and discovery metadata. Studio and Manage continue alongside it with speed work and admin features for larger organizations.
Expect workspaceName to be removed after the migration period, and more guardrails on write tools such as patch_documents.
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 GeoServer or Sanity.
At Universe, GitHub folds Copilot into Enterprise seats and lets Copilot Fusion pick the model.
CodeRabbit moves its review status to a GitHub check run and keeps Deep Scan coverage fresh.
Arrow Rust 60.1.0 ships, redacting Parquet encryption keys and adding read-ahead planning.
Zed 1.26 adds Pyrefly for Python and debugs WebAssembly from the JavaScript debugger.
Kubernetes moves conformance from the cluster to the workloads running on it.
Manticore 31.0.7 undoes a 2x COUNT(DISTINCT) slowdown its own collation fix caused.
See all GeoServer 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. GeoServer and Sanity 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. GeoServer and Sanity 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 DevOps products to evaluate alongside.
Top GeoServer alternatives in DevOps are ranked by recent ship velocity. Browse the "GeoServer alternatives" section above for the current picks, or visit /alternatives/geoserver 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.