chore(deps): update getmeili/meilisearch docker tag to v1.41.0 by renovate[bot] · Pull Request #76 · erebe/personal-server

renovate · 2026-02-18T15:37:33Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Update	Change
getmeili/meilisearch	minor	`v1.11.1` → `v1.41.0`

Release Notes

meilisearch/meilisearch (getmeili/meilisearch)

`v1.41.0`: 🏈

Compare Source

✨ Enhancement

Support dynamic search rules with pinning by @YoEight in #6182
Introduce the Dynamic Search Rules (DSR) experimental feature, making it easy to promote the right content for the right searches with flexible, condition-based pinning. In this first version, rules can be triggered by query-based conditions such as empty queries or literal substring matches, as well as time windows. Multiple documents can be pinned in a defined order, and pins still work with filtering, pagination, facet distribution, hybrid search, and federated search.

Rules can be created or updated with PATCH /dynamic-search-rules/{uid} and removed with DELETE /dynamic-search-rules/{uid}. In this first version, a rule can define query- or time-based conditions and pin specific documents at fixed positions in the results list.
Example of rule creation/update
```
  // PATCH /dynamic-search-rules/featured-wireless-headphones
  {
    "description": "Promote featured products for wireless headphone searches",
    "active": true,
    "conditions": [
      { "scope": "query", "contains": "headphone" }
    ],
    "actions": [
      {
        "selector": { "indexUid": "products", "id": "featured-headphones-001" },
        "action": { "type": "pin", "position": 0 }
      },
      {
        "selector": { "indexUid": "products", "id": "featured-headphones-002" },
        "action": { "type": "pin", "position": 1 }
      }
    ]
  }
  
```

Default to useNetwork: true in sharded instances by @dureuill in #6278

This release contains breaking changes for users of the network experimental feature.

Search requests now use the network by default when (replicated) sharding is enabled

§ Breaking changes

When network.leader is set in the instance, useNetwork now defaults to true in search requests when omitted.

So, when a network is configured, the following:

Search request without an explicit useNetwork

// POST /indexes/movies/search
{
  "q": "Batman dark knight returns 1",
  "filter": "genres IN [Action, Adventure]",
  "facets": ["genres"],
  "limit": 5
  // No `useNetwork` is passed
}

is now equivalent to a federated search over multiples remotes so that all shards in the network are covered exactly once.

Equivalent federated search request

// POST /multi-search
{
    "federation": {
        "limit": 5,
        "facetsByIndex": {
            "movies": [
                "genres"
            ]
        },
        "merge": {}
    },
    // assuming 3 remotes 0, 1, 2 and 3 shards a, b, c such that
    // 0 owns a, b
    // 1 owns b, c
    // 2 owns c, a
    "queries": [
        {
            "indexUid": "movies",
            "federationOptions": {
                "remote": "0"
            },
            "q": "Batman dark knight returns 1",
            "filter": ["genres IN [Action, Adventure]", "_shard = a"]
        },
        {
            "indexUid": "movies",
            "federationOptions": {
                "remote": "0" // useNetwork picked remote 0 for both shard a and b
            },
            "q": "Batman dark knight returns 1",
		     "filter": ["genres IN [Action, Adventure]", "_shard = b"]
        },
        {
            "indexUid": "movies",
            "federationOptions": {
                "remote": "2"
            },
            "q": "Batman dark knight returns 1",
		     "filter": ["genres IN [Action, Adventure]", "_shard = c"]
        }
    ]
}

Responding with documents from all the shards:

Response

