β οΈ Breaking Change
Impact Score: 7/10
Meilisearch: v1.36.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.
Breaking-change evidence from the source
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](https://github.com/meilisearch/documentation/blob/main/assets/open-api/meilisearch-openapi-mintlify.json).
β‘ Executive Summary (TL;DR)
Meilisearch v1.36.0. Source highlight: 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!
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.
β οΈ Breaking Changes & Deprecations (1)
- 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](https://github.com/meilisearch/documentation/blob/main/assets/open-api/meilisearch-openapi-mintlify.json).
β¨ New Features & Capabilities (2)
- Introduce the `attributeRank` and `wordPosition` criteria by @Kerollmops in https://github.com/meilisearch/meilisearch/pull/6154, https://github.com/meilisearch/meilisearch/pull/6155, and https://github.com/meilisearch/meilisearch/pull/6164
- 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 t
β‘ Performance & Enhancements (4)
- `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.
- Improve OpenAPI docs and CIs to improve documentation experience
- Improve output of the declarative tests, also in https://github.com/meilisearch/meilisearch/pull/6164
π§ Bug Fixes & Patches (2)
- Fix search failing when using `attributesToSearchOn` on an empty index
- Fix "test with almost all features" by @dureuill in https://github.com/meilisearch/meilisearch/pull/6139 and https://github.com/meilisearch/meilisearch/pull/6148
π View Raw Release Notes (Original Developer Log)
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 https://github.com/meilisearch/meilisearch/pull/6154, https://github.com/meilisearch/meilisearch/pull/6155, and https://github.com/meilisearch/meilisearch/pull/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 https://github.com/meilisearch/meilisearch/pull/5944
### πΒ Security
- Bump bytes from 1.11.0 to 1.11.1 by @dependabot[bot] in https://github.com/meilisearch/meilisearch/pull/6142
- Bump jsonwebtoken from 9.3.1 to 10.3.0 by @dependabot[bot] in https://github.com/meilisearch/meilisearch/pull/6141
- Bump time from 0.3.44 to 0.3.47 by @dependabot[bot] in https://github.com/meilisearch/meilisearch/pull/6144
- Bump rsa from 0.9.9 to 0.9.10 by @dependabot[bot] in https://github.com/meilisearch/meilisearch/pull/6149
### π© Miscellaneous
- Improve OpenAPI docs and CIs to improve documentation experience by @curquiza in https://github.com/meilisearch/meilisearch/pull/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](https://github.com/meilisearch/documentation/blob/main/assets/open-api/meilisearch-openapi-mintlify.json).
- GenAI contributing and PR template changes by @dureuill in https://github.com/meilisearch/meilisearch/pull/6140
- Fix "test with almost all features" by @dureuill in https://github.com/meilisearch/meilisearch/pull/6139 and https://github.com/meilisearch/meilisearch/pull/6148
- Allow any IP for SDK tests by @Strift in https://github.com/meilisearch/meilisearch/pull/6151
- Improve output of the declarative tests, also in https://github.com/meilisearch/meilisearch/pull/6164
β€οΈΒ Thanks to @zen-zap for contributing to this release!