[Release] weaviate/weaviate v1.36.22

Fixes, not features. That's the headline here. Weaviate v1.36.22 focuses on improving the reliability of its existing functionalities rather than introducing new capabilities. The LSM segment cleanup and WAL recovery crash-safety improvements are crucial for teams that depend on data integrity and uptime. But remember: these are foundational fixes, not flashy new tools. It's about making sure the engine runs smoothly, especially when things go wrong.

Here's the thing: if you're already using Weaviate in production, you likely depend on it for critical applications. The search-time HNSW entrypoint repair and vector normalization during reassignment are solid enhancements. They’ll help avoid headaches during vector queries, especially when dealing with dynamic data updates. However, without benchmarks or performance metrics accompanying these fixes, it’s hard to assess the real-world impact.

What they're not saying is how these changes translate into measurable performance improvements against competitors like Pinecone, Milvus, or Faiss. If your team is eyeing these alternatives, keep in mind that fixes alone won't sway your decision; you need to see tangible benefits in speed and reliability.

For teams already invested in Weaviate, this update is a must-apply to ensure stability. However, if you're evaluating options for a new vector database, this release lacks enough compelling news to shift the needle. It’s time to assess whether the existing stack meets your needs or if a more feature-rich competitor could serve you better.

Evaluate this update, but don’t expect it to be a game-changer. I recommend applying this update but keeping your eyes open for competitive offerings that may provide more value right now.