{
  "hits": [
    {
      "id": 123025,
      "title": "Batman: The Dark Knight Returns, Part 1",
      "overview": "Batman has not been seen for ten years. A new breed of criminal ravages Gotham City, forcing 55-year-old Bruce Wayne back into the cape and cowl. But, does he still have what it takes to fight crime in a new era?",
      "genres": [
        "Action",
        "Animation",
        "Mystery"
      ],
      "poster": "https://image.tmdb.org/t/p/w500/kkjTbwV1Xnj8wBL52PjOcXzTbnb.jpg",
      "release_date": 1345507200,
      "_federation": {
        "indexUid": "mieli",
        "queriesPosition": 2,
        "weightedRankingScore": 0.9894586894586894,
        "remote": "2"
      }
    },
    {
      "id": 142061,
      "title": "Batman: The Dark Knight Returns, Part 2",
      "overview": "Batman has stopped the reign of terror that The Mutants had cast upon his city.  Now an old foe wants a reunion and the government wants The Man of Steel to put a stop to Batman.",
      "genres": [
        "Action",
        "Animation",
        "Mystery"
      ],
      "poster": "https://image.tmdb.org/t/p/w500/arEZYd6uMOFTILne9Ux0A8qctMe.jpg",
      "release_date": 1357171200,
      "_federation": {
        "indexUid": "mieli",
        "queriesPosition": 1,
        "weightedRankingScore": 0.9894558963186414,
        "remote": "0"
      }
    },
    {
      "id": 16234,
      "title": "Batman Beyond: Return of the Joker",
      "overview": "The Joker is back with a vengeance, and Gotham's newest Dark Knight needs answers as he stands alone to face Gotham's most infamous Clown Prince of Crime.",
      "genres": [
        "Animation",
        "Family",
        "Action",
        "Science Fiction"
      ],
      "poster": "https://image.tmdb.org/t/p/w500/7RlBs0An83fqAuKfwH5gKMcqgMc.jpg",
      "release_date": 976579200,
      "_federation": {
        "indexUid": "mieli",
        "queriesPosition": 1,
        "weightedRankingScore": 0.9427964918160996,
        "remote": "0"
      }
    },
    {
      "id": 155,
      "title": "The Dark Knight",
      "overview": "Batman raises the stakes in his war on crime. With the help of Lt. Jim Gordon and District Attorney Harvey Dent, Batman sets out to dismantle the remaining criminal organizations that plague the streets. The partnership proves to be effective, but they soon find themselves prey to a reign of chaos unleashed by a rising criminal mastermind known to the terrified citizens of Gotham as the Joker.",
      "genres": [
        "Drama",
        "Action",
        "Crime",
        "Thriller"
      ],
      "poster": "https://image.tmdb.org/t/p/w500/qJ2tW6WMUDux911r6m7haRef0WH.jpg",
      "release_date": 1216166400,
      "_federation": {
        "indexUid": "mieli",
        "queriesPosition": 1,
        "weightedRankingScore": 0.5784178187403994,
        "remote": "0"
      }
    },
    {
      "id": 49026,
      "title": "The Dark Knight Rises",
      "overview": "Following the death of District Attorney Harvey Dent, Batman assumes responsibility for Dent's crimes to protect the late attorney's reputation and is subsequently hunted by the Gotham City Police Department. Eight years later, Batman encounters the mysterious Selina Kyle and the villainous Bane, a new terrorist leader who overwhelms Gotham's finest. The Dark Knight resurfaces to protect a city that has branded him an enemy.",
      "genres": [
        "Action",
        "Crime",
        "Drama",
        "Thriller"
      ],
      "poster": "https://image.tmdb.org/t/p/w500/vzvKcPQ4o7TjWeGIn0aGC9FeVNu.jpg",
      "release_date": 1342396800,
      "_federation": {
        "indexUid": "mieli",
        "queriesPosition": 2,
        "weightedRankingScore": 0.5772657450076805,
        "remote": "2"
      }
    }
  ],
  "query": "Batman dark knight returns 1",
  "processingTimeMs": 173,
  "limit": 5,
  "offset": 0,
  "estimatedTotalHits": 47,
  "facetDistribution": {
    "genres": {
      "Action": 46,
      "Adventure": 15,
      "Animation": 34,
      "Comedy": 3,
      "Crime": 14,
      "Drama": 6,
      "Family": 15,
      "Fantasy": 8,
      "Horror": 1,
      "Mystery": 4,
      "Romance": 1,
      "Science Fiction": 14,
      "TV Movie": 4,
      "Thriller": 4,
      "Western": 1
    }
  },
  "facetStats": {},
  "requestUid": "019bbcf4-a609-7701-8d82-d370611adfb3",
  "remoteErrors": {}
}

This change allows to naturally query all the documents in a sharded context.
When network.leader is not present (in particular, when no network was defined), then the behavior is identical to previous versions.

useNetwork picks local instance if it owns the shard by @dureuill in #6287
To prevent unnecessary network activity, when deciding which remote to ask for a shard in a search over the network, Meilisearch will now always pick the local instance if it owns the shard.
More efficient FST building by @Kerollmops in #6279
It improves the construction of the word FST (word dictionary) by removing the need for a full scan of the word docids database. This should drastically improve the database's performance when inserting a large number of documents, even when inserting only a few.

🪲 Bug fixes

Handle empty VERSION file as missing by @themavik in #6275

🔩 Miscellaneous

Remap post processing targets for better benchmark readability by @ManyTheFish in #6285
Update the description of the get task's document payload route by @Kerollmops in #6284

New Contributors

@themavik made their first contribution in #6275

`v1.40.0`: 🦈

Compare Source

This release introduced support for the distinct attribute in federated search, enabling cross-index distinct attributes with facet distribution support. Additionally, significant performance improvements were delivered, including faster federated search (approximately 100ms faster), optimized JSON document generation for better handling of large documents and a much better memory usage for large workloads.

✨ Enhancement

Support distinct in federated search by @dureuill in #6214

The distinct attribute can now be passed to the federation object in federated search to apply a global, cross-index and cross-remote distinct computation to the results.

Example of a federated search request with distinct

{
  "federation": {
    "distinct": "genres", // ✨ NEW
    "facetsByIndex": { // recovering facet distribution is also supported with distinct
      "comics": [
        "genres"
      ],
      "movies": [
        "genres"
      ]
    },
    "mergeFacets": {} // merging facet distributions is also supported with distinct
  },
  "queries": [
    {
      "indexUid": "comics",
      "q": "batman",
      "attributesToRetrieve": ["title", "genres"],
      "useNetwork": true // distinct is also supported with network queries
    },
    {
      "indexUid": "movies",
      "q": "superman",
      "attributesToRetrieve": ["title", "genres"],
      "useNetwork": true
    }
  ]
}

Sample response to a federated search request with distinct

{
  "hits": [
    {
      "title": "Batman",
      "genres": [
        "Family",
        "Adventure",
        "Comedy",
        "Science Fiction",
        "Crime"
      ],
      "_federation": {
        "indexUid": "comics",
        "queriesPosition": 0,
        "weightedRankingScore": 1.0,
        "remote": "ms2"
      }
    },
    {
      "title": "Batman",
      "genres": [
        "Fantasy",
        "Action"
      ],
      "_federation": {
        "indexUid": "comics",
        "queriesPosition": 0,
        "weightedRankingScore": 1.0,
        "remote": "ms1"
      }
    },
    {
      "title": "Batman & Bill",
      "genres": [
        "Documentary"
      ],
      "_federation": {
        "indexUid": "comics",
        "queriesPosition": 0,
        "weightedRankingScore": 0.9848484848484848,
        "remote": "ms1"
      }
    },
    {
      "title": "Superman: Red Son",
      "genres": [],
      "_federation": {
        "indexUid": "movies",
        "queriesPosition": 1,
        "weightedRankingScore": 0.9848484848484849,
        "remote": "ms0"
      }
    },
    {
      "title": "Superman, Spider-Man or Batman",
      "genres": [
        "Drama"
      ],
      "_federation": {
        "indexUid": "movies",
        "queriesPosition": 1,
        "weightedRankingScore": 0.9848484848484849,
        "remote": "ms0"
      }
    }
  ],
  "processingTimeMs": 15,
  "limit": 5,
  "offset": 0,
  "estimatedTotalHits": 11,
  "facetDistribution": {
    "genres": {
      "Action": 1,
      "Adventure": 1,
      "Comedy": 3,
      "Crime": 2,
      "Documentary": 1,
      "Drama": 1,
      "Family": 1,
      "Fantasy": 1,
      "Horror": 2,
      "Romance": 1,
      "Science Fiction": 1,
      "Thriller": 1,
      "Western": 1
    }
  },
  "facetStats": {},
  "requestUid": "019d05c7-ea65-77a1-8274-22a8ba9e26db",
  "remoteErrors": {}
}

