Meilisearch v1.19.0stable Released Aug 25, 2025
Impact Score: 5/10

Meilisearch: v1.19.0 ๐Ÿชธ

Source available โ€” automated, not human-reviewed

Component: meilisearch ยท Channel: stable. Automated analysis, not a compatibility certification. How this works.

Analysis updated: 2026-11-01.

Compatibility not verified โ€” check source notes
๐Ÿ“„ .MD
โšก Executive Summary (TL;DR)

Meilisearch v1.19.0. Source highlight: Automatically shard documents to scale horizontally

Who Does This Impact? (Role-Based Analysis)

๐Ÿ’ป Software Engineers & Devs

Check the source notes against the package and APIs you use before upgrading.

๐Ÿ“Š Product & Engineering Leads

Use the documented changes to assess relevance to your product; release frequency alone is not a quality measure.

โš™๏ธ DevOps & Security

Verify the target version, runtime requirements and rollback procedure in the official documentation.

๐Ÿ”ง Bug Fixes & Patches (1)

  • Takes the allowed max memory of the container when computing the max memory to use (#5729) @martin-g
๐Ÿ“„ View Raw Release Notes (Original Developer Log)
## ๐Ÿš€ Enhancements ## Automatically shard documents to scale horizontally Meilisearch can now automatically distribute documents between multiple instances using the new **sharding** feature. Find a guide on implementing sharding in [the documentation](https://www.meilisearch.com/docs/learn/multi_search/implement_sharding). > [!NOTE] > Sharding is an advanced feature available exclusively in **Meilisearch Enterprise Edition (EE)**. > > The EE features are governed by the [**Business Source License 1.1**](https://github.com/meilisearch/meilisearch/blob/v1.19.0/LICENSE-EE), which allows you to use, test, and develop with sharding for free in non-production environments. Please [reach out to us](mailto:[email protected]) before using it in production. Added in #5784 by @dureuill ## ๐Ÿ› Bug Fixes * Takes the allowed max memory of the container when computing the max memory to use (#5729) @martin-g โค๏ธ Huge thanks to our contributors: @Kerollmops, @dureuill and @martin-g.