Note the following to apply the distinct attribute at the federation level:

Applying distinct at the query level at the same time as the federation level is disallowed and will return a HTTP 400 error.
The chosen distinct field will apply to all remotes and indexes, so it must be a filterable attribute for all participating remotes and indexes.
While Meilisearch attempts to compute the most accurate facet distribution, in distributed contexts this cannot be guaranteed as the distinct algorithm is not applied on all of the remote documents.

Improve performance of federated search by @dureuill in #6229

Improves performance of federated search: about 100ms faster for all requests. Improves reliability of the HTTP server: the server will no longer be blocked when too many federated search requests are being processed.
Optimize the generation of JSON documents by @Kerollmops in #6257

Addresses performance issues that users might encounter when requesting large documents. Additionally, performance is enhanced when users request only a small subset of fields from large documents.
Use the latest version of mimalloc to improve memory usage by @Kerollmops in #6201

Updates mimalloc from v2 to v3, improving memory sharing between threads and significantly reducing memory usage on large workloads. It also overrides the allocator to use mimalloc at linking time, allowing LMDB, Meilisearch, and other C libraries to share their allocations for better overall memory efficiency. @Kerollmops wrote a blog post about the story behind this improvement.
Add POST /tasks/compact for task queue compaction by @YoEight in #6193

Compacts the task queue database and reclaim space so new tasks can keep being enqueued, without deleting existing tasks. This feature is behind the taskQueueCompactionRoute experimental feature flag.

[!WARNING]
Once task queue compaction completes, all write operations are blocked until the server is restarted.

🔐 Security

Bump rustls-webpki from 0.103.8 to 0.103.10 in #6273
Bump tar from 0.4.44 to 0.4.45 in #6271
Bump actix-web-lab from 0.24.3 to 0.26.0 in #6218
Bump quinn-proto from 0.11.13 to 0.11.14 in #6217

🪲 Bug fixes

Check char boundaries when hiding secrets by @ManyTheFish in #6262
Network fixes by @dureuill in #6255
Override "default" source base url with the config one to support AWS bedrock OpenAI API by @dureuill in #5905
Fix panic on virtiofs filesystem by @itsamine27 in #6261

🔩 Miscellaneous

Add X-Accel-Buffering: no for /logs/stream route by @YoEight in #6268
Add link to documentation on --experimental-allowed-ip-networks parameter by @paulden in #6263
Update sysinfo version to 0.38.4 by @GuillaumeGomez in #6211
Add a no-agent AGENTS.md file to prevent excessive AI-generated PRs by @Kerollmops in #6256

New Contributors

@GuillaumeGomez made their first contribution in #6211
@itsamine27 made their first contribution in #6261

`v1.39.0`: 🐳

Compare Source

What's Changed

✨ Enhancement

🔬 Cross-index document hydration

Add a new ForeignKeys setting allowing to hydrate documents with documents coming from other indexes.

📓 Note: This implementation doesn't support a remote sharding environment

`foreignKeys` experimental feature

A new experimental feature, foreignKeys, has been added to the /experimental-feature route that must be set to true to activate the hydration.

curl -X PATCH 'http://127.0.0.1:7700/experimental-features' \
  -H 'Content-Type: application/json' \
  --data-binary '{"foreignKeys": true}'

`foreignKeys` index setting

A new index setting, foreignKeys, has been added to the /indexes/{index_uid}/settings:

// new setting, an array of foreign keys that allows multiple foreign relationships between indexes
"foreignKeys":  [
	{
		// the path in the JSON document containing foreign document ids
		"fieldName": "actors",
		
		// the UID of the foreign index containing the documents to fetch during hydration
        "foreignIndexUid": "actors"
	}
]

Example

With this new feature, a document shaped as follows:

{
  "id": 1,
  "title": "Forrest Gump",
  // Document IDs in foreign index
  "actors": [
    1
  ]
}

Will be hydrated as follows in a search response:

{
  "id": 1,
  "title": "Forrest Gump",
  "actors": [
	{
	  "id": 1,
	  "name": "Tom",
	  "familyName": "Hanks",
	  "birthDate": "1956-07-09"
	}
  ]
}

By @ManyTheFish in #6047

Disable proxy response buffering on Server-Sent Events (SSE)

Add X-Accel-Buffering: no on POST /chats/{workspace_uid}/chat/completions when the streaming mode is activated.
By @YoEight in #6228

🪲 Bug fixes

Fix a memory leak in the indexation pipeline by @Kerollmops in #6212

We fixed an important memory leak caused by an invalid use of bumpalo. If you've seen Meilisearch using more and more memory over time, this issue is no longer visible in the latest version. If you want to read more about the bumpalo-trap we felt in, here is a good summary. It looks like this leak was introduced in v1.12, so approximately a year ago...
Avoid losing tasks by applying deltas on the wtxn view by @Kerollmops in #6222

We addressed a small performance regression introduced in v1.38.1 that affected sending updates to the engine during task deletion. We've restored the task deletion performance to match v1.38.0 levels and ensured no race conditions occur while still allowing updates during deletion.

🔩 Miscellaneous

Ignore flaky test on windows by @dureuill in #6226
Fix small documentation mistakes by @ManyTheFish in #6205
Improve messaging when field is missing in the settings indexing pipeline by @Kerollmops in #6213

Full Changelog: meilisearch/meilisearch@v1.38.0...v1.39.0

`v1.38.2`: 🐍

Compare Source

Meilisearch v1.38.2 fixes a regression introduced in Meilisearch v1.38.0 where Meilisearch could sometimes stop processing tasks after an automatic task queue cleanup performed while more tasks where being added.

We recommend that all users in v1.38.0 and v1.38.1 migrate to v1.38.2.

Note that the dumpless upgrade process can take up to one minute before the HTTP server becomes available when migrating from a previous v1.38 version.

Full Changelog: meilisearch/meilisearch@v1.38.1...v1.38.2

`v1.38.1`: 🐍

Compare Source

Meilisearch v1.38.1 fixes a regression we have seen in task processing, which caused the engine to stop processing tasks.

🪲 Bug fixes

Revert, optimize, and fix task deletion. By @Kerollmops in #6219

Full Changelog: meilisearch/meilisearch@v1.38.0...v1.38.1

`v1.38.0`: 🐍

Compare Source

Meilisearch v1.38 drastically improves indexing performance for embeddings, cleans up the task queue of orphan tasks and batches, ensures they are correctly deleted now, fixes issues users may encounter with OpenAI or VoyageAI when generating embeddings, and improves the tooling for generating routes in the documentation.

✨ Enhancement

Embeddings: Use the latest version of hannoy with improved performances by @Kerollmops in #6184
We drastically reduced embedding indexing time by eliminating full database scans. It is more efficient to add a couple of embeddings to a large database now.
Tasks: Optimize and fix task deletion by @Mubelotix and @kerollmops in #5828

🪲 Bug fixes

Embedders: Fix the intermittent connection reset by peer errors when embedding documents or search queries using a remote embedder. By @dureuill in #6191

🔩 Miscellaneous

Enforce that routes appear in the reference documentation by @dureuill and @manythefish in #6200
The reference API is now generated from the source code, but it used to miss some actix-declared routes. It is now mandatory to attach a route when using the newly-provided routes::routes and routes::path macros, which ensures the route is added to the reference. Please refer to the documentation of the individual macros and the many examples throughout the codebase for more details.
Chore: remove verbose debug log on list documents by @StephaneRob in #6198
Add guide to CONTRIBUTING.md to test doc locally by @curquiza in #6180
Docs: capitalize LangChain and MCP in README by @24f1000637 in #6183
Docs: improve documentation of the parameters of the search route by @curquiza in #6194

New Contributors

@StephaneRob made their first contribution in #6198
@24f1000637 made their first contribution in #6183

`v1.37.0`

Compare Source

[!IMPORTANT]
This release contains breaking changes for users of the network experimental feature.

Meilisearch v1.37 introduces replicated sharding, removes the vectorStoreSetting experimental feature, stabilizes our new vector store for best performance, adds a security fix and miscellaneous improvements.

✨ Improvements

§ Replicated sharding

[!NOTE]
Replicated sharding requires Meilisearch Enterprise Edition (EE).

Users of Meilisearch Cloud, please contact support if you need replicated sharding.

Users of the Community Edition, please contact the sales if you want to use replicated sharding in production.

§ Breaking changes

network objects sent to the PATCH /network route must now contain at least one shard object containing at least one remote when leader is not null.

Existing databases will be migrated automatically when upgraded with --experimental-dumpless-upgrade when leader is not null, such that for each remote:

A shard with the same name as the remote is created
This shard has exactly one remote in its remotes list: the remote with the same name as the shard.

This change will not cause any document to be resharded.

To be able to upgrade without resharding, the migration uses the same name for remotes and for shards. However, in new configurations, we recommend using different names for shards and remotes.

Example of migration

For instance, the following network object:

{
  "leader": "ms-00",
  "self": "ms-01",
  "remotes": {
    "ms-00": { /* .. */ },
    "ms-01": { /* .. */ }
  }
}

is converted to:

{
  "leader": "ms-00",
  "self": "ms-01",
  "remotes": {
    "ms-00": { /* .. */ },
    "ms-01": { /* .. */ }
  },
  "shards": {  // ✨ NEW
    "ms-00": {  // shard named like the remote
      "remotes": ["ms-00"] // is owned by the remote
    },
    "ms-01": {
      "remotes": ["ms-01"]
    }
  }
}

Addition of `network.shards`

The network object for routes PATCH /network and GET /network now contains the new field shards, which is an object whose values are shard objects, and keys the name of each shard.

Each shard object contains a single field remotes, which is an array of strings, each string representing the name of an existing remote.

Convenience fields

The shard objects in PATCH /network contain the additional fields addRemotes and removeRemotes meant for convenience:

pass an array of remote names to shard.addRemotes to add these remotes to the list of remotes of a shard.
pass an array of remote names to shard.removeRemotes to remove these remotes from the list of remotes of a shard.
if present and non-null, shard.remotes will completely override the existing list of remotes for a shard.
if several of these options are present and non-null, then the order of application is shard.remotes, then shard.addRemotes, then shard.removeShards.

Adding a new shard with some remotes

// PATCH /network
{
  // assuming that remotes `ms-0`, `ms-1`, `ms-2` where sent in a previous call to PATCH /network
  "shards": {
    "s-a": { // new shard
      "remotes": ["ms-0", "ms-1"]
    }
  }
}

Remotes ms-0 and ms-1 own the new shard s-a.

Fully overriding the list of remotes owning a shard

// PATCH /network
{
  // assuming remotes `ms-0`, `ms-1`, `ms-2`
  // assuming shard `s-a`, owned by `ms-0` and `ms-1`
  "shards": {
    "s-a": {
      "remotes": ["ms-2"]
    }
  }
}

ms-2 is now the sole owner of s-a, replacing ms-0 and ms-1.

Adding a remote without overriding the list of remotes owning a shard

// PATCH /network
{
  // assuming remotes `ms-0`, `ms-1`, `ms-2`
  // assuming shard `s-a`, owned by `ms-2`
  "shards": {
    "s-a": {
      "addRemotes": ["ms-0"]
    }
  }
}

ms-0 and ms-2 are now the owners of s-a.

Removing a remote without overriding the list of remotes owning a shard

// PATCH /network
{
  // assuming remotes `ms-0`, `ms-1`, `ms-2`
  // assuming shard `s-a`, owned by `ms-0` and `ms-2`
  "shards": {
    "s-a": {
      "removeRemotes": ["ms-2"]
    }
  }
}

ms-0 is now the sole owner of s-a.

Entirely removing a shard from the list of shards

Set the shard to null:

// PATCH /network
{
  "shards": {
    "s-a": null
  }
}

Or set its remotes list to the empty list:

// PATCH /network
{
  "shards": {
    "s-a": {
      "remotes": []
    }
  }
}

`network.shards` validity

When network.leader is not null, each shard object in network.shards must:

Only contain remotes that exist in the list of remotes.
Contain at least one remote.

Additionally, network.shards must contain at least one shard.

Failure to meet any of these conditions will cause the PATCH /network route to respond with 400 invalid_network_shards.

Change in sharding logic

Documents are now sharded according to the list of shards declared in the network rather than the list of remotes. All remotes owning a shard will process the documents that belong to this shard, allowing for replication.

Example of replication

The following configuration defines 3 remotes 0, 1 and 2, and 3 shards A, B, C, such that each remote owns two shards, achieving replication (losing one remote does not lose any document).

{
  "leader": "0",
  "self": "0",
  "remotes": {
    "0": { /* .. */ },
    "1": { /* .. */ },
    "2": { /* .. */ }
  },
  "shards": {
    "A": {
      "remotes": ["0", "1"]
    },
    "B": {
      "remotes": ["1", "2"]
    },
    "C": {
      "remotes": ["2", "0"]
    }
  }
}

Full replication is supported by having all remotes own all the shards.
Unbalanced replication is supported by having some remotes own more shards than other remotes.
"Watcher" remotes are supported by having remotes that own no shards. Watcher remotes are not very useful in this release, and might be upgraded in a future release, so that they keep all documents without indexing them, allowing to "respawn" shards for other remotes.

`useNetwork` takes `network.shards` into account

When useNetwork: true is passed to a search query, it is expanded to multiple queries such that each shard declared in network.shards appears exactly once, associated with a remote that owns that shard.

This ensures that there is no missing or duplicate documents in the results.

`_shard` filters

When the network experimental feature is enabled, then it becomes possible to filter documents depending on the shard they belong to.

Given s-a and s-b the names of two shards declared in network.shards, then:

_shard = "s-a" in a filter parameter to the search or documents fetch will return the documents that belong to s-a.
_shard != "s-a" will return the documents that do not belong to s-a
_shard IN ["s-a", "s-b"] will return the documents that belong to s-a or to s-b.

You can use these new filters in manual remote federated search to create a partitioning over all shards in the network.

[!IMPORTANT]
To avoid duplicate or missing documents in results, for manually crafted remote federated search requests, all shards should appear in exactly one query.

[!TIP]
Search requests built with useNetwork: true already build a correct partitioning over shards. They should be preferred to manually crafted remote federated search requests in replicated sharding scenarios.

Update instructions

When updating your Meilisearch network using dumpless upgrade, please observe the following guidelines:

Do not call the PATCH /network route until all remotes of the network are finished updating
If using the search routes with useNetwork: true, call them on un-updated remotes. Calling it on already updated remotes will cause un-updated remotes to fail the search as they don't know about the _shard filters.

By @dureuill in #6128

§ Remove `vectorStoreSetting` experimental feature

The new HNSW vector store (hannoy) has been stabilized and is now the only supported vector store in Meilisearch.

As a result, updating to v1.37.0 will migrate all remaining legacy vector store indexes (using arroy) to hannoy, and the vectorStoreSetting experimental feature is no longer available.

By @Kerollmops in #6176

Improve indexing performance for embeddings

We removed a computationally expensive step from vector indexing.

On a DB with 20M documents, this removes 300s per indexing batch of 1100s.

By @Kerollmops in #6175

§ 🔒 Security

Bump mini-dashboard (local web interface) which
- now stores API key in RAM instead of in the localStorage
- bumps dependencies with potential security vulnerabilities

By @Strift and @curquiza in #6186 and #6172

§ 🔩 Miscellaneous

Mark Cargo.lock as not linguist-generated by @Kerollmops in #6181

Full Changelog: meilisearch/meilisearch@v1.36.0...v1.37.0

`v1.36.0`: 🐙

Compare Source

Version v1.36.0 introduces an exciting update to the ranking rules to improve the engine's relevance. It's actually the first time we've made such a change since v1.0, and we're really happy about this improvement!

✨ Enhancement

Introduce the attributeRank and wordPosition criteria by @Kerollmops in #6154, #6155, and #6164

We released two new ranking rules that Meilisearch had already been using internally for the attribute one, which is basically both ranking rules applied one after the other:
- attributeRank: A document is considered better if the query words match in a higher searchable attribute. It ignores the position of the query words in this attribute.
- wordPosition: A document is considered better if the query words match closer to the beginning of an attribute. The attribute rank is ignored by this rule.
We continue our policy of migrating everyone to use a homemade HNSW by introducing a new dumpless upgrade step that migrates index uses the old annoy vector store to the new Hannoy one. Changing the vector store backend affects the ranking score. This step can take a couple of minutes when the number of embeddings is high, and we recommend changing the vector store backend beforehand to gain more control if needed. To do so, you must enable the vectorStoreSetting experimental feature and set the vectorStore root setting to experimental.

🪲 Bug fixes

Fix search failing when using attributesToSearchOn on an empty index by @zen-zap in #5944

🔒 Security

Bump bytes from 1.11.0 to 1.11.1 by @dependabot[bot] in #6142
Bump jsonwebtoken from 9.3.1 to 10.3.0 by @dependabot[bot] in #6141
Bump time from 0.3.44 to 0.3.47 by @dependabot[bot] in #6144
Bump rsa from 0.9.9 to 0.9.10 by @dependabot[bot] in #6149

🔩 Miscellaneous

Improve OpenAPI docs and CIs to improve documentation experience by @curquiza in #6145

[!WARNING]
Breaking change: the meilisearch-openapi-mintlify.json file will not be available in the release assets anymore. If you were using it, please refer to the one that is now available in our public documentation repository.

GenAI contributing and PR template changes by @dureuill in #6140
Fix "test with almost all features" by @dureuill in #6139 and #6148
Allow any IP for SDK tests by @Strift in #6151
Improve output of the declarative tests, also in #6164

❤️ Thanks to @zen-zap for contributing to this release!

`v1.35.1`

Compare Source

🦋 Bug fixes

Meilisearch v1.35.1 fixes a possible task database corruption issue that would occur when using the S3 streaming snapshot method.

Users of the Community Edition do not need to upgrade as this feature is Enterprise Edition only
Affected users of the Cloud have been contacted.

Details

While snapshotting the task database, sending a task to Meilisearch could corrupt it. Index DBs were not affected, so manually rebuilding the task database fixes the corruption.

By @dureuill in #6160

Full Changelog: meilisearch/meilisearch@v1.35.0...v1.35.1

`v1.35.0`

Compare Source

Meilisearch v1.35.0 contains improvements to the observability of the search performance, a breaking change to the recently introduced POST /indexes/<index_uid>/fields route, and other bugfixes and improvements.

🌈 Improvements

Observe the search performance

The search routes accept a new field named showPerformanceDetails. When set to true, the search response contains a performance trace, allowing the user to better
understand what takes time during a search query.

impacted routes:

POST /indexes/<index_uid>/search
GET /indexes/<index_uid>/search
POST /multi-search
POST /indexes/<index_uid>/similar
GET /indexes/<index_uid>/similar

Search

routes: POST /indexes/<index_uid>/search and GET /indexes/<index_uid>/search

Request

new request parameters:

showPerformanceDetails: true/false (boolean)

example

{
	"q": "glass",
	"showPerformanceDetails": true
}

Response

new response field:

performanceDetails: {"<span>": "<human_duration>", .. } (map)

example

{
	"hits": [
		// hits ..
	],
	"query": "glass",
	"processingTimeMs": 5,
	"limit": 20,
	"offset": 0,
	"estimatedTotalHits": 1,
	"requestUid": "<uuid>",
	"performanceDetails": {
		"wait for permit": "295.29µs",
		"search > tokenize": "436.67µs",
		"search > resolve universe": "649.00µs",
		"search > keyword search": "515.71µs",
		"search > format": "288.54µs",
		"search": "3.56ms"
	}
}

Multi-search

route: POST /multi-search

Request

new request parameters:

queries.showPerformanceDetails: true/false (boolean)

example

"queries": [
	{
		"indexUid": "<index_uid>",
		"q": "glass",
		"showPerformanceDetails": true
	}
]

Response

new response field:

results.performanceDetails: {"<span>": "<human_duration>", .. } (map)

example

{
	"results": [
		{
			"indexUid": "<index_uid>",
			"hits": [
				// hits ..
			],
			"query": "glass",
			"processingTimeMs": 5,
			"limit": 20,
			"offset": 0,
			"estimatedTotalHits": 1,
			"requestUid": "<uuid>",
			"performanceDetails": {
				"wait for permit": "295.29µs",
				"search > tokenize": "436.67µs",
				"search > resolve universe": "649.00µs",
				"search > keyword search": "515.71µs",
				"search > format": "288.54µs",
				"search": "3.56ms"
			}
		}
	]
}

Federated Search

route: POST /multi-search

Request

new request parameters:

federation.showPerformanceDetails: true/false (boolean)

example

{
	"federation": { "showPerformanceDetails": true },
	"queries": [
		{
			"indexUid": "<index_uid>",
			"q": "glass"
		}
	]
}

Response

new response field:

performanceDetails: {"<span>": "<human_duration>", .. } (map)

example

{
	"hits": [
		// hits ..
	],
	"query": "glass",
	"processingTimeMs": 5,
	"limit": 20,
	"offset": 0,
	"estimatedTotalHits": 1,
	"requestUid": "<uuid>",
	"performanceDetails": {
		"wait for permit": "213.83µs",
		"search > tokenize": "171.67µs",
		"search > resolve universe": "257.63µs",
		"search > keyword search": "577.71µs",
		"search > format": "114.96µs",
		"search > federation > wait for remote results": "62.71µs",
		"search > federation > merge results": "120.04µs",
		"search > federation > merge facets": "53.42µs",
		"search > federation": "237.04µs",
		"search": "289.08ms"
	}
}

Similar

routes: POST /indexes/<index_uid>/similar and GET /indexes/<index_uid>/similar

Request

new request parameters:

showPerformanceDetails: true/false (boolean)

example

{
	"id": 143,
	"embedder": "manual",
	"showPerformanceDetails": true
}

Response

new response field:

performanceDetails: {"<span>": "<human_duration>", .. } (map)

example

{
	"hits": [
		// hits ..
	],
	"id": "143",
	"processingTimeMs": "[duration]",
	"limit": 20,
	"offset": 0,
	"estimatedTotalHits": 4,
	"performanceDetails": {
		"search > format": "244.92µs",
		"search": "1.25ms"
	}
}

By @ManyTheFish in #6132

Stabilize multithreaded post-processing of facets and prefixes

Multithreaded post-processing of facets and prefixes speeds-up indexing on multi-core machines.

Before v1.35.0, it could be disabled with an experimental feature.

Meilisearch v1.35.0 removes that experimental feature, resulting in the multithreaded post-processing being always enabled.

Cloud users upgrading to v1.35.0 will benefit from the speed-up.

By @ManyTheFish in #6130

🦋 Fixes

Breaking change: return pagination fields in `POST /indexes/<index_uid>/fields` route

[!WARNING]
Breaking change: The POST /indexes/<index_uid>/fields route now returns an object containing the results, offset, limit, and total fields instead of returning an array of results. This change allows to know how many fields match a given filter

Example: before/after

Before:

[
  // fields ..
]

After:

{
  "results": [
    // [fields .. ]
  ],
  "offset": 0,
  "limit": 20,
  "total": 0
}

By @ManyTheFish in #6126

`POST /indexes/<index_uid>/fields`: Fix pattern filtering when a parent field was matching a child pattern: `title` was matching the pattern `title.to*`.

Example: before/after

For the following request:

{
  "filter": {
    "attributePatterns": [
      "title.en"
    ]
  }
}

Before Response, title field is returned:

{
  "results": [
    {
      "name": "title",
      //metadata...
    },
    
  ],
  "offset": 0,
  "limit": 20,
  "total": 1
}

After Response, nothing returned:

{
  "results": [],
  "offset": 0,
  "limit": 20,
  "total": 0
}

By @ManyTheFish, also in #6126

🐛 Other fixes

Bump mini-dashboard version to fix display of image in local UI interface by @Strift in #6129
Fix mTLS compatibility with Go by @curquiza in #6133

🔩 Miscellaneous

Add AI usage disclosure guidelines to CONTRIBUTING.md by @meili-bot in #6114
Expose SettingsDelta and related types for external crate usage by @MkDev11 in #6119

New Contributors

@MkDev11 made their first contribution in #6119 ❤️

Full Changelog: meilisearch/meilisearch@v1.34.3...v1.35.0

`v1.34.3`

Compare Source

🐛 Bug Fixes

Increase the auth store database size to 2 GiB so that we can index more keys by @Kerollmops in #6134

Full Changelog: meilisearch/meilisearch@v1.34.2...v1.34.3

`v1.34.2`

Compare Source

This patch fixes an accidental breaking change in v1.34.1 where Meilisearch would not start with a configuration file if experimental_allowed_ip_networks was not defined.

Meilisearch Cloud users do not need to update as they were not affected by this regression
We recommend that OSS users upgrade to v1.34.2

Full Changelog: meilisearch/meilisearch@v1.34.1...v1.34.2

`v1.34.1`

Compare Source

In Meilisearch v1.34.1, we released a security fix that affect web queries initiated by Meilisearch.

🔐 Security

Cloud users: no action is needed. We found no evidence of exploitation on Meilisearch Cloud and the Cloud is protected at the infrastructure level.
Open-source users: if you allow untrusted users to configure webhooks, embedders or network of machines, we recommend you update to Meilisearch v1.34.1

In Meilisearch versions v1.8 to v1.34.0, a user with an API key with write permissions to the configuration of the Meilisearch instance could set up Meilisearch to send POST or GET requests to domains and IPs local to the private network of the Meilisearch instance, effectively bypassing the firewall. The vulnerability has not yet been assigned a CVE number; it has CVE Request 1975471 for CVE ID.

Meilisearch v1.34.1 fixes the vulnerability by forbidding Meilisearch from making any requests to a host resolving to a non-global IP, in the sense of the IANA IPv4 Special-Purpose Address Registry or the IANA IPv6 Special-Purpose Address Registry. If you need this functionality in your Meilisearch instance, you can set private IP networks as allowed with the --experimental-allow-ip-networks parameter after reviewing the security implications.

This is a breaking change, which is allowed for security reasons.

Allowing non-global IP networks

The --experimental-allow-ip-networks CLI flag and the MEILI_EXPERIMENTAL_ALLOW_IP_NETWORKS environment variable control the behavior of Meilisearch with regards to non-global IP networks, with the CLI flag taking precedence over the environment variable when both are specified.

When missing, the default is to reject all web requests resolving to a non-global IP.
When set to a comma-separated list of CIDR-formatted networks (e.g. 192.168.0.0/16,10.0.0.0), then web requests to the networks from the list will be permitted. Web requests to the non-global IPs not part of the list will still be rejected.
When set to any, all web requests will be permitted regardless of the target IP, similar to the behavior of Meilisearch v1.34.0 and lower. Use this option when you control both the machine and the configuration of the deployed Meilisearch instance.

Acknowledgments

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

renovate bot force-pushed the renovate/getmeili-meilisearch-1.x branch from 10e3884 to 4f133e2 Compare February 23, 2026 09:41

renovate bot changed the title ~~chore(deps): update getmeili/meilisearch docker tag to v1.35.1~~ chore(deps): update getmeili/meilisearch docker tag to v1.36.0 Feb 23, 2026

renovate bot force-pushed the renovate/getmeili-meilisearch-1.x branch 2 times, most recently from c645ae2 to 4fef743 Compare March 2, 2026 13:00

renovate bot changed the title ~~chore(deps): update getmeili/meilisearch docker tag to v1.36.0~~ chore(deps): update getmeili/meilisearch docker tag to v1.37.0 Mar 2, 2026

renovate bot force-pushed the renovate/getmeili-meilisearch-1.x branch from 4fef743 to bdfd6d8 Compare March 9, 2026 10:15

renovate bot changed the title ~~chore(deps): update getmeili/meilisearch docker tag to v1.37.0~~ chore(deps): update getmeili/meilisearch docker tag to v1.38.0 Mar 9, 2026

renovate bot force-pushed the renovate/getmeili-meilisearch-1.x branch from bdfd6d8 to b7eeaa3 Compare March 11, 2026 14:34

renovate bot changed the title ~~chore(deps): update getmeili/meilisearch docker tag to v1.38.0~~ chore(deps): update getmeili/meilisearch docker tag to v1.38.2 Mar 11, 2026

renovate bot force-pushed the renovate/getmeili-meilisearch-1.x branch from b7eeaa3 to 6825dac Compare March 16, 2026 14:32

renovate bot changed the title ~~chore(deps): update getmeili/meilisearch docker tag to v1.38.2~~ chore(deps): update getmeili/meilisearch docker tag to v1.39.0 Mar 16, 2026

renovate bot force-pushed the renovate/getmeili-meilisearch-1.x branch from 6825dac to dbe9af8 Compare March 23, 2026 13:35

renovate bot changed the title ~~chore(deps): update getmeili/meilisearch docker tag to v1.39.0~~ chore(deps): update getmeili/meilisearch docker tag to v1.40.0 Mar 23, 2026

chore(deps): update getmeili/meilisearch docker tag to v1.41.0

513b40c

renovate bot force-pushed the renovate/getmeili-meilisearch-1.x branch from dbe9af8 to 513b40c Compare March 30, 2026 17:22

renovate bot changed the title ~~chore(deps): update getmeili/meilisearch docker tag to v1.40.0~~ chore(deps): update getmeili/meilisearch docker tag to v1.41.0 Mar 30, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update getmeili/meilisearch docker tag to v1.41.0#76

chore(deps): update getmeili/meilisearch docker tag to v1.41.0#76
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/getmeili-meilisearch-1.x

renovate bot commented Feb 18, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

renovate bot commented Feb 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

v1.41.0: 🏈

✨ Enhancement

Search requests now use the network by default when (replicated) sharding is enabled

§ Breaking changes

🪲 Bug fixes

🔩 Miscellaneous

New Contributors

v1.40.0: 🦈

✨ Enhancement

🔐 Security

🪲 Bug fixes

🔩 Miscellaneous

New Contributors

v1.39.0: 🐳​

What's Changed

✨ Enhancement

🔬 Cross-index document hydration

foreignKeys experimental feature

foreignKeys index setting

Example

Disable proxy response buffering on Server-Sent Events (SSE)

🪲 Bug fixes

🔩 Miscellaneous

v1.38.2: 🐍

v1.38.1: 🐍

🪲 Bug fixes

v1.38.0: 🐍

✨ Enhancement

🪲 Bug fixes

🔩 Miscellaneous

New Contributors

v1.37.0

✨ Improvements

§ Replicated sharding

§ Breaking changes

Addition of network.shards

Convenience fields

network.shards validity

Change in sharding logic

useNetwork takes network.shards into account

_shard filters

Update instructions

§ Remove vectorStoreSetting experimental feature

Improve indexing performance for embeddings

§ 🔒 Security

§ 🔩 Miscellaneous

v1.36.0: 🐙

✨ Enhancement

🪲 Bug fixes

🔒 Security

🔩 Miscellaneous

v1.35.1

🦋 Bug fixes

Details

v1.35.0

🌈 Improvements

Observe the search performance

Search

Request

Response

Multi-search

Request

Response

Federated Search

Request

Response

Similar

Request

Response

Stabilize multithreaded post-processing of facets and prefixes

🦋 Fixes

Breaking change: return pagination fields in POST /indexes/<index_uid>/fields route

POST /indexes/<index_uid>/fields: Fix pattern filtering when a parent field was matching a child pattern: title was matching the pattern title.to*.

🐛 Other fixes

🔩 Miscellaneous

New Contributors

renovate bot commented Feb 18, 2026 •

edited

Loading

`v1.41.0`: 🏈

`v1.40.0`: 🦈

`v1.39.0`: 🐳

`foreignKeys` experimental feature

`foreignKeys` index setting

`v1.38.2`: 🐍

`v1.38.1`: 🐍

`v1.38.0`: 🐍

`v1.37.0`

Addition of `network.shards`

`network.shards` validity

`useNetwork` takes `network.shards` into account

`_shard` filters

§ Remove `vectorStoreSetting` experimental feature

`v1.36.0`: 🐙

`v1.35.1`

`v1.35.0`

Breaking change: return pagination fields in `POST /indexes/<index_uid>/fields` route

`POST /indexes/<index_uid>/fields`: Fix pattern filtering when a parent field was matching a child pattern: `title` was matching the pattern `title.to*`.

`v1.34.3`

`v1.34.2`

`v1.34.1`